You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whenever we try to execute a transaction in Gnosis Safe we try to estimate the gas limit. In many cases we do this when one signature is still pending, so the last user can sign and execute in the same step. For some reason, Nethermind nodes are having problems into estimating the gas limit in this situation, and is the only type of node where we find this difficulties.
For estimating the gas we are just calling the estimateGas function from web3.
Funny thing is that executing a call to check if the transaction will go through returns a revert message. When adding a higher gas limit manually the call method will return success when we get the correct value for gasLimit
You will need to setup a Safe with any configuration you want
When executing any kind of transaction you will find that sending the transaction with the last signer (at create time if threshold is just one signer), a potential error message is shown. If ignored and the transaction is sent will revert because out of gas. Adding more gas until the error is not visible will make the transaction work perfectly
Expected behavior
I would expect that the node returns a valid gas limit to execute the transaction without issues
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever we try to execute a transaction in Gnosis Safe we try to estimate the gas limit. In many cases we do this when one signature is still pending, so the last user can sign and execute in the same step. For some reason, Nethermind nodes are having problems into estimating the gas limit in this situation, and is the only type of node where we find this difficulties.
For estimating the gas we are just calling the
estimateGas
function from web3.Funny thing is that executing a
call
to check if the transaction will go through returns a revert message. When adding a higher gas limit manually thecall
method will return success when we get the correct value for gasLimitTo Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect that the node returns a valid gas limit to execute the transaction without issues
The text was updated successfully, but these errors were encountered: