-
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
getTransaction: Error: Number can only safely store up to 53 bits #5703
Comments
Hi, thank you for bringing this to our attention. Could you provide what chain this transaction exists on? Doesn't seem to be on ETH mainnet, any of the testnets, or Binance chain Most likely there is a property of the transaction object that web3 is attempting to convert from hex to a number and is causing an overflow. We've seen this issue before and have introduced a fix in rewrite of the library ( |
i'm use bsc testnet: https://testnet.bscscan.com/tx/0xa648ab6d55adad2cc0df5c43499710cf010d58cacb16195d5338ade168d9e20c |
Hey @Sotatek-TuanNguyen7, As a workaround, you can pass the string |
Hi @nikoulai , |
👍 my bad |
This is possibly the same as #5761 |
Is there an existing issue for this?
Current Behavior
Transaction: 0xa648ab6d55adad2cc0df5c43499710cf010d58cacb16195d5338ade168d9e20c
calling getTransaction for this transaction fails with: "Error: Number can only safely store up to 53 bits"
Expected Behavior
get success transaction success
Steps to Reproduce
web3.eth.getTransaction('0xa648ab6d55adad2cc0df5c43499710cf010d58cacb16195d5338ade168d9e20c')
Web3.js Version
1.8.1
Environment
Anything Else?
No response
The text was updated successfully, but these errors were encountered: