L2 data not reaching L1: blob submissions stalled or L2 finalizations not becoming L1-final
criticalmatched by component coordinator · reviewed 2026-10-13What it meansmoreThe coordinator conflates L2 blocks into batches, submits their data to L1 as blobs, and later submits finalization transactions with proofs. Blob submission stalled means conflation moves but no blob lands on L1; L1 finality gap means L2 finalizations land on L1 but the L1 blocks holding them do not become final. Causes seen: the L1 stalled or deadlocked (INC-15), the coordinator wedged, or the L2 web3signer could not sign (keys missing).
ImpactmoreNothing settles on L1: finalization, withdrawals and anchoring of L2 → L1 messages wait. SEV2 when it lasts over 20 minutes (settlement-freshness pages); check l1-chain-stalled first if the L1 itself is stuck.
Quick mitigation0/4
Diagnosis4 queries
Highest blob submitted on L1 and last conflated block, over the last hour:
max(linea_blob_highest_submitted_on_l1)max(linea_conflation_last_block_number)L2 finalized block as seen at the L1 latest and finalized tags:
max by (l1_block_tag) (lineth_l2_rollup_finalized_block)Coordinator submission errors:
{namespace="lineth-l2", pod=~"coordinator-.*"} |~ "(?i)blob|submission|nonce|insufficient|reverted"Fix0/2
Escalation
If no blob lands for an hour with the L1 and signer healthy, page the IC and collect the coordinator thread dump and logs before any further restart.
Seen in INC-2026-10-13-15, INC-2026-10-11-11 · SLOs settlement-freshness, withdrawal-1h · owner s1ns3nz0