-
Notifications
You must be signed in to change notification settings - Fork 515
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
Add ERC: Wallet Call Token Capabilities #681
base: master
Are you sure you want to change the base?
Conversation
28fff5b
to
fa05264
Compare
6fe45bb
to
fd11f4c
Compare
ERCS/erc-7795.md
Outdated
|
||
In this scenario, the wallet **MAY** prompt the user to sign the necessary transactions to fulfill the requirements before proceeding with the main transaction. The wallet **SHOULD** compute possible solutions to meet the requirements and **MUST** ensure that these prerequisites are met prior to executing the main transaction. | ||
|
||
```mermaid |
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.
Our renderer does not support mermaid. Please include an image (preferably SVG) in your assets directory.
ERCS/erc-7795.md
Outdated
3. Independent versioning of requirement types | ||
4. Simpler implementation for basic wallets | ||
|
||
## Reference Implementation |
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.
The reference implementation section should contain a minimal example implementation of the standard, not usage examples. This content belongs in the specification section, especially considering it's introducing new requirements (with MUST/MAY/etc.)
ERCS/erc-7795.md
Outdated
|
||
Users already trust their wallet provider to craft, manipulate and send transactions on their behalf. This ERC only adds a new field to the transaction request, which the wallet can use to make more informed decisions about transaction construction. | ||
|
||
DApps **MAY** opt out of using this feature if they wish to handle requirement fulfillment themselves. |
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.
Requirements should only be introduced in the specification section.
Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
The commit e49930c (as a parent of 9bbd734) contains errors. |
Thanks @SamWilsn ! 🙏 I've addressed all comments. Let me know if any further changes are required |
This ERC introduces a mechanism for dapps to provide prerequisites for transactions to smart contract wallets. Wallets can use these prerequisites to make more informed decisions about transaction construction.