-
Notifications
You must be signed in to change notification settings - Fork 257
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
Dynamic call indices for sudo and utility batch #356
Comments
Any update on this matter? I am trying to execute dynamic batch calls and assume it not to be working in 0.25.0 due to this issue? |
See the latest thinking in #716. I think pure dynamic calls might be working, e.g. see the multisig example: https://github.com/paritytech/subxt/blob/master/examples/examples/dynamic_multisig.rs#L61. Note if you are running e.g. one off scripts where you can guarantee the metadata is synced with the target node you can use the statically generated types e.g. https://github.com/ascjones/seeding/blob/main/src/main.rs#L47 |
This is something that |
This is resolved now on |
Currently the
Sudo::sudo
andUtility::batch
dispatchables generate code which accepts statically constructed instances of the top levelCall
enum. This means that if there is a mismatch of pallet/dispatchable composition between the static metadata used to generate API, and the target node runtime, then the node will fail to decode the calls.When making a
Call
directly, the API will use the metadata of the running node to prepend the pallet index and the call index. We should consider making this available when constructing these composite dispatchables.Extracted from #309
The text was updated successfully, but these errors were encountered: