The team behind the Ethereum Layer-2 solution Base has published a report on two incidents that occurred on June 25 and 26, which led to a halt in block production. The cause was a bug in the sequencer logic related to incorrect transaction processing.

The first outage lasted 116 minutes, and the second lasted 20 minutes. During this period, the network stopped producing new blocks, transactions were not included in the blockchain, and the queue of unconfirmed operations became overloaded, causing users to encounter errors when sending new transactions. It is important to emphasize: user funds remained safe and were not affected.

Incident Details

The problem arose after one transaction completed with an error. The sequencer did not clear the temporary state (journal state), causing the next correct 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, completely halting block production.

After applying the fix, developers encountered a second error — a "race condition" when restarting the sequencer cluster, which prevented nodes from synchronizing quickly. This was the cause of the second, shorter outage the following day.

Improvement Plans

Following the incident, the Base team pledged to enhance stress testing and protocol fuzzing to proactively identify non-standard transaction processing scenarios. They also plan to improve network monitoring and implement a "graceful recovery" mechanism to restore network operations more quickly after such failures.

Recall that in February, the Base team announced a transition from the Optimism technology stack to its own unified network architecture, which likely contributed to instability during the early stages of implementation.

My analysis: Such incidents are an inevitable part of the evolution of L2 infrastructure. Although the outage caused temporary inconvenience, the team's swift response and transparent report strengthen trust in the project. However, users should consider that any transition to a new architecture carries risks, and I recommend diversifying assets across multiple L2 solutions until Base fully stabilizes.