`safeTxGas` estimation fails with non-Geth nodes
See original GitHub issueTitle/Description
Estimating the safeTxGas
for a Safe transaction fails with non-Geth nodes
Steps to reproduce
Create a transaction with an RPC that uses not a Geth node (e.g. on xDai basically all nodes are OpenEthereum / Nethermind)
Expected result
safeTxGas
should be > 0 for valid transactions
Obtained result
safeTxGas
is 0
and an error is logged
Screenshots
Misc
- This bug would be a problem for Omen/GP and other Safe apps.
- Please see the comments of this issue below for more details. There’s even a link to the code which is most likely causing the problem.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
safeTxGas estimation fails with non-Geth nodes #1515 - GitHub
Title/Description Estimating the safeTxGas for a Safe transaction fails with non-Geth nodes Steps to reproduce Create a transaction with an ...
Read more >How to properly estimate gas? Auto gas-estimation via safe ...
Failed transaction can have many reasons. More details on how safeTxGas behaves can be found in the docs on the safe-contract repo.
Read more >Advanced transaction parameters - Gnosis Help Center
This article describes how to set transaction parameters such as nonce or gas limit manually when performing Safe transactions.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@alfetopito identified the issue: It’s failing on the estimateData call https://github.com/gnosis/safe-react/blob/8efafc1aaa83d731c46048648829002d0079e45c/src/logic/safe/transactions/gasNew.ts#L110-L114
@dasanra This is still an issue, please see the error below: