Skip to content

op-e2e/actions: build Amsterdam L1 blocks in the action-test L1 miner #24177

Open

Description

@sebastianst

The action-test L1 miner builds L1 blocks itself with go-ethereum's block-processing functions: op-e2e/actions/helpers/l1_miner.go.

From Amsterdam on, an L1 block carries a block access list (EIP-7928) and a slot number. The miner builds neither. With the cutover to upstream go-ethereum (#24176) it fails with an explicit error when Amsterdam is active on L1, so no action test can run on an Amsterdam L1.

No action test activates L1 Amsterdam today.

Task

  • Build the block access list while the miner applies transactions and system calls, and set the header fields Amsterdam adds.
  • Add an action test that runs on an Amsterdam L1, e.g. a batch submission and its derivation.
  • Decide which L1 fork the action tests run on by default. Today every action test's L1 is at Osaka from genesis, without the BPO forks, which is behind mainnet. The default should follow the latest fork that is live or scheduled on mainnet, so that the tests stay realistic; Amsterdam becomes that default once the miner can build its blocks.

🤖 Co-created with Claude Fable 5.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions