-
Notifications
You must be signed in to change notification settings - Fork 258
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 a basic version of the CheckMetadataHash signed extension #1590
Conversation
So this break the Barely mentioned in the change log that this could happen, e.g. even the staking miner included this release and has that issue now. Not to mention that all 0.36 user will upgrade to this as well as soon as they run into any issues... |
@FlorianFranzen do you mind filing an issue in the staking-miner repo? I wonder why it's just works on "test chains" ^^ |
Could you provide a way for us to reproduce this, please? Adding the new extension to |
@jsdw I looked at in detail and tried to create a trivial example without success, so it must be particular to our use-case. The last time I looked at this was also before the runtime update on Polkasama, so that might also play a role is guiding me to believing it is the config that caused the issue. The issue also appeared in the miner, but it seems unrelated. I currently lack the time to look into this further. Sorry for the false alert. I will post an update should I uncover anything of value. |
This version doesn't try to hash the metadata and provide a hash at the moment, and just tells the node that there will be no hash via a 0 byte in the tx payload.
I tested this by compiling polkadot from paritytech/polkadot-sdk#4274 and running
cargo run --example tx_basic
with and without the new extension. It failed without and worked with.Close #1605