The workforce in the encourage of Starknet, an Ethereum layer‑2 (L2) scaling community, launched a autopsy file outlining the muse cause of the non permanent mainnet downtime on Monday.
The foundation cause of the mainnet downtime became a discrepancy in the community relate between the blockifier execution layer and the proving layer that exams that the execution layer is processing transactions precisely, in line with the file. The Starknet workforce defined:
“In a single sigh mixture of noxious-characteristic calls, variable writes, reverts, and catching them, the blockifier remembered a relate-writing that came about within a characteristic that became reverted, causing an wrong transaction execution.
This wrong execution beneath no circumstances saw L1 finality thanks to Starknet’s proving layer,” the StarkNet workforce mentioned, highlighting how the proving layer functioned successfully by flagging the error and no longer committing the depraved transactions to the ledger.
The incident compelled a block reorganization, and 18 minutes of community job to be reverted. StarkNet is encourage to authorized efficiency, the workforce mentioned.
The incident triggered the workforce to commit to testing and code audits to end identical issues in due course. Monday’s StarkNet disruption also highlights the recount of coding for essentially the latest technology of blockchain networks, which consist of multi-layered technology stacks.
Associated: Iran is lower off from the accept: Right here’s how crypto may per chance well well even peaceful work
Monday’s outage wasn’t the first time Starknet skilled disruption in 2025
StarkNet skilled loads of disruptions in 2025, with essentially the most serious outage occurring in September following a foremost protocol strengthen known as Grinta.
The outage lasted over five hours and became precipitated by a sequencer worm, in line with a autopsy file from the Starknet workforce. Sequencers are the programs passe to recount transactions on a blockchain community.
Throughout the outage, block manufacturing halted, and two chain reorganizations were completed to revive the community to a useful relate.
The reorganization compelled about 1 hour of community job to be reverted or rolled encourage, that implies users needed to resubmit the transactions.
From a consumer perspective, having to resubmit a transaction is a minor anxiousness if the transaction became no longer time-sensitive, however it completely may per chance well well even showcase catastrophic for a frequent trader or an investor who wishes to exit a situation or put up a transaction within a temporary timeframe.
Magazine: Ethereum’s Fusaka fork defined for dummies: What the hell is PeerDAS?
