-
Notifications
You must be signed in to change notification settings - Fork 918
Stabilize V16 metadata #8443
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?
Stabilize V16 metadata #8443
Conversation
@bkchr Do you think we should update One constraint is that I'd like to get this merged before the release cutoff date on May 15th to get it into the next stable release, so my preference is to merge this first and update that later. |
Given the looser version requirements, no change to |
Co-authored-by: Bastian Köcher <[email protected]>
Makes sense! I guess it will eventually want to be updated for V16 metadata so that it can be used for decoding/checking v5 transactions (because V16 metadata contains the transaction extensions for each possible version the extrinsic might use)? |
All GitHub workflows were cancelled due to failure one of the required jobs. |
This PR bumps frame-metadata 23.0.0, which stabilizes V16 metadata. This was previously available as the "unstable" metadata.
The main additions provided by V16 metadata are:
To sanity check this, I've built a polkadot node with this change and checked that using Subxt (this PR paritytech/subxt#1999), v16 metadata is indeed available, downloads and decodes correctly.