2026-01-11 02:25:30

Starknet officially released a comprehensive analysis report on the mainnet outage on January 5th. The culprit of this failure was a bug in the blockifier—under certain conditions, it incorrectly processed transactions.

What exactly happened? When operations such as cross-function calls, variable writes, rollbacks, and rollback captures occurred in combination, the generator would go awry. State write operations within rolled-back functions that should have been cleared were mistakenly marked as valid, causing issues in transaction execution.

Fortunately, Starknet's proof layer mechanism served as a lifesaver. This erroneous execution was never finalized on the L1 layer, effectively preventing the problem from becoming permanent on the chain. On-chain activity was rolled back for about 18 minutes.

Speaking of which, this is the second major outage Starknet has experienced in 2025. Previously, in September, there was a validator bug that caused over 5 hours of downtime, during which nearly an hour of on-chain activity was rolled back. The consecutive stability issues are indeed concerning.

STRK-1,06%

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

PaperHandsCriminal

· 01-11 02:55

Here we go again, Starknet, your resilience really can't hold up anymore.

View OriginalReply0

BtcDailyResearcher

· 01-11 02:55

Down again? Starknet's stability really can't hold up anymore.

View OriginalReply0

AirdropChaser

· 01-11 02:42

Is it down again? Starknet's stability is really concerning...

View OriginalReply0

screenshot_gains

· 01-11 02:39

Another one? Feels like Starknet is a bit too frequent --- L1 saved the day, or it would have been really over --- Twice... when will it finally stabilize --- Fortunately, there is a proof layer as a safety net, otherwise it would be diss'ed again --- The bug in blockifier is a bit outrageous, issues can arise even across function calls --- An 18-minute rollback is considered mild, better than last time --- I just want to know when it will be fixed. Do people still dare to store money on it now? --- Sequencer → blockifier → what's next? It's a bit disappointing --- The key is that these bugs should have been caught, where is the testing? --- Still need to keep observing, but at least it didn't go to L1... that's a bright spot

View OriginalReply0