Conversation
when number can only safely store up to 53 bits web3#3745
|
|
|
Thank you for opening a PR for this! After discussing this with the team, this would be a breaking change for the library and doesn't make sense to do it in this way for now. To achieve similar functionality without a breaking change, would require an overwriting functionality that will exist using the plugin system we have planned for I'm curious to know if this was a one-off issue for you for this transaction, or is this something you've faced multiple times? It's just extremely unusual to set such a high |
|
Hello @spacesailor24. I often see this Similar transactions with hight `gasLimit`https://bscscan.com/tx/0x442496852e205278cc6b8fc0c3f5a93579a2330a67b037aef1329f13aff97aae Right now i used |
|
Thank you for the reply, I'm happy to hear you've found a work around. As mentioned above, we most likely won't be merging this any time soon, but we will keep this in mind for the next major version update |
|
this could help #3936 (comment) |
Description
fixes issue when number can only safely store up to 53 bits
#3745
Type of change
Checklist:
npm run dtslintwith success and extended the tests and types if necessary.npm run test:unitwith success.npm run test:covand my test cases cover all the lines and branches of the added code.npm run buildand testeddist/web3.min.jsin a browser.