-
Notifications
You must be signed in to change notification settings - Fork 357
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
Setting up node, transfer failed #2394
Comments
Hi @goushijie It seems you are mixing multiple call data. "Balances.transfer" is the Substrate API, but the substrate API doesn't support providing gas (nor gas limit or price). Which SDK are you using ? I'm not familiar with the syntax you provided. |
Thank you very much for your reply. I started the script
But the error message: |
will local nodes ban transactions? the link |
@goushijie failing transactions are banned for 30min IIRC. You can restart your node (the docker command) to try again. The code you wrote is unknown to me, can you tell me what SDK/Framework is it ? |
@crystalin I restarted the node, the same problem, I used SubstrateInterface https://github.com/polkascan/py-substrate-interface |
@albertov19 any experience with this ? |
@eshaben could you please check what the issue is? Thanks in advance 🙏 |
@goushijie i tried your code snippet out using the latest version of py substrate interface, 1.7.3, and it worked as expected. can you please try to bump the version and let me know if that resolves the issue for you? |
![]()
![]() |
Ah ok, I attempted this on a development node, not on moonbeam mainnet. So my command was the same as yours with the exception of the |
I'm sorry that you lost your funds 😔💔 Moving forward, if you're running a node on mainnet, try to avoid using the |
I execute
Docker run -- rm -- name moonbeam_ Development - p 9944:9944 puretake/moonbeam: v0.32.1-- chain moonbeam -- ws external -- rpc external
, and then call the transfer through the program, why did it fail?Error is {'code': 1010, 'message': 'Invalid Transaction', 'data': 'Transaction call is not expected'}
The text was updated successfully, but these errors were encountered: