Jovian + Karst: Consensus influencing event nonces [TRACKER]

[mdehoog]

Overview

This is a tracking issue for ethereum-optimism/specs#330 (comment), which introduces a nonce for L1 events that affect consensus (SystemConfig.ConfigUpdate and OptimismPortal2.TransactionDeposited).

Design doc PR: ethereum-optimism/design-docs#182
Design review issue: ethereum-optimism/design-docs#183

Rollout plan

1. Jovian: introduce change in op-node / op-program / Kona to accept ConfigUpdate and TransactionDeposited for both version 0 and 1. Version 1 will also contain an incrementing nonce in the upper 128-bits of the version argument. Also update the L1Block contract to track these nonces on the L2.
2. Between Jovian + Karst: roll out contract upgrades to SystemConfig and OptimismPortal2 that introduce this new version 1 events with the nonce.
3. Karst: remove support for version 0 events, requiring incrementing nonces going forward. This guarantees that nonces are available, allowing for simplification of the derivation pipeline by supporting skipping L1 blocks that contain none of these events.

Step 1 TODOs (Jovian):

• Specs: [Jovian] Add specs for consensus event nonces (deposits + config changes) specs#487
• Implementation:
  • [WIP] L1 nonce for consensus events (deposits + config updates) #13539
  • Add support for the new Jovian block info tx op-geth#457

Step 2 TODOs (contract upgrades):

• Devnet rollout
• Testnet rollout
• Mainnet rollout

Step 3 TODOs (Karst):

• Specs: WIP
• Implementation: WIP

[mslipper]

Closing this out for now - I don't think we'll be implementing this for the time being. Will reopen if I receive guidance otherwise.