Review of two brief outages on Base mainnet: Sequencer state management bug caused block production interruption.

robot
Abstract generation in progress
ME News: On June 28 (UTC+8), Base released a post-mortem report stating that the mainnet experienced two block production interruptions on June 25 and 26, lasting approximately 116 minutes and 20 minutes respectively. The official emphasized that the incident did not affect on-chain asset security and user funds were always accessible. The root cause of the failure was a flaw in the sequencer's block construction logic: after a transaction execution failure, the system failed to properly clean up the historical journal state, causing abnormal gas calculation during subsequent legitimate transaction executions, thereby generating invalid state transition blocks and halting block production on the entire L2 network. During the interruption, the network experienced issues including complete cessation of block production, inability to submit transactions to the chain, and mempool congestion, with user-submitted eth_sendRawTransaction requests continuously returning errors. The official subsequently fixed the issue via a patch (PR #3806) and resumed block production. However, due to an engine reset race condition during the sequencer cluster restart process, recovery synchronization was hindered, which also became an indirect cause of another brief outage the following day. Going forward, Base stated it will focus on strengthening protocol-level fuzz testing and stress testing capabilities to detect abnormal transaction paths earlier, while upgrading monitoring and operational systems, and introducing a more "graceful recovery mechanism" to improve the network's ability to quickly recover from similar failures in the future. (Source: PANews)
ETH-0.25%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments