On January 11th, Ethereum L2 network Starknet released a post-mortem report regarding this week’s brief mainnet outage, 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 rolled-back state write, leading to transaction execution anomalies. The relevant 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; the previous one in September was caused by a sequencer vulnerability, resulting in over 5 hours of downtime and rolling 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.
Starknet Outage Report: State conflict between the execution layer and the proof layer caused approximately 18 minutes of on-chain activity rollback
On January 11th, Ethereum L2 network Starknet released a post-mortem report regarding this week’s brief mainnet outage, 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 rolled-back state write, leading to transaction execution anomalies. The relevant 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; the previous one in September was caused by a sequencer vulnerability, resulting in over 5 hours of downtime and rolling back about 1 hour of on-chain activity.