-
Notifications
You must be signed in to change notification settings - Fork 5.1k
eth.getBlock fails with "Number can only safely store up to 53 bits" #3512
Comments
Are you using the Quorum blockchain or another EVM based fork? If so, the solution is to use a Web3.js extension library like jpmorganchase/quorum.js. (Possible duplicate of #3442) |
Thanks for the reply, I don't use Quorum. I've linked a small example in Ethereum Studio, it's only slightly modified version of the hello-world app there, but demonstrates the problem. I've seen similar issues here (such as #1960 or #1905), but they were closed already. The one you linked mentions timestamps specifically but the error happens already before the |
@MaxXor From what I can see superblocks/ethereum-studio is using a custom client. It might be worthwhile to open this issue over there. We run a large set of tests here against
They all work. Closing since this looks like an issue downstream from here...please just ping if you discover otherwise. |
For future googlers, in my case this was caused by using number type for gas when parsing from hex. Changing this to String fixed the issue for me: https://github.com/dvcrn/web3.js/commit/b868c5fece70fba6d34b577ef59f3fa3159390ad |
Expected behavior
Get the block.
Actual behavior
Error "Number can only safely store up to 53 bits"
Example code
Ethereum Studio example: https://studio.ethereum.org/5eb924ed26b4730012351a47?openFile=app/app.js Lines (133-145)
Steps to reproduce the behavior
Environment
Javascript with web3.js version 1.2.7
The text was updated successfully, but these errors were encountered: