【Block Rhythm】Starknet has had another incident recently. This Ethereum L2 network experienced a brief mainnet outage on Monday this week, and the official team released a root cause analysis afterward.
According to the incident report, the problem stemmed from state inconsistency between the execution layer (blockifier) and the proof layer. Specifically, under certain combinations of cross-function calls and rollbacks, the execution layer incorrectly recorded some state changes that should have been rolled back, directly causing transaction execution anomalies. The affected transactions did not receive finality confirmation from the L1 layer.
This incident triggered a chain reorganization on-chain, with approximately 18 minutes of transaction records completely rolled back. What’s somewhat frustrating is that this is already the second major outage for Starknet since 2025. Looking back at the timeline, the failure last September caused by a sequencer vulnerability resulted in network downtime exceeding 5 hours and rolled back approximately 1 hour of on-chain activity.
Consecutive technical issues have dealt a significant blow to confidence in an L2. For ecosystem applications and users relying on Starknet, such instability will inevitably prompt reconsideration. How to strengthen system stability going forward should be the most urgent task for the Starknet team.
Starknetメインネットの短時間のダウン後の続報：状態の不一致によりブロックのリオーグが発生、今年2回目となる
【Block Rhythm】Starknet has had another incident recently. This Ethereum L2 network experienced a brief mainnet outage on Monday this week, and the official team released a root cause analysis afterward.
According to the incident report, the problem stemmed from state inconsistency between the execution layer (blockifier) and the proof layer. Specifically, under certain combinations of cross-function calls and rollbacks, the execution layer incorrectly recorded some state changes that should have been rolled back, directly causing transaction execution anomalies. The affected transactions did not receive finality confirmation from the L1 layer.
This incident triggered a chain reorganization on-chain, with approximately 18 minutes of transaction records completely rolled back. What’s somewhat frustrating is that this is already the second major outage for Starknet since 2025. Looking back at the timeline, the failure last September caused by a sequencer vulnerability resulted in network downtime exceeding 5 hours and rolled back approximately 1 hour of on-chain activity.
Consecutive technical issues have dealt a significant blow to confidence in an L2. For ecosystem applications and users relying on Starknet, such instability will inevitably prompt reconsideration. How to strengthen system stability going forward should be the most urgent task for the Starknet team.