add new fields required by Ecotone upgrade #46
Conversation
roberto-bayardo
force-pushed
the
ecotone
branch
from
58fd066 to
48b8cb8
Compare
roberto-bayardo
force-pushed
the
ecotone
branch
from
48b8cb8 to
20055da
Compare
|
I am not sure if we want to merge this because we may want to hardcode the values so that L1 and the L2 view never get out of sync. The current implementation of the smart contracts in ethereum-optimism/optimism#8723 migrates the legacy scalar to the base fee scalar and sets the blob base fee scalar to 0 so we could just hardcode those values. We need to consider the cases of new chains and upgrading chains which adds some complexity to the smart contract implementations if we wanted to allow for dynamic setting of these values in genesis for new chains. If the values can be different, then it makes the consensus rules different in different op stack chains for the upgrade txs which adds complexity that i prefer to avoid. |
|
I am feeling confident that we do not need this PR based on the params being deterministic as per ethereum-optimism/optimism#8829 |
Description
Adds two new parameters required by the Ecotone (formerly Eclipse) upgrade to the GenesisSystemConfig.