Skip to content

opgeth-decoupling: migrate the kona proof harness off the in-process op-geth L2 EL #21905

Closed
3 of 3 issues completed

Description

@sebastianst

Part of #20257 (see also #20415/#21196). Blocks #20266 — after #21787 lands, this harness is the last in-process op-geth L2 EL consumer in the tree.

Finding

op-geth has no debug_executePayload. Today kona-host therefore gets every L2 state node through its fine-grained debug_dbGet fallback against op-geth's hashdb (see the retry loop and L2StateNode). reth can't serve that, because its debug_dbGet returns contract code only.

Production op-reth serves the witness via debug_executePayload. The sysgo proof acceptance tests already run kona-host against it: sysgo starts op-reth with the debug API enabled, and superfaultproofs runs kona-host. The port moves the harness onto that production path.

  • Missing test-engine methods: debug_getRawHeader, debug_getRawReceipts, debug_executePayload and debug_dbGet (code form). It already serves the eth_ reads kona-host uses.
  • No HTTP listener needed: kona-host dials the engine's Unix socket over IPC.
  • One state-access user: the pre-fork state generator (just nut-prefork-state-for, StateAt). It needs a new optest_dumpAccounts. The harness's other reads map onto existing eth RPC.

Plan

Risk

A state node outside the witness falls back to raw-hash debug_dbGet, which reth can't serve. kona-host then retries forever, and the test hangs until the Go timeout. Production op-reth would hit the same gap. Add a harness-side timeout so it fails fast.

Acceptance

  • rust/kona/tests/proofs runs against the reth test engine; op-e2e/e2eutils/gethengine deleted; no in-process op-geth L2 EL constructor remains in the tree.

🤖 Co-created with Claude Opus 5.5

Activity

  1. self-assigned this
    on Oct 13, 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