Starknet Explains What Went Wrong Behind Monday’s Mainnet Outage

What Caused Starknet’s Temporary Mainnet Downtime?

The team behind Starknet has published a post-mortem explaining the cause of a brief mainnet disruption that occurred on Monday. According to the report, the issue stemmed from a mismatch in network state between two core components: the blockifier, which handles transaction execution, and the proving layer, which verifies that execution before finalizing it.

In a narrow edge case involving cross-function calls, state writes, and reverts, the blockifier incorrectly retained a state change that should have been discarded. The error caused certain transactions to be executed incorrectly at the execution layer, even though they should not have passed validation.

“In one specific combination of cross-function calls, variable writes, reverts, and catching them, the blockifier remembered a state-writing that happened within a function that was reverted, causing an incorrect transaction execution,” the Starknet team wrote in its report.

Crucially, the issue never reached ETH finality. Starknet’s proving layer detected the inconsistency and prevented the faulty transactions from being committed to the ledger. As a result, the network initiated a block reorganization, rolling of activity.

Investor Takeaway

Why Didn’t the Bug Reach ETH Finality?

Starknet’s architecture separates transaction execution from proof verification. While the blockifier processes transactions, the protocol rules before anything is finalized on ETH.

In this case, the proving layer acted as a backstop. It flagged the incorrect execution and stopped it from being finalized, forcing a reorganization instead. “This incorrect execution never saw L1 finality thanks to Starknet’s proving layer,” the team said.

The trade-off was temporary disruption rather than permanent damage. The network reverted recent blocks, and users whose transactions were affected had to resubmit them once the chain returned to a valid state. Starknet said the network has since resumed normal operation.

The team also committed to expanding testing coverage and audits to reduce the likelihood of similar issues, particularly around edge-case interactions between execution logic and rollback mechanisms.

How Does This Compare With Starknet’s Earlier Outages?

Monday’s disruption was not the first time Starknet faced reliability issues in 2025. The most severe incident occurred in September, following a major protocol upgrade known as Grinta. That outage lasted more than five hours and was traced to a sequencer bug.

Sequencers are responsible for ordering transactions before they are executed and proved. During the September incident, entirely. The recovery process required two chain reorganizations, which rolled back roughly one hour of network activity.

Users affected by that event were forced to resubmit transactions, a manageable inconvenience for some but a serious issue for traders or applications operating on tight timing constraints. Compared with that episode, Monday’s 18-minute rollback was shorter and more contained, but it followed a similar recovery pattern.

What Does This Say About Modern Layer-2 Design?

Together, the incidents highlight a broader challenge facing advanced L2 networks. Starknet and similar systems rely on multi-layered stacks that include execution engines, proving systems, sequencers, and cross-layer coordination with ETH. Each layer adds security and scalability, but also increases the surface area for subtle bugs.

The latest outage shows how even well-isolated edge cases can trigger chain reorganizations when execution logic and rollback handling diverge. While Starknet’s securety mechanisms worked, the user experience still involved downtime and transaction reversions.

For , the lesson is not that L2 systems are unsecure, but that they are still maturing. Features such as zero-knowledge proofs and custom execution engines bring powerful guarantees, yet they demand extensive testing across combinations that are hard to exhaustively model.

Investor Takeaway

What Happens Next for Starknet?

Starknet says it has already restored full functionality and is reviewing internal processes to strengthen testing around execution-and-revert logic. The team framed the incident as evidence that its proving layer worked as designed, while acknowledging the need to reduce the likelihood of reorgs.