This is a segment from the 0xResearch newsletter. To read full editions, subscribe.
Ethereum developers on Monday initiated the Pectra upgrade on the Holesky testnet to evaluate the upgrade’s production readiness.
Shortly after activation, the Holesky testnet experienced issues with finalizing transactions. Hildobby, a data analyst at Dragonfly, noted that Holesky was down for almost two hours following the upgrade. Hildobby attributed it to “buggy code [causing] an invalid block that most execution clients accepted.”
The issue affected Besu, Nethermind and Geth, while Erigon and Reth operated correctly.
However, developers assessed that the issue is unique to Holesky — a result of a misconfigurating specific to that testnet that wouldn’t occur on Ethereum mainnet. It’s not a problem with Pectra code, per se, according to Ethereum Foundation’s Parithosh Jayanthi.
“There are learnings we can take forward, but it isn’t a bug with a wide surface area,” Jayanthi said. “We may take some time to manually verify some things, but the problem seems fully explained.”
A case like this shows the benefits of client diversity. A heterogeneous client ecosystem ensures that no single software implementation becomes a systemic point of failure, improving Ethereum’s resilience and decentralization.
Meanwhile, efforts are underway to rectify the issues on Holesky. But “recovery is very difficult,” Geth developer Marius van der Wijden said.
“This whole thing will make Ethereum much stronger,” according to van der Wijden. Waxing poetic, he added “we will mend the cracks with gold and be better prepared for any eventualities in the future.”
Pectra aims to introduce account abstraction and bolster layer-2 scaling solutions:
This Holesky deployment is part of the critical testing phase. The Sepolia testnet will follow before the anticipated mainnet launches in April.
Get the news in your inbox. Explore Blockworks newsletters:
All Rights Reserved. Copyright 2025, Central Coast Communications, Inc.