Base Mainnet Postmortem: Sequencer State Management Bug Causes Two Block Production Outages

Base Mainnet Postmortem: Sequencer State Management Bug Causes Two Block Production Outages

N
News Editor
2026-06-28 01:09:20
Base experienced two block production outages on June 25 and 26, 2026, lasting approximately 116 minutes and 20 minutes respectively. The official postmortem report identifies the root cause as a sequencer state management bug: after a failed transaction execution, the system failed to clean up historical journal state, leading to anomalous gas calculation and invalid state transition blocks. Base has deployed fix PR #3806 and plans to enhance fuzzing, stress testing, and recovery mechanisms. User funds remained safe throughout.
Basemainnet outagesequencerstate managementpostmortemL2block production

Outage Overview: Two Incidents, Impact and Duration

According to Base's official postmortem, the Base mainnet suffered two block production outages on June 25 and 26, 2026. The first outage lasted approximately 116 minutes, the second about 20 minutes. The team confirmed that user assets and on-chain data remained safe and accessible at all times, with no funds at risk.

Root Cause: Sequencer State Management Flaw

The core issue was a defect in the sequencer's block construction logic. After a transaction execution failure, the system failed to properly clean up historical journal state. This caused subsequent valid transactions to encounter gas computation anomalies, generating invalid state transition blocks and halting the entire L2 network. During the outage, users experienced complete block production cessation, inability to submit transactions, and mempool congestion, with eth_sendRawTransaction calls continuously returning errors.

Fix and Future Improvements

Base deployed a fix via PR #3806, cleaning up the journal state issue and resuming block production. However, a race condition during the sequencer cluster restart hindered synchronization, indirectly contributing to the second outage the following day. Going forward, Base plans to strengthen protocol-level fuzz testing and stress testing to detect abnormal transaction paths earlier. It will also upgrade monitoring and operations tooling and introduce a more graceful recovery mechanism to improve resilience against similar failures.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
400

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.