Skip to content

kona-node: document or resolve the interop local-safe and cross-safe delegated parity gap #23911

Open

Description

@einar-oplabs

Part of ethereum-optimism/protocol-team#545.

Under interop, op-node imports local-safe and cross-safe separately (#19330). Kona's delegated derivation copies the delegated safe head into both labels. The tracker requires this parity gap to be resolved or explicitly documented before #545 closes. It does not affect the non-interop test network.

Scope:

  • Document the current behavior and its consequences for interop deployments in the kona-node delegated derivation docs.
  • Decide whether Kona should import the two labels separately when the delegate exposes them; if so, implement it with a regression test, otherwise record the decision and the conditions under which it must be revisited.

Activity

  1. self-assigned this
    on Nov 4, 2026
  2. einar-oplabs commented on Nov 9, 2026

    @einar-oplabs
    ContributorAuthor

    Draft fix: #24005, stacked on #24004. Decision: import the two labels separately, as op-node's FollowSource does.

    • Local-safe head: drives the EL lookup, EL sync and reorgs.
    • Cross-safe head: moves the safe label, and the forkchoice safe hash, only when it advances it.
    • Before interop: both heads are the same block, so non-interop chains see no change.
    • Docs: the label behavior and the interop caveat are in the kona-node configuration docs (Derivation Delegation Arguments) and the --l2-follow-source help. Under interop, the source must verify cross-chain dependencies, since kona-node verifies none itself.
  3. einar-oplabs commented on Nov 11, 2026

    @einar-oplabs
    ContributorAuthor

    Claude: Status of #24005 at head 3c2d3be113 (2026-11-11)

    Implemented:

    • Local-safe and cross-safe are imported separately.
    • Only the unsafe head and established finality count as chain proof.
    • EL lookups happen only at or below the unsafe head, and only while the EL has applied the last forkchoice.
    • A catch-up keeps a safe label that the EL holds.
    • No reorgs while the EL has not applied the last forkchoice.
    • Inconsistent heads are rejected, and the local-safe L1 origin must be canonical.
    • Non-interop chains see no change.

    Checks: CI is green, and 703 unit tests pass.

    Open findings (Fable 5.1 xhigh, round 5):

    • The repair for an unsafe head below safe does not apply when the delegated local-safe head is at or below the unsafe head. The forkchoice update then carries head < safe and the engine resets.
    • During an unproven multi-block catch-up, missing EL evidence is treated as divergence, so safe can drop while the EL syncs.
    • A routine multi-block catch-up is handled as a reorg and logged at warn.
  4. added a commit that references this issue on Nov 19, 2026
    536e4f6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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