-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Why this type can not be decode? #8591
Comments
So the “Bytes” part of the input means that is come back in the metadata as You didn’t specify a chain or the actual code link, so cannot quite comment further. The first would indicate (with metadata retrieval) the actual type definition, ie. You can see what is returned and linked (also in the UI). The second will show the actual definition from Rust. |
The original definition: https://github.com/darwinia-network/darwinia-2.0/blob/08b703a75e657a120b6701a5781bdbbd88e6a617/pallet/deposit/src/lib.rs#L59 The associated type: https://github.com/darwinia-network/darwinia-2.0/blob/08b703a75e657a120b6701a5781bdbbd88e6a617/pallet/staking/src/lib.rs#L66 And it was used in this storage item: https://github.com/darwinia-network/darwinia-2.0/blob/08b703a75e657a120b6701a5781bdbbd88e6a617/pallet/staking/src/lib.rs#L128 It's a little bit like |
Which network is this? (You guys have a couple, hence asking - would like to pull the metadata and look at the type definitions in the metadata alongside) |
Ok, all good. Cann see the reason from the first link provided.
So it will treat it as the normal |
* Fix type & code optimization * Use `u16` to bypass the polkadot-js/apps#8591
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. |
I didn't get any helpful answers from StackExchange.
So, I open an issue here.
Sorry for this.
Is there any way to decode this? Thanks.
I don't know how to make my front end works.
The text was updated successfully, but these errors were encountered: