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: keep delegated finalization pending during EL catch-up #23675
Delegated derivation can terminate Kona during ordinary execution-client catch-up. This is the catch-up liveness scope of the delegated derivation parity tracker.
Reproduction
Local unsafe=20, safe=10, finalized=0; delegate reports safe=30, finalized=15.
Consolidation requests the new forkchoice; the EL returns SYNCING.
FinalizeTask fetches finalized block 15 by hash. The local EL has not downloaded it yet and returns null.
BlockNotFound is classified Critical and propagates out of the engine actor, stopping the node.
An honest upstream can trigger this. It was reproduced with actual kona-engine tasks and mocked Engine API responses, not a live EL outage.
Draft fix: #23908. It follows up on the closed #23678 with a fresh implementation. A pinned finalized target that the EL has not downloaded yet, or that sits above the local safe head, is skipped without a forkchoice update and resubmitted by the next delegate poll, so the node no longer stops during catch-up. Pinned lookups now reject a returned block whose hash or number differs (BlockIdentityMismatch), and by-number finalization still fails hard.
Activity
einar-oplabs commentedon Nov 4, 2026
Draft fix: #23908. It follows up on the closed #23678 with a fresh implementation. A pinned finalized target that the EL has not downloaded yet, or that sits above the local safe head, is skipped without a forkchoice update and resubmitted by the next delegate poll, so the node no longer stops during catch-up. Pinned lookups now reject a returned block whose hash or number differs (
BlockIdentityMismatch), and by-number finalization still fails hard.