The crew behind Starknet, the Ethereum Layer 2 (L2) scaling community, launched a autopsy report on Monday outlining the basis causes of short-term mainnet downtime.
In response to the report, the basis reason behind the mainnet downtime was a mismatch in community situations between the blocking execution layer and the attestation layer that ensures the execution layer is processing transactions appropriately. The Starknet crew defined:
“In a single specific mixture of cross-function calls, variable writes, cancellations, and their catches, the blocking perform remembered state writes that occurred throughout the canceled perform, inflicting incorrect transaction execution.
Diagram exhibiting how a bug within the code affected the community. sauce: stark web
“Due to Starknet's proof layer, this inaccurate execution by no means achieved L1 finality,” the StarkNet crew mentioned, highlighting how the proof layer labored correctly by flagging the error and never committing the offending transaction to the ledger.
This incident pressured a block reorganization, reversing 18 minutes of community exercise. In response to the analysis crew, StarkNet has returned to regular performance.
This incident prompted the crew to conduct testing and code audits to stop comparable points from occurring sooner or later. Monday's StarkNet disruption additionally highlighted the challenges of coding the most recent era of blockchain networks, which embrace multi-layered expertise stacks.
Associated: Iran is lower off from the web: Right here's how cryptocurrencies nonetheless work
Monday's outage wasn't the primary time Starknet skilled disruption in 2025
StarkNet skilled a number of outages in 2025, with probably the most extreme failure occurring in September after a significant protocol improve referred to as Grinta.
In response to the Starknet crew's after-action report, the outage lasted greater than 5 hours and was attributable to a bug within the sequencer. A sequencer is a system used to order transactions on a blockchain community.
Starknet uptime. The purple sq. represents the September outage. sauce: stark web
Throughout the outage, block era stopped and two chain reorganizations had been carried out to revive the community to a useful state.
This reorganization resulted in roughly an hour of community exercise being undone or rolled again, requiring customers to resubmit their transactions.
From a person's perspective, having to resubmit a transaction is much less painful if the transaction just isn’t time-sensitive, however it may be deadly for frequent merchants and traders who often shut positions or must submit transactions in a brief time frame.
journal: Ethereum's Fusaka fork defined to novices: What precisely is PeerDAS?
