Starknet experienced a brief mainnet outage this week, and the official team subsequently released a technical analysis report. The root cause was identified as a mismatch in state data between the execution layer (blockifier) and the proof layer. Specifically, under certain special combinations of cross-function calls and rollbacks, the execution layer recorded state writes that should have been rolled back, leading to transaction execution anomalies. Since these transactions did not receive finality confirmation from the L1 layer, the entire system triggered a chain reorganization, and approximately 18 minutes of on-chain activity was completely rolled back.

This is the second major disruption for Starknet this year. In September, a vulnerability in the sequencer caused over 5 hours of downtime, during which about 1 hour of on-chain data was rolled back. The short interval between these two failures highlights that the L2 network still faces significant stability challenges that need to be addressed.