-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
1.x "Error: Number can only safely store up to 53 bits" on batch getTransaction #6241
Comments
FYI the error persists even when we upgrade to v1.10 |
Hi there, thank you for reporting this issue - it's actually a longstanding known issue with We did completely fix this issue in the latest version of web3, version |
I understand that in version 4 is resolved and we do plan to migrate ASAP but it is not straight forward and ideally we would like to have enough time to do it properly. A fix on this would give us that time. I wonder if gas can be moved into the if(hex) block or even if we treat the gas as a <string | number> instead; when the number is too big would temporarily fix the issue 🤷 |
#5845 is supposed to keep A little off topic, but when you guys do decide to migrate to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
Hello,
we are using web3 eth.getTransaction function to batch fetch transaction data using eth.BatchRequest();.
However, in web3-core-helpers the outputTransactionFormatter is throwing "Error: Number can only safely store up to 53 bits" when is trying to parse gas value for BNB chain.
Here is a tx example: 0x3e005e4ef863873682e028a3f500ee575474ded431edc09ee70e7e3c4e981c6a
and the gas that is passed is
gas: '0x7fffffffffffffff'
Expected behavior
to properly parse the value
Actual behavior
throws Error: Number can only safely store up to 53 bits
Environment
Web3 version 1.7.5
The text was updated successfully, but these errors were encountered: