-
Notifications
You must be signed in to change notification settings - Fork 69
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
How to use tx.proxy.proxy with api-cli correctly? #329
Comments
Ummm... it checks against what is on-chain in the metadata, so assuming you connected to a proxy-capable chain, it should just work. https://github.com/polkadot-js/tools/blob/master/packages/api-cli/src/api.ts#L188 Will try and see if I can reproduce on something like Kusama/Polkadot with proxies. |
It indeed works as expected, i.e. Which chain did you try it on? |
Having said all that - the nested calls (same would be the case with batch) as an issue. An example is the So although it has nothing to do with your specific question (well, it is related, aka it won't work), stuff like TL;DR Your chain may not expose |
Thanks for taking time to provide support. I tried to do Kusama Democracy votes. I will post you the complete logs, perhaps it was something else wrong in transaction. Error messaging of the api-cli seems a bit tricky to understand for me still.
|
So polkadot-js-extension wallet generates following extrinsics as argument contents, but api support only 3 arguments. |
Receiving error when trying to commit tx.proxy commands using api-cli.
The text was updated successfully, but these errors were encountered: