Skip to content

opgeth-decoupling: final cutover (flip go.mod to upstream go-ethereum) #20266

Closed
3 of 3 issues completed

Description

@sebastianst

Part of #20257. The last step after all other sub-issues land.

Goal

Remove the op-geth replace directive from go.mod; clean up any remaining shims or transitional code.

Scope

  • Remove from go.mod: replace github.com/ethereum/go-ethereum => github.com/ethereum-optimism/op-geth vX.Y.Z.
  • Update the direct github.com/ethereum/go-ethereum dependency to the target upstream version.
  • Run go mod tidy; resolve any residual import issues.
  • Remove ALL op-core differential tests (types, fees, params, sync-tester PayloadID) and the §2 transaction-helper scaffolding — no longer meaningful without op-geth as a comparison point.
  • op-core/params.GethChainConfig() sheds the OP fork fields and the Optimism struct from the produced go-ethereum ChainConfig (they only exist on the fork).
  • Before the flip, audit every remaining GethChainConfig() / GethGenesis() call: after it, they yield a config with only the Ethereum fork schedule, and the ratchet can't see what that changes. A call may only rely on Ethereum-semantics results (genesis state root, header hashing, fork-schedule encoding). Anything that builds or executes blocks, transactions or precompiles, or computes fee or EIP-1559 values with it, moves to op-reth or op-core first (e.g. opgeth-decoupling: return opparams.ChainConfig from op-devstack's L2 ChainConfig() #23655).
  • op-core/interop/messages switches params.InteropCrossL2InboxAddress (fork const) to op-core/predeploys.
  • Flip the log-layer alias to the owned interface (opgeth-decoupling: own the log layer; re-home the RPC metrics hooks #21745 phase 2).
  • Update CI / build configs that referenced op-geth.
  • Remove the CI ratchet (opgeth-decoupling: CI ratchet — required upstream type-check against a shrinking allowlist #21748, ops: add an op-geth decoupling ratchet check #23407): the ops/scripts/opgeth-ratchet/ tool and its allowlist, the opgeth-ratchet CI job (incl. its ci-gate entry and upstream-module cache), the just opgeth-ratchet / opgeth-ratchet-update recipes, and the ratchet notes in AGENTS.md and docs/ai/go-dev.md.
  • Verify go build ./... and go test ./....
  • Update CLAUDE.md / AGENTS.md pointer text (after this lands, the plan doc is historical reference).

Dependencies

Blocked on all other sub-issues, notably:

The CI ratchet (#21748) is the readiness gauge: this issue is executable exactly when the ratchet allowlist is empty; the flip PR deletes the ratchet (see the scope item above).

🤖 Generated by Claude Code

Activity

  1. self-assigned this
    on Oct 27, 2026
  2. sebastianst commented on Nov 13, 2026

    @sebastianst
    MemberAuthor

    🤖 Fable says: One test assertion to change in the flip PR: TestSpanBatchTxsRejectsDepositTx expects protected tx has chain ID 0, but expected chain ID 1, because op-geth decodes the deposit and the span batch encoder then rejects it at the chain-ID check. Upstream go-ethereum does not decode a deposit, so the expected error becomes failed to decode tx. Added in #23864.

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