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
just Erigon used as an Execution Layer for Consensus Layer clients with default configuration
Chain/Network:
ETH main
Expected behaviour
I would like to use eth_callMany to simulate a trade. Obviously 0x380d096daec90a2d255574df70a89f65efc773a627adc924fba5f5869570e642 on ethereum is a successfully executed transaction and its position in the block is 10. So when I build the correct raw transaction and use eth_callMany at any position in block, I should be able to call this transaction successfully.
Actual behaviour
In fact, when I use eth_callMany at any position greater than 10, it occurs this:
insufficient funds for gas * price + value: address ...
Any position less than or equal to 10 can be executed normally, which means that the original transaction at position 10 was not executed normally.
To be able to execute eth_callMany, I had to set gasBailout in core.ApplyMessage to True in erigon/cmd/rpcdaemon/commands/eth_callMany.go
Noticing that the transaction at position 9 has the same tx.from as the transaction at position 10, it leads me to believe that this issue is related to block BaseFee in callMany #6569 . @ArielTM
System information
Erigon version:
OS & Version:
Commit hash:
Concensus Layer:
Chain/Network:
Expected behaviour
eth_callMany
to simulate a trade. Obviously 0x380d096daec90a2d255574df70a89f65efc773a627adc924fba5f5869570e642 on ethereum is a successfully executed transaction and its position in the block is 10. So when I build the correct raw transaction and useeth_callMany
at any position in block, I should be able to call this transaction successfully.Actual behaviour
eth_callMany
at any position greater than 10, it occurs this:eth_callMany
, I had to setgasBailout
incore.ApplyMessage
to True inerigon/cmd/rpcdaemon/commands/eth_callMany.go
tx.from
as the transaction at position 10, it leads me to believe that this issue is related to block BaseFee in callMany #6569 . @ArielTMSteps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: