Skip to content

opgeth-decoupling: swap eip1559 + superchain + fees imports; delete op-service/superutil #20271

Closed
2 of 2 issues completed

Description

@sebastianst

Part of #20263 → #20257. See plan §4, §7, §8 in the op-geth decoupling doc.

Scope

The op-core packages these swaps depend on are all landed: #20267 (op-core/superchain), #20268 (op-core/eip1559), #20261 (op-core/fees) — all closed.


Note on sync-superchain prerequisites (added during #20314 review)

Resolved in #21485. When op-core/superchain is swapped in, op-node and ~13 other binaries start embedding superchain-configs.zip (gitignored) at compile time. Rather than auditing every just recipe and Dockerfile individually (the original plan below), #21485 regenerates the zip inside the shared op-stack-go Docker builder stage from the superchain-registry submodule data, git-free, verified against the committed .sha256; the justfile build-go/CI prerequisites are wired there too.

Original audit note (superseded)
  • just recipes: every recipe that builds Go code importing op-core/superchain (op-node, op-batcher, op-proposer, op-challenger, op-supernode, op-faucet, etc.) needs sync-superchain as a prerequisite. Right now those recipes are: op-node, op-batcher, op-proposer, op-challenger, op-program-client, op-program-host, cannon-prestates, make-pre-test, op-program, etc. Audit each in justfile and add sync-superchain to the prereq list.
  • Docker builds: any Dockerfile that runs go build ./... or builds a binary that links op-core/superchain needs the zip in its build context. Either:
    • Run just sync-superchain in the Dockerfile before go build, or
    • Bake the zip into the build context (rebuild the image when the pinned commit bumps).
    • Audit op-batcher/Dockerfile, op-node/Dockerfile, op-proposer/Dockerfile, op-challenger/Dockerfile, op-conductor/Dockerfile, op-supernode/Dockerfile, op-faucet/Dockerfile, plus the OP_STACK_GO_BUILDER upstream image.

🤖 Generated by Claude Code

Metadata

Metadata

Assignees

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