Daily Crypto News & Musings

Ethereum’s ACDE #207 Tackles Holesky Issues, Plans Hoodi Testnet

Ethereum’s ACDE #207 Tackles Holesky Issues, Plans Hoodi Testnet

Highlights of Ethereum’s All Core Devs Meeting (ACDE) #207

The recent All Core Devs Meeting (ACDE) #207 tackled significant issues with the Holesky Testnet, focusing on its non-finality and the massive validator exit queue. The meeting also explored various solutions, with a strong inclination towards launching a new testnet, Hoodi, to ensure a stable environment for future upgrades. Discussions extended to the upcoming Pectra and Fusaka upgrades, system contract error handling, RPC changes, and ongoing research into stateless clients.

  • Holesky Testnet’s non-finality and validator exit queue
  • Launch of Hoodi Testnet as a solution
  • Timelines for Pectra and Fusaka upgrades
  • System contract error handling and RPC enhancements
  • Progress on stateless client research

The Holesky Testnet has been a thorn in the side of Ethereum developers, suffering from non-finality for nearly two weeks. This state, where transactions couldn’t be confirmed, led to network instability, akin to a traffic jam in the blockchain world. Validators faced mass slashings, creating a validator exit queue so long that it resembled trying to exit a packed concert with a million people ahead of you. This situation made Holesky unsuitable for testing the upcoming Pectra upgrade.

To address these issues, the Ethereum community, known for its resilience, considered four solutions. Plan A, the favored approach, involves launching Hoodi Testnet, which will mirror Mainnet conditions more closely by using 32 ETH validators at launch. This new testnet aims to provide a stable and reliable environment crucial for forthcoming upgrades. Plans B, C, and D included using Devnet 6, implementing a shadow fork, and executing a hard fork to reset the exit queue. However, the primary concern with Plan D was the potential risk to Mainnet from implementing a hardcoded exit queue reset.

Looking ahead, the Pectra Mainnet upgrade is scheduled for a fork between late April and early May 2025, following a stability test on Hoodi. This timeline highlights Ethereum’s commitment to continuous improvement. The Fusaka upgrade, another critical development, focuses on enhancing blob transaction formatting—think of it as improving how transactions are processed and stored—execution API adjustments, and handling the EVM Object Format (EOF). A proposal was reviewed to address potential edge cases in transaction formatting for Ethereum blobs, showcasing the community’s dedication to refining the network.

System contract error handling was another focus, with developers exploring ways to standardize failure responses across clients. This includes marking blocks as invalid, handling failures per transaction, and codifying a standardized failure response. Additionally, a new RPC error code will be introduced to indicate when requested data is no longer available due to pruning, enhancing the predictability and user-friendliness of Ethereum’s RPC system.

Research into stateless clients continues to progress, aiming to optimize the Merkle Patricia Trie (MPT) for lower storage and improve sync times. Stateless clients, which don’t need to store full state data, promise to enhance Ethereum’s scalability and security. While significant work remains before implementation, these efforts signal a long-term commitment to improving the Ethereum ecosystem.

Despite these technical challenges, the Ethereum community remains optimistic about the platform’s future. The decision to launch Hoodi Testnet and the planned upgrades demonstrate a proactive approach to addressing issues and enhancing the network’s capabilities. As Ethereum evolves, these developments underscore its dedication to maintaining a robust and efficient blockchain platform.

However, not everyone is singing Ethereum’s praises. Some argue that the platform’s complexity and frequent updates could lead to centralization, as only a few highly specialized teams can keep up with the rapid changes. Others point out that the focus on testnets and upgrades might distract from more pressing issues like user experience and adoption. Yet, Ethereum’s resilience and the community’s willingness to tackle these challenges head-on fuel optimism for its future.

From a Bitcoin maximalist perspective, Ethereum’s frequent updates might seem like a double-edged sword. While innovation is commendable, the simplicity and stability of Bitcoin are seen by some as more important for a cryptocurrency’s long-term success. However, Ethereum’s ability to adapt and its role in filling niches that Bitcoin might not serve well remains undeniable.

As Ethereum navigates these waters, it’s clear that the journey is far from smooth. But with each meeting, each upgrade, and each new testnet, Ethereum takes steps toward a more decentralized and efficient future. And while the road may be bumpy, the destination—a fully functional, scalable, and secure blockchain—remains in sight.

Key Takeaways and Questions

  • What issues did the Holesky Testnet face?

    The Holesky Testnet faced non-finality for nearly two weeks, resulting in instability and mass validator slashings, which led to a large validator exit queue of one million validators.

  • What solutions were considered for the Holesky issues?

    Four solutions were considered: launching a new testnet (Plan A), using Devnet 6 (Plan B), implementing a shadow fork (Plan C), and executing a hard fork to reset the exit queue (Plan D).

  • What is the Hoodi Testnet, and how does it relate to Holesky?

    Hoodi is a new testnet proposed to replace Holesky due to the latter’s issues. Hoodi will mirror Mainnet conditions with 32 ETH validators and provide a reliable testing environment.

  • When is the Pectra Mainnet upgrade expected to occur?

    The Pectra Mainnet upgrade is expected to occur between late April and early May 2025, following a stability test on Hoodi.

  • What are the key areas of focus for the Fusaka upgrade?

    The Fusaka upgrade focuses on blob transaction formatting, execution API adjustments, and handling of the EVM Object Format (EOF).

  • How will Ethereum handle system contract failures?

    Ethereum is exploring options to standardize failure responses across clients, including marking blocks as invalid, handling failures per transaction, and codifying a standardized failure response.

  • What changes are planned for Ethereum’s RPC system?

    A new RPC error code will be introduced to indicate when requested data is no longer available due to pruning, improving response predictability and user-friendliness.

  • What is the current status of research into stateless clients?

    Research into stateless clients continues, focusing on optimizing the Merkle Patricia Trie (MPT) for lower storage and improving sync times, with further research needed before implementation.