The team behind the Ethereum L2 solution Base has released a detailed report on two consecutive network outages that occurred on June 25 and 26. During the incidents, a complete halt in block production was observed, leading to temporary network unavailability. The cause was a critical bug in the sequencer logic.
The first outage lasted 116 minutes, the second — 20 minutes. During this period, blocks were not produced, transactions were not processed, and the queue of unconfirmed operations overflowed, causing errors for users when submitting new requests. It is important to emphasize: user funds were not affected and remained secure throughout the incidents.
Root of the Problem
According to the analysis, the error occurred after the unsuccessful processing of one transaction. The sequencer did not clear the temporary state (journal state), leading to an incorrect calculation of the fee for the next valid transaction. As a result, a block with an invalid state transition was formed, which was rejected by the other network nodes. This caused a complete halt in block production.
After applying the first fix, developers encountered a recurring issue: a race condition during the restart of the sequencer cluster prevented nodes from synchronizing quickly. This led to a shorter but repeated outage the following day.
Strengthening Plans
In response to the incidents, the Base team announced a significant enhancement of stress testing and the introduction of protocol fuzzing. This will allow for the early detection of non-standard transaction processing scenarios that could lead to similar outages. Additionally, plans include improving network monitoring and implementing a graceful recovery mechanism to speed up the network's return to normal operation after emergencies.
Recall that in February, the Base team announced a transition from the Optimism technology stack to its own unified network architecture. This step undoubtedly provides more control but also requires more thorough testing of all components.
My expert assessment: Two consecutive outages in one network are a serious signal. Although user funds were not affected, such incidents undermine trust in L2 solutions, which are supposed to ensure high availability. The transition to a proprietary architecture requires time and resources, and these outages show that the debugging process is far from complete. Investors should closely monitor further protocol improvements before increasing activity on the Base network.