Lisk mainnet derivation gap bug

Incident Report for Lisk

Resolved

A combination of two bugs in our rollup stack caused L2 blocks 31997343..31999643 to be omitted from L1 batch submissions. As a result, L1-based verifier derivation cannot process the subsequent batch starting at
block 31999644.

Current status
- The L2 chain remains live and continues to produce blocks; sequencer-facing transactions are unaffected.
- Full nodes are currently operational.
- Archival nodes are not operational at this time; recovery is in progress via EL sync.
- No user funds, balances, or transaction state are at risk.

Root cause
1. op-node’s EL-sync completion path marked an unsafe block as safe/finalized prior to L1 confirmation.
2. The batcher trusted the resulting local safe label without cross-checking against the latest confirmed L1 batch range.

Posted May 14, 2026 - 08:00 UTC