-
Notifications
You must be signed in to change notification settings - Fork 180
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
decoding extrinsic panics. #405
Comments
@georlav Hello, have you solved this problem? I also have this problem. |
No, I haven’t spent much time on it. As a temporary workaround, I had created a small function that mimics SubmitAndWatchExtrinsic but accepts the extrinsic bytes versus extrinsic.Extrinsic, bypassing the encoding step. |
Hi, could you share your solution with me? I'd be very grateful. |
Here is a draft example of how you can use the client and submit the extrinsic bytes
|
@georlav Oh, I thought you had solved the problem of parsing string extrinsic temporarily. Thank you anyway. |
Every time I try to use codec.Decode or codec.DecodeFromHex on an extrinsic I previously created using the codec, the codec panics. I can broadcast these extrinsics without any issues, so they are valid.
In the following example, I'm using codec.DecodeFromHex for simplicity, but the same problem occurs if I use codec.Decode or even if I try to use the Marshaler.
However, I receive the following panic:
The extrinsic can be decoded successfully using this tool: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fasset-hub-westend-rpc.dwellir.com#/extrinsics/decode
I am using the latest master branch.
The text was updated successfully, but these errors were encountered: