You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
kona-node: validate a stale delegated snapshot whose safe head is below local finalized #23910
A complete stale upstream snapshot can report a safe head below Kona's local finalized head. The finalized-monotonicity fix (#23677) protects the finalized label only: it does not validate or clamp an earlier delegated safe update that sits below local finalized, so Kona can still adopt a safe head that is behind its own finality. The tracker lists this as a pre-existing ordering question outside the three core fixes, and it must not be described as resolved by them.
Scope:
Reproduce with Kona engine tasks and mocked Engine API responses: local unsafe > safe > finalized, delegate reports safe < local finalized.
Decide the policy (reject, clamp to finalized, or accept with a warning) by comparing with op-node's follow-source handling, and implement it.
Regression test asserting the chosen behavior and that finalized never moves backward as a side effect.
Claude: Status of #24004, head 50000d6358 (2026-11-11)
Implemented
The delegate actor drops a status whose labels are out of order. A zero local-safe head counts as unreported.
The delegate actor also drops a status that breaks the engine's applied finality.
The engine skips a delegated safe head that is below established finality or conflicts with it.
A delegated safe head below the engine's safe head is ignored. It is forwarded once per engine view, unless an EL that applied the last forkchoice holds a different block at that height. That proves divergence, and the engine reorgs onto the delegate's chain above finality.
Labels left with the unsafe head below the safe head are repaired by the next delegated head above finality.
Checks: CI green except contracts-bedrock-upload, which hit a GitHub 503 while resolving the target branch; it was rerun. 663 unit tests pass.
Open findings (Fable 5.1 xhigh, round 5)
The lagging-head dedup is not cleared on reset. A diverged head dropped by a reset is never resent.
While the EL has not applied the last forkchoice, a mismatching head moves only the safe labels. That can publish a safe head that is not an ancestor of the unsafe head.
The build task's forkchoice update does not maintain el_applied_last_forkchoice.
A lagging head sends no forkchoice update, so an EL that lost its safe or finalized labels keeps them stale.
Activity
einar-oplabs commentedon Nov 9, 2026
Draft fix: #24004, stacked on #23947.
followUpstreamdoes.L2BlockRefAdvances.einar-oplabs commentedon Nov 11, 2026
Claude: Status of #24004, head
50000d6358(2026-11-11)Implemented
Checks: CI green except
contracts-bedrock-upload, which hit a GitHub 503 while resolving the target branch; it was rerun. 663 unit tests pass.Open findings (Fable 5.1 xhigh, round 5)
el_applied_last_forkchoice.