Starknet, an Ethereum layer-2 scaling network, has published a post-mortem report detailing the cause of a recent temporary mainnet outage. The disruption, which lasted approximately 18 minutes, was attributed to a state discrepancy between the blockifier execution layer and the proving layer. While the network has since resumed normal operations, the incident has prompted a commitment to enhanced testing and code audits to prevent future occurrences.
Key Takeaways
-
A state discrepancy between the blockifier and proving layers caused the outage.
-
The proving layer successfully prevented faulty transactions from reaching L1 finality.
-
Approximately 18 minutes of network activity were reverted, requiring users to resubmit transactions.
-
Starknet is enhancing testing and audits to prevent similar issues.
Root Cause of the Outage
The core issue stemmed from an edge case involving cross-function calls, variable writes, and reverts. In this specific scenario, the blockifier incorrectly remembered a state write that occurred within a reverted function, leading to an erroneous transaction execution. However, Starknet's proving layer, designed to verify the correctness of execution, detected this inconsistency. This safeguard prevented the faulty transactions from being finalized on the Ethereum mainnet, triggering a block reorganization instead.
Network Recovery and User Impact
As a result of the detected error, Starknet initiated a block reorganization, rolling back about 18 minutes of network activity. While this prevented permanent damage and ensured user funds remained secure, affected users had to resubmit their transactions. The team confirmed that the network has returned to full functionality.
Lessons Learned and Future Prevention
This incident underscores the complexities of developing advanced layer-2 solutions with multi-layered technology stacks. The Starknet team has committed to strengthening its testing procedures and conducting more rigorous code audits, particularly focusing on the interactions between execution logic and rollback mechanisms. This proactive approach aims to minimize the likelihood of future disruptions.
Previous Incidents
This is not the first disruption Starknet has experienced in 2025. A more significant outage occurred in September following a protocol upgrade named Grinta, which lasted over five hours and was caused by a sequencer bug. That incident also required chain reorganizations and transaction resubmissions, highlighting the ongoing challenges in ensuring consistent uptime for next-generation blockchain networks.
Sources
-
Starknet publishes post-mortem report after temporary network outage — TradingView News, TradingView — Track All Markets.
-
Starknet Explains What Went Wrong Behind Monday’s Mainnet Outage, FinanceFeeds.
This article was created with support from AI-driven technology, drawing on multiple reputable sources. The final content has been thoroughly reviewed and edited by BlockzHub's editorial team to ensure accuracy, clarity, and coherence. Original reporting sources are credited whenever appropriate and as required. The opinions expressed in this article do not necessarily represent the official views or positions of BlockzHub. This article is intended for informational purposes only and should not be considered financial or professional advice. Investing involves risk, and you should consult a qualified financial advisor before making any investment decisions.