Repository navigation
Closed
3 / 33 of 3 issues completed
Copy link
Description
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-ethereumdependency 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 theOptimismstruct from the produced go-ethereumChainConfig(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/messagesswitchesparams.InteropCrossL2InboxAddress(fork const) toop-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, theopgeth-ratchetCI job (incl. itsci-gateentry and upstream-module cache), thejust opgeth-ratchet/opgeth-ratchet-updaterecipes, and the ratchet notes inAGENTS.mdanddocs/ai/go-dev.md. - Verify
go build ./...andgo test ./.... - Update
CLAUDE.md/AGENTS.mdpointer text (after this lands, the plan doc is historical reference).
Dependencies
Blocked on all other sub-issues, notably:
- opgeth-decoupling: swap call-sites to op-core/* across op-node, op-service, op-batcher #20263, opgeth-decoupling: make op-service/sources the OP-aware eth client #20264, opgeth-decoupling: migrate tests (op-e2e L2 call sites, wait.go split, delete op-e2e/opgeth, audit op-devstack/sysgo) #20265 — call-site swaps, OP-aware sources client, test migration.
- op-reth-test-engine: minimal in-test EL for op-e2e/actions (and Rust action-test parity) #20415 + opgeth-decoupling: migrate op-e2e/actions onto op-reth-test-engine (subprocess EL) #21196 — op-e2e/actions track (hard prerequisite).
op-e2e/actionsembeds op-geth in-process; flipping go.mod before it lands would silently re-resolve those imports to upstream go-ethereum with incorrect OP EVM behaviour. - opgeth-decoupling: run all op-deployer scripts on upstream forge; delete op-chain-ops/script #23300 — run all op-deployer scripts on upstream forge; delete op-chain-ops/script (replaces the closed opgeth-decoupling: replace op-chain-ops/script's op-geth EVM with a Rust script engine #21743).
op-chain-ops/scriptdepends on fork-only EVM hooks; no module-split escape hatch (any in-repo module still on op-geth keeps the fork maintained, defeating the epic's purpose). - opgeth-decoupling: retire the in-process op-geth L2 EL in op-e2e system tests and op-devstack/sysgo #21744 — op-reth-only L2 EL in op-e2e system tests + sysgo (otherwise the flip silently runs upstream geth as the L2 EL with wrong OP semantics — no compile error to warn).
- opgeth-decoupling: own the log layer; re-home the RPC metrics hooks #21745 — foundations: own the log layer + re-home the RPC recorder (fork log/rpc extensions break the whole tree at flip time).
- opgeth-decoupling: check-* fork tools — delete stale checkers, swap the rest to op-core #21746 (check-*), opgeth-decoupling: delete op-wheel's cheat commands (op-geth datadir surgery) #21747 (op-wheel/cheat), opgeth-decoupling: migrate op-chain-ops/genesis to build against upstream go-ethereum #21281 (genesis), opgeth-decoupling: delete op-simulate and op-run-block #21282 (op-simulate/op-run-block deletion), opgeth-decoupling: op-sync-tester — reimplement the OP-aware PayloadID hash (drop op-geth miner) #21525 (sync-tester PayloadID).
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
Metadata
Metadata
Assignees
Labels
No labels
Activity
fix(op-deployer): keep PV ABI shape until PR 2
refactor: remove ProtocolVersions Go plumbing (ethereum-optimism#20441)
refactor: remove ProtocolVersions Go plumbing (ethereum-optimism#20441)
docs: keep §13 open for the devstack L2 ChainConfig and fix the flip …
sebastianst commentedon Nov 13, 2026
🤖 Fable says: One test assertion to change in the flip PR:
TestSpanBatchTxsRejectsDepositTxexpectsprotected 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 becomesfailed to decode tx. Added in #23864.opgeth-ratchet: type-check against the cutover target v1.17.10
opgeth-ratchet: type-check against the cutover target v1.17.10