Repository navigation
Description
Part of ethereum-optimism/protocol-team#545.
Summary
If kona-node's forkchoice update is answered SYNCING, the execution layer (EL) then finishes syncing, and no further unsafe payload arrives, kona-node never completes engine sync. It never resends the forkchoice update, so it never sees VALID and el_sync_finished stays false. The engine actor never reports sync completion. Under delegated derivation, the DelegateDerivationActor therefore never polls its source, and local-safe, safe and finalized stay at genesis. develop has the same behavior.
Evidence
CircleCI job 5859222 (memory-all-kona-op-reth-fusaka), test TestFollowL2_LabelsMatchELByHashWithSequencerPaused from #24007:
- The follow-source kona-node's op-reth logged
Received new payload ... number=7, thenReceived forkchoice updated message when syncing. - 16 ms later it logged
Canonical chain committed number=7, so its p2p sync had finished. - The sequencer stopped 2 s later. After that, op-reth logged no further
newPayloadorforkchoiceUpdatedfrom kona-node, and its status lines showlatest_block=7until the test ended four minutes later. - kona-node's local-safe stayed at 0 for 120 attempts, while the op-node sequencer and verifier reached local-safe 7.
The test passed while it waited for L2 finality before pausing: continued gossip produced a forkchoice update answered VALID.
Mechanism
- The insert task applies the unsafe head on a
SYNCINGreply. el_sync_finishedis set only by aVALIDforkchoice reply, insynchronize.- While
el_sync_finishedisfalse, nothing resends an unchanged forkchoice update: there is no timer, and no reset is triggered. - The engine actor marks sync complete only once
el_sync_finishedis set, and the delegate actor polls only after that.
Expected behavior / acceptance criteria
- While
el_sync_finishedisfalse, kona-node resends the unchanged forkchoice update on a bounded interval until the EL answersVALID. Compare with op-node's handling during initial EL sync. - Regression test with kona-engine and mocked Engine API responses: the first forkchoice update is answered
SYNCING, no further payloads arrive, and a later resend answeredVALIDcompletes engine sync. -
TestFollowL2_LabelsMatchELByHashWithSequencerPausedpasses under kona-node with the sequencer paused right after kona-node's first unsafe block. kona-node-service,op-acceptance-tests: exercise delegated derivation recovery end to end #24007 currently avoids that case by waiting for local-safe ≥ 1 before the pause.
Related
- ethereum-optimism/protocol-team#574: kona-node treats
SYNCINGas applied for unsafe payloads. - kona-node: missing L2 block during EL catch-up resets the engine in a loop #23931 / kona-engine: wait for EL sync instead of resetting on a missing consolidation block #24006: derived block missing during EL sync; kona-engine: wait for EL sync instead of resetting on a missing consolidation block #24006 resends the forkchoice update only for derived attributes.
- kona-node: verify delegated derivation parity against op-node #23912 / kona-node-service,op-acceptance-tests: exercise delegated derivation recovery end to end #24007: the verification that exposed this.
Activity
kona-node-service,op-acceptance-tests: share the scripted delegate an…
joshklop commentedon Nov 11, 2026
is this the same as Is this the same as https://github.com/ethereum-optimism/protocol-team/issues/681?