Ethereum Developers Tackle Holesky Testnet Issues in Core Call #206

Ethereum developers convened on February 27, 2025, for the All Core Developers Execution (ACDE) Call #206, chaired by Tim Beiko of the Ethereum Foundation. The meeting focused on the Holesky testnet recovery following its disruption post-Pectra activation and discussed the upcoming Sepolia testnet upgrade, according to galaxy.com.

Holesky Testnet Challenges

The activation of Pectra on February 24 led to issues on the Holesky testnet, primarily due to misconfigured client software in Geth, Nethermind, and Besu. This caused a chain split, complicating efforts to stabilize the network. As a result, only a minority of validators continued to operate correctly, prompting a detailed discussion on recovery strategies.

Tim Beiko explained the root cause of the failure, emphasizing the incorrect validator deposit addresses, which differ from those on the mainnet. Developers are coordinating efforts to recover Holesky, including a proposed mass slashing event to finalize the correct version of the network. However, this plan faces skepticism due to potential coordination challenges among clients and validators.

Sepolia Upgrade Plans

Developers also addressed the upcoming Sepolia testnet upgrade, scheduled for March 5. The upgrade requires updated client software from Geth, Nethermind, and Besu, as well as a mandatory update for the Lodestar CL client. Tim Beiko confirmed that the activation date would remain unchanged, stressing the importance of timely updates by node operators.

Long-Term Initiatives

In addition to immediate recovery efforts, developers discussed longer-term initiatives to prevent similar incidents. Suggestions included standardizing fork configuration formats and enhancing checkpoint sync capabilities across clients. These initiatives aim to improve network resilience and prepare for future Ethereum upgrades, such as Fusaka.

Conclusion

The ACDE call provided valuable insights into Ethereum’s network management and future protocol adjustments. While some skepticism remains about the feasibility of current recovery plans, the discussion highlighted the importance of Holesky as a testing environment and the need for improved network resilience.

FAQs

• What caused the Holesky testnet issues?
  The issues were caused by misconfigured client software in Geth, Nethermind, and Besu, leading to a chain split and validator deposit address discrepancies.
• What is the proposed recovery plan for Holesky testnet?
  The plan includes a proposed mass slashing event to finalize the correct version of the network, but faces skepticism due to potential coordination challenges among clients and validators.
• When is the Sepolia testnet upgrade scheduled?
  The Sepolia testnet upgrade is scheduled for March 5, 2025.