[Ethereum] Error: Number can only safely store up to 53 bits

bignumberweb3js

const result = await myContract.methods.myMethod(1).call();

brings the error from above. There is a simmilar questions here but since I use call gas shouldn't matter. I'm using "web3": "1.0.0-beta.35", (Beta.36 doesn't work for me at all.)

Best Answer

Note that I believe this is fixed in the latest v3.0.0 of web3 which isn't out yet. This issue is now occuring for Binance Smart Chain. In the meantime, this fix worked for me:

https://github.com/ChainSafe/web3.js/pull/3948#issuecomment-821779691

Related Solutions

[Ethereum] Uncaught Error: Error: Number can only safely store up to 53 bits

I found the problem after long debating and searching. The problem relies in the gas field of the transaction. When changed to a smaller number, for example 1000000, it works perfectly fine. It just had to do that I was supplying the gas parameter such a high value that it didn't know what to do with it.

[Ethereum] Error from web3.eth.getPastLogs() hex string without 0x prefix

I have figured it out at my end while facing the same problem. When you are using fromBlock and toBlock parameters in the function call web3.eth.getPastLogs you will have to cast the values to their hex version/equivalent. Which can be done using :

web3.utils.toHex(<fromBlock/toBlock_Value>)

This worked for me.

Best Answer

Related Solutions

[Ethereum] Uncaught Error: Error: Number can only safely store up to 53 bits

[Ethereum] Error from web3.eth.getPastLogs() hex string without 0x prefix

Related Topic