`deployContract` of the `RpcProvider` throws an error
See original GitHub issueFrom Consensys:
When using the “deployContract” function of the “RpcProvider” class, we always get the following error:
Error: -32602: More than 64 digits found: 76 at line 1 column 147
at RpcProvider.eval (eval at <anonymous> (eval at <anonymous> (lockdown.umd.min.js:1:18455)), <anonymous>:70169:35)
I think the root cause is that inside the function, constructorCalldata
was converted to decimal string and passed to starknet_addDeployTransaction
, but they should instead be in hex string…
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Error: cannot estimate gas; transaction may fail or may require ...
I frequently get errors like the following: Error: cannot estimate gas; transaction may fail or may require manual gas limit [ See: ...
Read more >Replacement fee too low - node.js - Stack Overflow
I run the script with truffle with truffle exec script.js --network testnet and I get this error and I don't know why I...
Read more >Why is an 'UNPREDICTABLE_GAS_LIMIT' error thrown when ...
In my case, I got that exact error message because I instantiated a contract using an incorrect address. Fixing the address made the...
Read more >Documentation - Ethers.js
If the current environment does not have a secure entropy source, an error is thrown. Wallets created using this method will have a...
Read more >hardhat cannot estimate gas; transaction may fail or ... - You.com
The "function selector was not recognized" error message is thrown when you're ... Hardhat deploy contract error: Error: cannot estimate gas; transaction ....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jonesho & @ivpavici I came to a similar solution and have submitted a PR to fix this bug.
Hi @ivpavici
The project I am working on is currently using the OZ Cairo contracts v0.3.1. I am just using the basic Account preset:
I am first instantiating a Provider based on the users config (either rpc or sequencer):
The configuration file provides the following:
Account keys are generated with the following:
Contract is deployed with the following:
This pattern works to successfully deploy an account with the sequencer provider. It fails with the following error when using the rpc provider:
Thanks @janek26 I will take a look into this myself if I can make some time to do so. I have submitted a PR previously, albeit just a minor documentation fix.