2026-01-05 18:23:05

On January 5th, Starknet experienced some issues. Starting from 09:53 UTC, the network first slowed down block production, and then it completely stopped. The official team later confirmed that the transactions submitted between 09:24 and 09:42, a span of 18 minutes, were the most severely affected.

The technical team conducted an investigation and found that the problem stemmed from a discrepancy between the transaction execution logic and the zero-knowledge proof logic. In simple terms, the two systems had different understandings of the same transaction. To fix this issue, the development team rolled back the chain to block 5,187,263 and urgently released a patched version of Blockifier.

If you made any transactions during that period—whether transfers, swaps, or other contract interactions—it's best to check the block explorer now. Some transactions might not have been included on-chain or may have been canceled. In such cases, manually resubmit the transactions.

Honestly, this is the second major stability issue Starknet has encountered after the "Grinta" upgrade in 2025. Although the price of STRK has been holding up, consecutive outages are testing the patience of developers. Currently, it’s recommended to wait until the official release of a comprehensive root cause analysis report before handling large on-chain operations.

STRK-0,4%

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.

15 Likes

Reward
15
8
Repost
Share

Comment

0/400

YieldWhisperer

· 18h ago

Once again, Starknet is down... Are they using us as a stress test? Oh my God, after the Grinta upgrade, how many times has this happened... I really can't hold on anymore. Rolling back transactions sounds simple to say but hard to do? It's exhausting. STRK is resistant to falling but can't withstand this frequency, buddy. Waiting for the RCA report? I can't wait, I'll just withdraw directly.

View OriginalReply0

LightningClicker

· 20h ago

Oh no, Starknet is causing trouble again? These days, zero-knowledge proof systems are really good at pulling stunts... Wait, rolling back to that block? I need to quickly check my transactions from that day, I feel like I have to resubmit again. So annoying. After the Grinta upgrade, this is the second time. When will it finally stabilize? I think I should wait for the official report before moving large funds. Although the STRK price is still okay, the user experience is really terrible.

View OriginalReply0

POAPlectionist

· 01-05 18:52

Another crash? Starknet's pace really can't keep up anymore.

View OriginalReply0

SolidityNewbie

· 01-05 18:52

Another one? I really can't hold it anymore. After the Grinta upgrade, there have been two major outages. This pace is a bit outrageous.

View OriginalReply0

AlphaBrain

· 01-05 18:51

Another one? Starknet really needs to reflect properly; this frequency is a bit outrageous.

View OriginalReply0

DegenWhisperer

· 01-05 18:50

Coming again? Just a few days after the upgrade, and now this. Starknet is treating us like guinea pigs. Consecutive failures, yet the STRK price can still hold. The community's mentality is really tough. The trade entered 18 minutes ago probably has to be redone now. Let's wait for the root cause analysis report, everyone. Large transactions should be frozen first. This situation is quite risky. It's purely technical; stability still needs to be refined. Whoever entered the Swap back then, good luck to you. Check your orders in the browser. Rolling back to that block feels like playing a save/load game... The promised 2025 upgrade, but it turns out this is a bug upgrade.

View OriginalReply0

SchrodingerAirdrop

· 01-05 18:40

Secondary outage occurred again; after the Grinta upgrade, this pace is indeed a bit chaotic.

View OriginalReply0

LowCapGemHunter

· 01-05 18:29

Bro, Starknet is down again, and this time it's pretty serious... Two systems are conflicting with each other, how embarrassing is that? The rollback operation seems to have been quite rushed, but I just want to know why such logical deviations made it to the production environment. I need to quickly check the transactions from that period, or I might get canceled quietly without even knowing. Two consecutive issues of this level, honestly, it's a bit disappointing... STRK price is holding up pretty well, but if this continues, developers will be very annoyed. Let's wait for the official root cause analysis before making large transactions. Dealing with this hot potato now is too costly.

View OriginalReply0