Unable to sign on a solo chain with custom signed extensions
Leouarz opened this issue · 4 comments
Hello,
Sorry if this it not the correct place to discuss this issue I have.
I currently followed all the instructions to add a custom network.
It all went fine regarding the QR code generation for specs and metadata.
Unfortunately, when trying to sign a transaction, i got the following error:
Something has gone wrong
Failed to decode extensions.
Please try updating metadata for data-avail network.
Parsing with data-avail16 metadata:
Error parsing incoming transaction content. Genesis hash values from decoded extensions and from used network specs do not match.
The thing is metadata are obviously fresh from being generated 2 mn ago. The genesis hash is ok on chain and in the vault, and the spec_number is fine too.
I definitely suspect our custom signed extension and would like to know if you have already stumbled into a similar issue as we really want to make Polkadot Vault available with Avail.
Don't hesitate in case you need more information.
Thank you for the report. This is the first ticket about this issue.
Thank you for your answer, is the link not available or i am missing something ? 😅
Oh, sorry for the confusion. I meant there were no other tickets about this issue; this is the first one. Thanks again for reporting.
Ahh, thanks for the clarification, I don't know how it will proceed from now, but know that I can help if it's needed since there's some interesting use cases and chains using signed extension (for the asset pallet, the transaction payment, and in general any custom verifications), I guess you're already aware haha.