BlockBeats News, January 11 — Ethereum L2 network Starknet released a post-mortem report on the short-term 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 rolled-back state, leading to transaction execution anomalies. The related transactions did not receive finality 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; previously, in September, a sequencer vulnerability caused 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.
3 Likes
Reward
3
1
Repost
Share
Comment
0/400
GateUser-d3d18387
· 01-11 01:14
Good luck in the Year of the Horse, hold onto your chips, and wait for the rise.
Starknet Outage Report: State conflict between the execution layer and the proof layer caused approximately 18 minutes of on-chain activity rollback
BlockBeats News, January 11 — Ethereum L2 network Starknet released a post-mortem report on the short-term 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 rolled-back state, leading to transaction execution anomalies. The related transactions did not receive finality 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; previously, in September, a sequencer vulnerability caused over 5 hours of downtime and a rollback of about 1 hour of on-chain activity.