The team behind the Ethereum L2 solution Base has published a detailed report on two consecutive network outages that occurred on June 25 and 26. Both incidents led to a complete halt in block production, causing an overflow of the unconfirmed transaction queue and widespread errors for users when submitting operations.

The first outage lasted 116 minutes, the second 20 minutes. In both cases, user funds remained safe, but the situation itself exposed a critical vulnerability in the sequencer's operational logic.

Root of the Problem: Bug in State Handling

According to the report, the root cause was a failed processing of one transaction. The sequencer did not clear the temporary state (journal state) after the error, causing the next valid transaction to receive an incorrect fee calculation. This led to the formation of a block with an invalid state transition, which the other network nodes could not accept. As a result, block production completely stopped.

After applying the first fix, developers encountered an additional problem — a race condition during the restart of the sequencer cluster. This prevented nodes from quickly synchronizing and caused the second, shorter outage the following day.

Plans to Strengthen Infrastructure

In response to the incidents, the Base team announced several key changes. First, stress testing and protocol fuzzing will be significantly enhanced to identify non-standard transaction processing scenarios at early stages. Second, the network monitoring system is planned to be improved. Third, developers intend to implement a "graceful recovery" mechanism that will allow the network to resume operation more quickly after such failures.

Recall that in February of this year, Base announced a transition from the Optimism technology stack to its own unified network architecture. It is evident that the migration process and adaptation of new code require increased attention to testing quality.

Analytical Commentary: Such incidents are a warning signal for the entire L2 ecosystem. Base is one of the largest second-layer solutions, and its stability is critically important for user trust. The fact that the problem arose from a trivial error in state clearing logic indicates the need for deeper code auditing and the implementation of formal verification, not just fuzzing. If the team does not accelerate the adoption of automatic recovery mechanisms, similar outages could recur at the most inopportune moment.