StarkNet suffers second 2025 outage; block reorg rolls back.

Starknet briefly halts mainnet on Jan 5, 2026 after execution–proving layer state mismatch forces 18‑minute reorg; team vows tighter testing after second 2025 disruption

  • Starknet suffered a temporary mainnet outage tied to a state mismatch between its execution and proving layers.
  • The bug involved the blockifier remembering a reverted state write, producing an incorrect execution that the proving layer detected.
  • The proving layer prevented the faulty transactions from reaching L1 finality, triggering a block reorganization that rolled back 18 minutes of activity.
  • The team pledged increased testing and code audits after the incident.
  • This was the second major 2025 disruption; a September upgrade caused a multi-hour outage and about one hour of rolled-back activity.

The team behind Starknet, an Ethereum layer‑2 scaling network, reported a temporary mainnet downtime on Monday, January 5, 2026, caused by a state discrepancy between the execution layer and the proving layer, according to the report. The mismatch occurred during a specific combination of cross-function calls and reverts that led the execution layer to record an incorrect state write.

- Advertisement -

The post-mortem explains that the execution tool known as the blockifier “remembered a state-writing that happened within a function that was reverted, causing an incorrect transaction execution,” the report said. The network’s proving layer correctly flagged the inconsistency and stopped the faulty transactions from reaching L1 finality, preventing the error from being committed to the ledger.

Operators executed a block reorganization to resolve the discrepancy, reverting about 18 minutes of network activity. The team reported that mainnet functionality has returned to normal and said it will strengthen testing and perform code audits to reduce the risk of similar errors.

This incident follows an earlier disruption in 2025 after a major protocol upgrade called Grinta. A post-mortem for the September outage found a sequencer bug stopped block production for over five hours and required two chain reorganizations, forcing roughly one hour of activity to be rolled back, as detailed in the September report and illustrated in the network uptime data on Starknet’s status page.

✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.

- Advertisement -

Previous Articles:

- Advertisement -

Latest News

BitMine’s $8B ETH Loss: Tom Lee Says It’s “A Feature”

BitMine Immersion Technologies holds over 4.29 million ETH worth $16.4 billion, approximately 3.5% of...

Alphabet Stock Dips 2.5% Despite Strong Earnings Amid AI Spend Worries

Alphabet (GOOGL) stock fell 2.5% Thursday, extending a five-day slide to 4% despite a...

US Crypto Bill Stalls in Senate Amid Partisan Dispute

A major crypto market structure bill has cleared the Senate Agricultural Committee but faces...

Treasury Chief Blasts ‘Nihilist’ Crypto Lobby on Bill

U.S. Treasury Secretary Scott Bessent criticized crypto industry figures resisting a major market structure...

Radix Proposes Tapering Validator Subsidy to End Treasury Dependency

The Radix Foundation proposes a phased end to its validator subsidy by June 2026,...
- Advertisement -

Must Read

Best Metaverse Tokens to Buy on Binance for 10X Gains

Ever since Facebook renamed their company to Meta, as well as their plans to build a metaverse where we can travel into using Virtual...
🔥 #AD Get 20% OFF any new 12 month hosting plan from Hostinger. Click here!