-
Notifications
You must be signed in to change notification settings - Fork 114
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
compose_call only works with dest=PUB_KEY #8
Comments
P.S.: Please also see paritytech/substrate#5180 perhaps you have ideas how to solve it? Thanks. |
It should auto-detect the address format, but you were right, there was an issue with the auto-detection of whether the given argument is a public key, SS58 encoded AccountId or SS58 encoded AccountIndex. I assumed the SS58 encoded AccountId is always 47 chars long, but this was not the case. Thanks for the feedback, I fixed it in polkascan/py-scale-codec@650723e so with a new pip install it should be fixed. Regarding your comment about subkey, I also asked a question in the Riot group 'Substrate Technical', but no answers there unfortunately. We also want to implement signing, so as soon as I have a solution I'll let you know. |
Oh wow, you're a star. That was VERY quick. Thanks a million! |
Thanks a lot, @arjanz - any news? |
When playing with
I got a lot of errors like
until I realized that I cannot (?) send to an
but must use the
instead, for the
dest
:I suggest, you mention that the https://github.com/polkascan/py-substrate-interface#compose-call explanations?
The text was updated successfully, but these errors were encountered: