Skip to content

kona-node: execution-layer sync parity with op-node #24100

Open
1 of 4 issues completed
Open

Description

@einar-oplabs

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).

  • WillStartEL skips EL sync when the EL already has a non-genesis finalized block and the engine kind does not support post-finalization EL sync.
  • FinishedELButNotFinalized sets the safe and finalized heads with headsAfterELSync. 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

Before EL sync completes

EL-sync completion

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 SYNCING as 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 SYNCING on build

Acceptance coverage

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 sends finalized_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's EngineKind::supports_post_finalization_elsync is deprecated and unused, so kona-node always EL-syncs. Decide whether kona-node needs this, given op-geth's deprecation.
  • SYNCING after initial EL sync. In execution-layer mode, op-node still accepts SYNCING on unsafe inserts and plain forkchoice updates after EL sync finishes. In consensus-layer mode it does not. The target behavior for Version Packages #681 depends on which mode kona-node matches.

Related

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