-
Notifications
You must be signed in to change notification settings - Fork 363
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
Fails to decode OpaqueCall
on Westend
#2858
Comments
Extrinsic -
So, yes, whatever it is, cannot decode it manually either, it is invalid. (length does match up nicely with the 37 for the actual data, so the store and weight params is most-probably correct) TL;DR Expected, also see https://westend.subscan.io/extrinsic/0x5b7ee199447a71c0a3f411ea64a919e2a02b0e9d5ba565668b89026ea11675fa |
Closing. Operating as expected with the data provided. |
Thank you for the detailed break down! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
The below code errors trying to decode an
OpaqueCall
from a block #2223354 on Westend:I had a similar problem before, but that was due to using the wrong registry (see #2753). In this case, from what I understand, I am using the correct registry.
Is this expected behavior on Westend? I recall seeing something about having problems supporting older Westend runtimes, but I couldn't find a concrete github issue to confirm.
(relates to paritytech/substrate-api-sidecar#343)
The text was updated successfully, but these errors were encountered: