-
Notifications
You must be signed in to change notification settings - Fork 70
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
Error when estimating gas #3
Comments
I am also having this problem. |
Seems to stem from a |
@banteg We at badger would love to fund a gitcoin bounty for the next round to solve this problem. Are you already working on it and/or would it be helpful to have someone fork this repo and sort that out? |
some form of this problem persists after #11:
|
This is not related to the initial error; you tried to estimate a transaction that calls multicall contract via the |
really want to get to the bottom of this, i think passing good gas values to the final tx is important. i create a new env, with nothing else but this seems to fail in the same way @jo-tud reports in the beginning of this issue:
someone suggested to use the
now if i run the script again, but this time with amount anything else but the full balance of the safe, it works! somehow doing
breaks however, its output
differs a lot from the recommended gas limit. also, in all the of erroneous cases above, and tbh, all i care for is that that recommended gas limit ends up in so hereby a feature/fix request: let there be a function which grabs recommended gas and sets |
my understanding is that this issue is related to using gnosis safes <v.1.3.0. the implementation of safe-global/safe-smart-account#274 in v.1.3.0 makes setting for those still on <v1.3.0, @Uxio0's pr #15 is a workaround that removes dependency of web3's |
Yes, in Safes |
I'm receive the following error, when trying the to estimate the gas for any safe tx:
No idea why that would be happening.
safe.preview(safe_tx, call_trace=True)
works without flaw and shows the gas used...The text was updated successfully, but these errors were encountered: