Version Packages

Trigger release

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

fix(ctb): correct GPO abi and layout (#4582)

Fixes some small errors in the GPO's API and storage layout that did not
conform to the standards for how we are ugprading the L2 system.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Trigger Release

op-node: Fix too eager advance in batch queue

op-node: Add stubbed Goerli config

op-chain-ops: better deploy config validation

feat(ctb): check for relayed legacy messages

This includes an op-e2e action test which can be used as a regression test
against the invalid epoch advancement. I also had to fix several other tests.

This bug is caused by the batch queue advancing to the next epoch prior to
having the full sequence window for that epoch. This occurs when auto generating
batches. Once it has generated all of the batches for the current epoch, it
creates the first batch of the next epoch before it should.

Note: I had to remove the assumption that the epoch of the safe head is
the same as the epoch inside the batch queue. This is not true when generating
the last batch of an epoch. We can advance the batch queue, but we don't
generate a safehead with the new origin.

op-chain-ops: do not allow 0 scalar

bedrock: hardcode L2 genesis coinbase

op-chain-ops: make the migrated withdrawals version 0

The `DeployConfig` value for the `GasPriceOracleScalar` should
not be allowed to be set to 0. If it is set to 0, it would effectively
make the L1 portion of the fee nothing. This isn't useful since
eip1559 is enabled which required ether to be burnt with
execution, meaning that free transactions are not allowed
on the network.

If this value is set to 0, it is most likely a bug in the config
and we do not want to lose money by charging no L1 portion of the
fee.

Ensure that the `DeployConfig.Check` function checks for
the existence of the `L1StartingBlockTag`. This check was
previously being done outside of the `Check` function.
Also remove a check for the L2 genesis gas limit being
non zero since this is being done inside of `Check`.
Also add some better error messages in the case of bad
deploy config parsing.

Removes the config option for being able to set
the coinbase of the bedrock transition block.
It is now always set to the sequencer fee vault
predeploy. This is one less config option that needs
to be set correctly. The coinbase is always set to
the sequencer fee vault in bedrock blocks.

Updates the CrossDomainMessenger base contract to check for relayed
legacy messages. We originally specified that only unrelayed messages
would be migrated as part of the bedrock migration, but we recently
changed this to migrate all messages. As a result, we have to
reintroduce checks into the CrossDomainMessenger contracts to block
legacy messages that have already been relayed from being relayed again.

Update the migrated withdrawals to be version 0 based
on the new scheme that is introduced in https://github.com/ethereum-optimism/optimism/pull/4562.
This is a safety measure to ensure that withdrawals cannot
be double withdrawn and that ether stuck in the L1xdm cannot
be stolen in the case of a withdrawal with value reverting.

contracts-bedrock: deterministic storage

Makes the storage slot deterministic for the unsafe
block signer. This is useful because the `op-node` uses
a storage proof to fetch the value, so the `op-node` can
compute the storage slot value locally. This decouples
the way that `solc` lays out storage from the network policy,
making bugs less likely to happen when changing the contracts.