Deep Tide TechFlow News, January 11th, according to an official announcement, Ethereum L2 network Starknet released a post-incident analysis report regarding the short-term mainnet outage on Monday. The report states 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 rolled-back state, leading to transaction execution anomalies. The related transactions did not receive final confirmation from L1.
This incident triggered a blockchain reorganization, rolling back approximately 18 minutes of on-chain activity. This is the second major outage since 2025; the previous one in September was caused by a sequencer vulnerability, resulting in over 5 hours of downtime and a rollback of 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.
Deep Tide TechFlow News, January 11th, according to an official announcement, Ethereum L2 network Starknet released a post-incident analysis report regarding the short-term mainnet outage on Monday. The report states 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 rolled-back state, leading to transaction execution anomalies. The related transactions did not receive final confirmation from L1.
This incident triggered a blockchain reorganization, rolling back approximately 18 minutes of on-chain activity. This is the second major outage since 2025; the previous one in September was caused by a sequencer vulnerability, resulting in over 5 hours of downtime and a rollback of about 1 hour of on-chain activity.