-
Notifications
You must be signed in to change notification settings - Fork 779
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 SignedExtension to check Metadata Root Hash #2016
Comments
Yea sounds good. Maybe could to for an RFC (but not sure if its a must here) https://github.com/polkadot-fellows/RFCs |
Yep, not super sure myself either! If need be down the line, happy to do it :) |
That is not really a spec ;) |
Having a RFC for the spec would be a good start IMO. |
@bkchr edit from spec to description to make it clearer. We'll move ahead then with the RFC first and then come back here. |
Ty! The extension will actually not be that complicated, more integrating this into the build process. However, even the integration to the build process will be easy against the metadata merkleization. |
Duplicate of: #291 |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Motivation
Offline signer experience in the Polkadot ecosystem can be massively improved. Today there is either too much manual, no scalable work (Ledger) or simply too much trust deposit on a third party (Polkadot Vault / Kampela).
The Zondax and Alzymologist team provided a way to solve these issues to the Polkadot Community on Ref #62. This gave way to the 'Metadata for Offline Signers' project that can be tracked here.
Related: #291
Request
The proposed solution is to maximize the usage of the Metadata so as to provide the right information to the offline signer. As this needs to be passed to the signer by some third party software, in order to avoid attacks the proposal is to add a new SignedExtension that would add the check of the Metadata Root Hash. This will make it so that any transaction sent from an offline device will include the root hash and this information will be then checked by the runtime.
As to how calculate this metadata root hash, there's a
specdescription and a reference implementationSolution
No response
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: