-
Hi! There is an issue opened crustio/crust#894 and I don't understand whether it's a type registry issue (think not, since we are talking about inability to use the pallet) or a pallet discovery issue. Any ideas if something should be updated in py-substrate-interface? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Ok I did some tests and the culprit is actually manually setting the type registry to This was necessary before in order to interpret the types used in the runtime, but I noticed Crust Shadow on Kusama upgraded to After analyzing what PolkadotJS generate for extrinsic bytes I found out the real culprit is actually the change in TL;DR: you can omit the |
Beta Was this translation helpful? Give feedback.
-
It worked! Thanks, I would never figured it out without your help. |
Beta Was this translation helpful? Give feedback.
Ok I did some tests and the culprit is actually manually setting the type registry to
type_registry_preset="crust"
.This was necessary before in order to interpret the types used in the runtime, but I noticed Crust Shadow on Kusama upgraded to
MetadataV14
, which embeds its own type registry (PortableRegistry
), so that drops the need to set manual types.After analyzing what PolkadotJS generate for extrinsic bytes I found out the real culprit is actually the change in
Address
fromAccountId
toMultiAddress
, which adds one extra bytes in front of the AccountId and because that was missing, it messed up the decoded by the runtime and caused the panic.TL;DR: you can omit the
type_registry_pr…