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
Also reach out to @fleupold - he has now looked into it a bit and might be able to share some useful insights in what ways current behaviour is not optimal.
Right now the Erigon implementation has two issues:
It includes tx.to access keys even if it has less than 24 storage keys (including the extra 2400 gas we pay for the to address is an overhead since the address is already marked warm as part of the fixed tx overhead, so we need at least 24 keys each saving 100 gas to make up for it)
Not containing all addresses/storage keys that are accessed
(Requested by Martin Köppelmann)
This is a call to create an access list for this transaction: https://etherscan.io/tx/0x94eb6bc442d66d1c185133c796de8279e61cd83da08eb7abf0187ba2d251a27c
If you would use the access list that Erigon calculates the transaction would get more expensive. If you manually remove the first entry:
(which is the “to address”) it will get slightly cheaper. But I am pretty sure the access list is incomplete.
The text was updated successfully, but these errors were encountered: