Open riordant opened 1 year ago
The transaction that we attempt to send is a valid state change (verified by executing on a fork from the same block afterwords) but when trying to send, it fails.
The actual error is execution reverted
it's a bit further. How do you get the exact block number on which the estimation was run, since it's not available in the error? Block time on arbitrum goerli is fast so if your block number is approximate still it may have worked for you but on actual one it must be failing.
For debugging, if you can find a block number when it fails otherwise you can just hardcode a gasLimit, so that whenever if it fails it will send a failed tx. Then you can use any of online tools like tenderly to debug the actual cause of the revert on that tx.
Ethers Version
5.7.1
Search Terms
No response
Describe the Problem
Hi, we are getting strange issues with sending transactions through Ethers on the arbitrum-goerli test chain. It only seems to occur when there is a gas spike. The transaction that we attempt to send is a valid state change (verified by executing on a fork from the same block afterwords) but when trying to send, it fails. we believe it is related to gas estimation in Ethers (v5). any help would be appreciated. thanks.
Code Snippet
Contract ABI
No response
Errors
Environment
Arbitrum-Goerli