L2 web3signer has fewer than 4 keys loaded

Probable cause web3signer-l2

Detected
Declared
Mitigated
Resolved
Closed

Close blocked: 1 follow-up without an issue

33m

to resolve

alerts, all cleared

0/19

checklist

—

next update

acked 60s

paging

L2 data not reaching L1: blob submissions stalled or L2 finalizations not becoming L1-final

criticalmatched by component web3signer-l2 · reviewed 2026-10-13

What 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).

Impactmore

Loading…