-
Notifications
You must be signed in to change notification settings - Fork 591
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: App Keys for Fully Embedded Accounts #615
base: master
Are you sure you want to change the base?
Conversation
bca569a
to
f793cf0
Compare
Sorry, had some files from other branches. Cleaning up. |
f793cf0
to
e972ff0
Compare
Merged by EIP-Bot.
e972ff0
to
158a896
Compare
158a896
to
3fdb552
Compare
As we build infrastructure that facilitates embedded wallets, sites have a new opportunity to manage keys to manage permissions they receive (like via ERC-7715). Alternatively, the site may want to defer key backup to the wallet, while still wanting the benefits of being able to sign on their own behalves. This is one extremely minimal initial approach to granting sites key material that is deterministically generated to them. It probably needs some refinement in its algorithm, but can be treated as a general outline of an approach for consideration even in this initial draft form.
3fdb552
to
1d2de27
Compare
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
cdcdfb6
to
3bb1270
Compare
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
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.
Note to self, this is blocked on #436.
As the Ethereum ecosystem continues to evolve, standardized approaches to key management and permissions become increasingly important. This ERC aims to contribute to the ongoing development of user-friendly and secure wallet interfaces, fostering innovation in decentralized applications while maintaining strong security practices. | ||
|
||
By adopting this standard, wallets and dApps can work together more effectively, providing users with a more streamlined and secure experience in the Web3 environment. As the community continues to refine and expand upon these concepts, we anticipate further improvements in user experience, security, and interoperability across the Ethereum ecosystem. | ||
|
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.
## Copyright | |
Copyright and related rights waived via [CC0](../LICENSE.md). |
The copyright section is not optional.
## Conclusion | ||
|
||
This ERC proposes a standardized method for wallets to generate and manage app-specific keys, providing a secure and consistent approach to permission management in decentralized applications. By implementing this standard, wallets can offer enhanced privacy and security for users while enabling more seamless interactions between dApps and user accounts. | ||
|
||
The proposed `wallet_getAppKey` method allows for the creation of unique, deterministic keys for each application, reducing the risk of cross-app tracking and improving overall user privacy. This approach also facilitates easier permission management and potential future upgrades to more advanced account structures. | ||
|
||
As the Ethereum ecosystem continues to evolve, standardized approaches to key management and permissions become increasingly important. This ERC aims to contribute to the ongoing development of user-friendly and secure wallet interfaces, fostering innovation in decentralized applications while maintaining strong security practices. | ||
|
||
By adopting this standard, wallets and dApps can work together more effectively, providing users with a more streamlined and secure experience in the Web3 environment. As the community continues to refine and expand upon these concepts, we anticipate further improvements in user experience, security, and interoperability across the Ethereum ecosystem. |
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.
All of this content probably belongs in the Motivation section, since it's trying to convince the reader to pick this particular standard.
The commit 85cd73a (as a parent of 4229bc8) contains errors. |
As we build infrastructure that facilitates embedded wallets, sites have a new opportunity to manage keys to manage permissions they receive (like via ERC-7715).
Alternatively, the site may want to defer key backup to the wallet, while still wanting the benefits of being able to sign on their own behalves.
This is one extremely minimal initial approach to granting sites key material that is deterministically generated to them. It probably needs some refinement in its algorithm, but can be treated as a general outline of an approach for consideration even in this initial draft form.