Starknet mainnet short-term outage follow-up: state inconsistency caused block reorganization, marking the second time this has happened this year.

NullWhisperer · 2026-01-11T00:48:11+00:00

Starknet recently experienced a brief mainnet outage again due to inconsistencies between the execution layer and the proof layer, resulting in transaction anomalies and on-chain record rollbacks of 18 minutes. This is the second major outage since 2025, further impacting user and ecosystem application confidence. The team needs to strengthen system stability as soon as possible.

NullWhisperer

2026-01-11 00:48:11

Abstract generation in progress

【Blockchain Rhythm】Recently, Starknet has encountered issues again. This Ethereum L2 network experienced a brief mainnet outage on Monday, and the official team subsequently released a root cause analysis.

According to the incident report, the problem stemmed from a state inconsistency between the execution layer (blockifier) and the proof layer. Specifically, in certain cross-function call and rollback scenarios, the execution layer incorrectly recorded some state changes that should have been rolled back, directly causing transaction execution anomalies. Affected transactions did not receive finality confirmation from the L1 layer.

This incident triggered on-chain block reorganization, with approximately 18 minutes of transaction records being completely rolled back. To make matters worse, this is the second major outage for Starknet since 2025. Looking back at the timeline, the failure in September last year was caused by a sequencer vulnerability that led to over 5 hours of network downtime and a rollback of about 1 hour of on-chain activity.

Repeated technical issues significantly undermine confidence in an L2. For ecosystem applications and users relying on Starknet, such instability may cause reconsideration. Strengthening system stability in the future should be the most urgent task for the Starknet team.

STRK-1,85%

ETH0,51%

View Original

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.

11 Likes

Reward
11
4
Repost
Share

Comment

0/400

GasWaster

· 11h ago

Starknet doing the same thing again? Just after the New Year, and now the second time. The frequency is a bit outrageous. Where is the promised stability of Starknet? Why is it still playing the "inconsistent state" game? All transactions in 18 minutes are gone. I just want to know if anyone lost money because of this. The execution layer and the proof layer are fighting. To put it nicely, it's an architecture flaw. Do such basic issues still occur? Aren't all L2s the same? Why is Starknet so troublesome? Can we really trust a rollback chain? User fund security is a concern. Sequencers, blockifiers, and various issues keep emerging. Are they trying to boost their popularity? It's happened twice this year. It seems you need to be mentally prepared when investing in Starknet. Every time it's "root cause analysis," and next time there will be new faults. The cycle is annoying.

View OriginalReply0

BlockchainGriller

· 11h ago

Starknet is down again? What's going on with this guy this year? It was supposed to be stable, right? Two major incidents in a year, this frequency is a bit outrageous. The execution layer and the proof layer are fighting, causing 18-minute transactions to have to be redone. Unbelievable.

View OriginalReply0

OfflineNewbie

· 11h ago

Starknet is down again? This guy just started 2025 and has already caused the second outage. Come on, just focus on testing properly.

View OriginalReply0

GasFeeCrybaby

· 11h ago

Starknet is acting up again. This time it's not as outrageous as last time, but twice a year is really hard to keep up… --- The execution layer and the proof layer are fighting, and it was gone in 18 minutes. I just want to know who the hell wrote this code… --- Stopped for 5 hours last September and now it's happening again? Can we still trust L2… --- Such low-level errors like inconsistent states can happen. It feels like they haven't even tested their testnet. --- Rolling back, rolling back every day. What's the difference from doing nothing…

View OriginalReply0