Skip to content

opgeth-decoupling: remove op-program from the monorepo #20276

Closed

Description

@sebastianst

Part of #20266 → #20257. The plan excludes op-program from the decoupling because it depends on op-geth state execution (core/state, core/vm). The in-tree replacement lives at rust/kona (client + host). This issue tracks op-program's actual removal from the monorepo — a prerequisite for the final go.mod cutover (#20266) since op-program shares the monorepo's single go.mod.

Context

op-program has no separate go.mod — it's part of the root module, so it uses the same replace github.com/ethereum/go-ethereum => ... op-geth directive. As long as op-program is in the module, the cutover can't flip that directive.

External consumers (need migration first)

In-scope packages currently import op-program Go packages:

op-challenger (Go code):

  • op-challenger/game/fault/trace/super/provider_supervisor.go, provider_supernode.go → op-program/client/interop/types
  • op-challenger/game/fault/trace/cannon/provider.go → op-program/host/types, op-program/host/kvstore
  • op-challenger/game/fault/trace/utils/preimage.go → op-program/client/l1
  • (plus test files referencing the same packages)

op-devstack (runtime artefact references):

  • op-devstack/sysgo/add_game_type.go, superroot.go → op-program/bin/prestate-*.json paths
  • op-devstack/shared/challenger/challenger.go → op-program/bin/op-program binary path (used as the Cannon fraud-proof server)

Build configs:

  • Makefile, justfile, .golangci.yaml entries for op-program

Scope

  1. Relocate the Go packages op-challenger depends on. For each imported op-program subpackage, either move the relevant types to op-core/ (if stable and reusable) or fold the minimal needed surface into op-challenger itself. Packages to handle:
    • op-program/client/interop/types — interop message types
    • op-program/host/types — KV store types
    • op-program/host/kvstore — KV store impl
    • op-program/client/l1 — L1 preimage helpers
  2. Swap op-challenger imports to the new locations; remove op-program from its import graph.
  3. Update op-devstack runtime references to use kona artifacts (kona-host binary + prestate files) instead of op-program/bin/*. Blocked on kona reaching production-readiness for the Cannon fraud-proof server role. If not yet ready, leave a clear TODO rather than stale paths.
  4. Delete op-program/ from the repo.
  5. Remove op-program targets from Makefile, justfile, .golangci.yaml, and any CI workflows.
  6. Confirm go mod tidy cleanly drops op-program's transitive deps.

Dependencies

Out of scope

  • Further kona development beyond what's needed to replace op-program's roles.
  • Rewriting op-challenger's fault-proof logic — only the imports/paths change, not the algorithms.

🤖 Generated by Claude Code

Activity

  1. linked a pull request that will close this issuechore: remove op-program from the monorepo #21271on Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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