-
Notifications
You must be signed in to change notification settings - Fork 690
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
Metadata V16: Features to include in V16 #4520
Comments
polkadot-fellows/RFCs#99 with we would need to change the metadata to return multiple sets of transaction/signed extensions indexed by the version. |
IMO an absolute must have of metadata v16 is a dedicated top-level entry named
|
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/metadata-v16-updates/9557/1 |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/metadata-v16-updates/9557/7 |
Raising this issue to discuss about the features that are needed by the community in the next metadata version.
These features will be initially exposed under a metadata unstable versioning (u32::max), that will stabilize into v16.
I've compiled a possibly incomplete list of requested features that we may want to add to v16:
Requested features V16
SignedExtension
toTransactionExtension
#5347Core_hash
runtime API for hashing extrinsics #5468cc @jsdw @niklasad1 @bkchr @paritytech/subxt-team @xlc @josepot
The text was updated successfully, but these errors were encountered: