Recently, the Ethereum ecosystem's L2 solution Starknet experienced an unexpected outage. According to post-incident analysis by the official team, the issue was related to state verification between the execution layer (blockifier) and the proof layer.

Specifically, under certain cross-function calls combined with state rollbacks, a logical vulnerability occurred in the execution layer — it incorrectly recorded state modifications that should have been rolled back. This directly caused anomalies in subsequent transaction executions, and these affected transactions did not receive finality confirmation from the L1 layer.

What was the result? The entire network triggered a chain reorganization mechanism, and all on-chain activities within approximately 18 minutes were rolled back. It sounds a bit alarming, but in distributed systems, this self-healing mechanism is actually a designed feature.

More notably, this is the second major outage Starknet has experienced in 2025. Previously, in September, a vulnerability in the sequencer caused over 5 hours of service disruption, during which about 1 hour of on-chain data was rolled back. It appears that the robustness of L2 networks under high concurrency or abnormal scenarios still needs to be strengthened.