Wu said that Ethereum L2 network Starknet released a post-mortem report on the brief mainnet outage this Monday, stating that the cause of the incident was a state inconsistency between the execution layer (blockifier) and the proof layer: under specific cross-function call and rollback combinations, the execution layer incorrectly recorded a state that had been rolled back, leading to transaction execution anomalies. The related transactions did not receive finality confirmation from L1. This event triggered a blockchain reorganization, rolling back approximately 18 minutes of on-chain activity. This is the second major outage since 2025; previously, in September, a sequencer vulnerability caused over 5 hours of downtime and rolled back about 1 hour of on-chain activity.
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.
Wu said that Ethereum L2 network Starknet released a post-mortem report on the brief mainnet outage this Monday, stating that the cause of the incident was a state inconsistency between the execution layer (blockifier) and the proof layer: under specific cross-function call and rollback combinations, the execution layer incorrectly recorded a state that had been rolled back, leading to transaction execution anomalies. The related transactions did not receive finality confirmation from L1. This event triggered a blockchain reorganization, rolling back approximately 18 minutes of on-chain activity. This is the second major outage since 2025; previously, in September, a sequencer vulnerability caused over 5 hours of downtime and rolled back about 1 hour of on-chain activity.