Incident Overview: Two Outages Totaling 136 Minutes
According to a ChainCatcher report, Base has published a post-mortem analysis of two block production interruptions on its mainnet that occurred on June 25 and 26, lasting 116 minutes and 20 minutes respectively. The report confirms that on-chain assets remained secure throughout both incidents, with user funds always in a safe state.
Root Cause: Stale Journal State in Sequencer Block Construction
The root cause was traced to a logic flaw in the sequencer's block construction logic. Specifically, after a transaction execution failed, the old journal state was not properly cleared, causing subsequent valid transactions to encounter gas calculation errors. This led to the generation of invalid state transition blocks, halting the entire L2 chain. The vulnerability is a classic "stale state" issue, which is rare in Ethereum layer-2 sequencer implementations but can cripple network operation when triggered.
Base operates on the OP Stack architecture, where the sequencer is responsible for bundling L2 transactions and submitting them to Ethereum L1. This incident highlights the insufficient defense in the sequencer's handling of abnormal transaction execution paths and underscores the importance of robust transaction simulation and state rollback mechanisms in L2 infrastructure.
Fix and Future Enhancements
Base has already deployed a patch to fully resolve the issue. To prevent recurrence, the team will enhance protocol-level fuzz testing and stress testing systems to identify potential malicious transaction paths. Operational monitoring and maintenance processes will also be optimized. Additionally, Base plans to introduce an automated recovery mechanism to improve rapid resilience in future similar events, minimizing the impact on user and developer experience.
Although the downtime was prolonged, the absence of any asset loss underscores Base's emphasis on fund safety in its design. However, the centralization risk introduced by the sequencer remains a critical area for improvement within the OP Stack ecosystem, and this event serves as a timely reminder of the need for ongoing security hardening.