Content pfp
Content
@
0 reply
0 recast
0 reaction

jacopo pfp
jacopo
@jacopo
any plans to add support for custom gas limit in c.contract?
1 reply
0 recast
1 reaction

Vladyslav Dalechyn pfp
Vladyslav Dalechyn
@dalechyn.eth
afaik that's limited by frame spec, we can't pass `gasLimit` there =(.
1 reply
0 recast
1 reaction

jacopo pfp
jacopo
@jacopo
possible to add support for custom gas limit in frames? @v @horsefacts.eth sometimes default estimate needs to be overridden for a tx to go through
1 reply
0 recast
1 reaction

headless horsefacts pfp
headless horsefacts
@horsefacts.eth
Actually this already works, docs are out of date! Add an attribute like `gas: "100000"` (string value) to set the gas limit.
2 replies
1 recast
3 reactions

jxom  pfp
jxom
@jxom
What’s the point of adding a gas limit when wallets fill this in anyway?
1 reply
0 recast
1 reaction

jxom  pfp
jxom
@jxom
What wallets aren’t estimating this properly to warrant this workaround? Maybe should reach out.
1 reply
0 recast
1 reaction

jacopo pfp
jacopo
@jacopo
I stumbled upon this in the past and it was regardless of wallet. It happens unpredictably with certain conditions in contract functions, and generally when state has changed between simulation and execution. I think I saw a related issue in the past, will try to dig it up
1 reply
0 recast
2 reactions

jacopo pfp
jacopo
@jacopo
this is the common scenario https://github.com/wevm/wagmi/discussions/2196 I’ll look for one related to my edge case which is different and harder to reproduce (condition is evaluated wrongly on estimate, sometimes), which I’d love to see fixed. but generally a multiplier or override on estimated gas is enough
1 reply
0 recast
0 reaction

jxom  pfp
jxom
@jxom
I see. I still wish wallets were smarter about gas estimations, IMO.
0 reply
0 recast
2 reactions