The team behind the Ethereum layer-2 solution Base has presented a detailed analysis of two consecutive network outages that occurred on June 25 and 26. The cause of the block production halt was a critical bug in the sequencer logic, which led to a violation of chain integrity.

The first incident lasted 116 minutes, the second 20 minutes. In both cases, the network stopped producing new blocks, transactions ceased to be confirmed, and the queue of unconfirmed operations became full. Users encountered errors when submitting new transactions, but funds remained safe — the team emphasizes that client assets were not affected.

Technical Background of the Outages

According to the report, the problem arose after processing a transaction that ended 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 rejected. As a result, block production came to a complete halt.

After installing the fix, developers encountered a race condition when restarting the sequencer cluster. This secondary error prevented the nodes from synchronizing quickly, which caused the second, shorter outage the following day.

Action Plan: From Testing to Architecture

In response to the incidents, the Base team announced a significant enhancement of stress testing and protocol fuzzing. The goal is to proactively identify non-standard transaction processing scenarios that could lead to similar failures. Additionally, developers plan to improve network monitoring and implement a graceful recovery mechanism, which will allow the network to resume operations more quickly after emergency stops.

Recall that in February, Base announced a transition from the Optimism technology stack to its own unified network architecture. This step likely increases risks associated with new components, but simultaneously gives the team greater control over performance and security.

Expert opinion: Two outages in two days is an alarming signal for a network striving for mass adoption. Although user funds were not affected, the frequency of incidents undermines trust in L2 solutions. Strengthening testing and implementing a graceful recovery mechanism are logical steps, but it is critically important for Base to accelerate code audits and implement automated monitoring systems capable of preventing such failures before they manifest on the mainnet.