Repository navigation
Description
Claude: Tracker for what kona-node needs in order to match op-node's execution-layer (EL) sync. Tickets on the op-node deprecation board already cover parts of it. This issue groups them and lists the gaps that have no ticket yet.
Background
op-node has two sync modes, selected by --syncmode (default consensus-layer). In execution-layer mode, its engine controller moves through these statuses in order: WillStartEL → StartedEL → FinishedELButNotFinalized → FinishedEL (op-node/rollup/engine/engine_controller.go).
WillStartELskips EL sync when the EL already has a non-genesis finalized block and the engine kind does not support post-finalization EL sync.FinishedELButNotFinalizedsets the safe and finalized heads withheadsAfterELSync. If the SafeDB tip is canonical, it resumes from that tip. Otherwise it places both heads--syncmode.offset-el-safe(default 12h) behind the synced tip.
kona-node has a single model. Derivation waits in AwaitingELSyncCompletion until the EL first answers a forkchoice update with VALID. The status is spread across booleans in EngineState and EngineActor. kona-node has no --syncmode flag, no EL-sync completion step and no unsafe-payload queue.
Sub-issues
Sync-mode model
- ethereum-optimism/protocol-team#631 CL-sync mode (
--syncmode=consensus-layer) - kona-engine: model EL sync status as an explicit state instead of booleans #24099 model EL sync status as an explicit state instead of booleans
Before EL sync completes
- kona-node: resend the forkchoice update until the EL answers VALID after an initial SYNCING #24030 resend the forkchoice update until the EL answers
VALIDafter an initialSYNCING - kona-node: missing L2 block during EL catch-up resets the engine in a loop #23931 a missing L2 block during EL catch-up resets the engine in a loop
- ethereum-optimism/protocol-team#634 the EL head behind its finalized block crash-loops the engine reset
EL-sync completion
- ethereum-optimism/protocol-team#590 completion step: port
headsAfterELSyncand--syncmode.offset-el-safe - kona-node: finalized head does not leave genesis after an EL datadir wipe #24066 the finalized head does not leave genesis after an EL datadir wipe
- kona-node,safedb,gap-detection: resume derivation from the canonical SafeDB tip after EL sync #23658 resume derivation from the canonical SafeDB tip after EL sync (deferred)
- ethereum-optimism/protocol-team#589 engine-reset head selection differs from
FindL2Heads. EL-sync completion runs a reset today.
Unsafe payloads during and after EL sync
- ethereum-optimism/protocol-team#574 unsafe-payload queue and stalled-head gap fill
- ethereum-optimism/protocol-team#681 unsafe inserts treat
SYNCINGas applied after initial EL sync - ethereum-optimism/protocol-team#601 a persistently failing insert blocks the engine queue
- ethereum-optimism/protocol-team#641 sequencer backoff when the EL reports
SYNCINGon build
Acceptance coverage
- op-acceptance-tests: run TestELSyncSafeRetractedByOffset against kona-node #23828
TestELSyncSafeRetractedByOffset - op-acceptance-tests: run TestUnsafeGapFillAfterSafeReorg against kona-node #22275
TestUnsafeGapFillAfterSafeReorg - op-acceptance-tests: run TestUnsafeGapFillAfterUnsafeReorg_RestartL2CL against kona-node #22276
TestUnsafeGapFillAfterUnsafeReorg_RestartL2CL - op-acceptance-tests: run TestUnsafeGapFillAfterUnsafeReorg_RestartCLP2P against kona-node #22277
TestUnsafeGapFillAfterUnsafeReorg_RestartCLP2P - op-acceptance-tests: run TestSDMPostExecBlockDerivesOnIsolatedVerifier against kona-node #22271
TestSDMPostExecBlockDerivesOnIsolatedVerifier(needs CL-sync mode)
Open questions without a ticket
- Finalized hash in forkchoice updates. During initial EL sync, op-node leaves the finalized hash out of forkchoice updates (
tryUpdateEngineInternal,insertUnsafePayload). kona-node always sendsfinalized_head(EngineSyncState::create_forkchoice_state). The impact has not been assessed. - Skipping EL sync for op-geth. op-node skips EL sync when the EL has a non-genesis finalized block and
--l2.engine-kind=geth. kona'sEngineKind::supports_post_finalization_elsyncis deprecated and unused, so kona-node always EL-syncs. Decide whether kona-node needs this, given op-geth's deprecation. SYNCINGafter initial EL sync. Inexecution-layermode, op-node still acceptsSYNCINGon unsafe inserts and plain forkchoice updates after EL sync finishes. Inconsensus-layermode it does not. The target behavior for Version Packages #681 depends on which mode kona-node matches.
Related
- ethereum-optimism/protocol-team#545 delegated derivation parity. Covers EL catch-up on the delegated path: kona-node: keep delegated finalization pending during EL catch-up #23675, kona-node: reliably deliver and retry delegated forkchoice updates #23676, kona-node: recover when the EL rejects a delegated forkchoice update #24061.
- ethereum-optimism/protocol-team#101 inventory of acceptance-test skips.
Activity