-
Notifications
You must be signed in to change notification settings - Fork 630
Add ERC: Universal On-Chain Metadata Parser Interface #755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,192 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--- | |
--- | |
eip: 7835 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
title: wallet_transmitCrossChainIntents Method | ||
description: Standard Cross-Chain Intent Parsing Method For EVM Wallet | ||
author: ZeroKPunk (@ZeroKPunk), 0xbbPizza (0xbbPizza) | ||
discussions-to: <URL> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please create a discussions topic in Eth Magicians with a link to this PR: https://ethereum-magicians.org/c/ercs/57
… Ethereum - Completely redefined the purpose of the ERC from a cross-chain wallet RPC to a metadata abstraction parser for Ethereum. - Broadened the scope to enable wider applicability across diverse Ethereum use cases. - Focused on providing a standardized interface for parsing Ethereum network metadata. - Removed cross-chain wallet RPC specifics to align with the new goal of flexibility and broader adoption.
The commit 4d80df3 (as a parent of dd694df) contains errors. |
--- | ||
eip: 7835 | ||
title: Universal On-Chain Metadata Parser Interface | ||
description: A universal interface for parsing wallet-accessed metadata, enhancing security, usability, and data readability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your description contains only either a restatement of your title ("A universal interface for parsing...metadata") or fluff ("enhancing security, usability, and data readability".)
Try to include more information in your description than was already introduced in your title.
For example, you could try to answer questions like:
- What is metadata?
- How is it universal?
- How is it parsed on chain, and why would you want it there?
|
||
## Abstract | ||
|
||
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to Wallets. The standard consists of two core components: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
metadata (MetaData)
Is "MetaData" different from "metadata"?
|
||
## Abstract | ||
|
||
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to Wallets. The standard consists of two core components: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to Wallets. The standard consists of two core components: | |
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to wallets. The standard consists of two core components: |
|
||
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to Wallets. The standard consists of two core components: | ||
|
||
- **1.Wallet-level parser interface:** wallet_metaDataAbstractParser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inline code should be enclosed in backticks (`) throughout the document. Also, just use a regular markdown ordered list.
- **1.Wallet-level parser interface:** wallet_metaDataAbstractParser | |
1. Wallet-level parser interface:** `wallet_metaDataAbstractParser` |
This proposal defines a standardized interface for parsing on-chain metadata (MetaData) relevant to Wallets. The standard consists of two core components: | ||
|
||
- **1.Wallet-level parser interface:** wallet_metaDataAbstractParser | ||
A universal entry point that Wallets can use to request metadata parsing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wallet isn't a proper noun.
A universal entry point that Wallets can use to request metadata parsing. | |
A universal entry point that wallets can use to request metadata parsing. |
|
||
### 2. Smart Contract-Level Parsing Logic: parserHandler and parserData | ||
|
||
`parserHandler` is a smart contract deployed on-chain that implements the actual parsing logic. It receives parameters from Wallets and returns parsed, human-readable metadata. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`parserHandler` is a smart contract deployed on-chain that implements the actual parsing logic. It receives parameters from Wallets and returns parsed, human-readable metadata. | |
`parserHandler` is the address of a smart contract deployed on-chain that implements the actual parsing logic. It receives parameters from Wallets and returns parsed, human-readable metadata. |
|
||
## Rationale | ||
|
||
### **1. Generalization:** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just use normal headings. You don't need to do manual numbering.
|
||
## Security Considerations | ||
|
||
### Parsing Logic Security: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Parsing Logic Security: | |
### Parsing Logic Security |
|
||
- Parsing contracts should be audited to prevent potential vulnerabilities or malicious behavior. | ||
|
||
### User Privacy: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### User Privacy: | |
### User Privacy |
|
||
- Wallets must ensure that user data is handled securely and not leaked during parsing. | ||
|
||
### Trust Minimization: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Trust Minimization: | |
### Trust Minimization |
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: