# Post-finality Holesky path forward **The Problem** Currently we have sepolia, a closed validator set testnet. This network enables application developers to test their applications in a closed environment. This network is not optimal for validators as they can't make deposits. We have holesky, which in it current state is not really suitable for testing validator related features. Due to the recent unfinality event, and the fact that the exit queue is full for the next ~1.5 years, full validator lifecycle tests are not possible. Consolidations rely on the exit queue as well, so this feature is currently untestable. We propose a few different plan options that the public,client teams,application developers,staking pools should consider. We would like to hear the feedback from everyone. _________________________________ **Plan A: Plan for the future new testnet** We are currently investigating the possibility of creating a new testnet, which will be more suitable for validators. This network could be big enough to enable consolidations but would not be too large so as to be expensive for each client team to run. **Benefits of a new testnet:** * Adds one more network to the mix, which is good to test feature forks to ensure that they are feature complete. * Enables a place where the public can test their validator setup at its full lifecycle. - including consolidations and exits. * We can increase the gas limit on this network and test execution limits too **Drawbacks of a new testnet:** * Yet another network to maintain. * Client teams will have to add another named testnet to their codebase. * Tooling takes a while to get deployed to new networks, making it not ideal for the pectra critical testing path **Estimated launch date by end of March 2025. Expected runtime - 5 years.** _________________________________ **Plan B: Use devnet-6 as a testnet.** Let the public test their validator setup at its full lifecycle. - including consolidations and exits. **Benefits of using devnet-6:** * No need to maintain another network. * Client teams could easily add it to their releases, and make it easy for the public to run. **Drawbacks of using devnet-6:** * Devnet-6 is not using mainnet spec, e.g withdrawal delays are shorter **Already running network. Expected runtime - till June 2025.** ________________________________ **Plan C: Use a shadowfork of holesky.** Keep the EL side of the network as before the unfinality event, and start a new genesis validator set on the CL side. **Benefits of using a shadowfork of holesky:** * EL state is the same, so contracts are already deployed **Drawbacks of using a shadowfork of holesky:** * Would still require a lot of tooling to be redeployed * Would possibly use confusion to the public, especially if the network is not named differently. (we could name it holesky-shadowfork in client releases) * We would still need to maintain another network. **Expected launch date in 2 weeks. Expected runtime - till mainnet fork of pectra.** ________________________________ **Plan D: Use hacky solution to empty Holesky queue** This could imply having a large exit queue size for holeksy, allowing us to empty the queue far faster than currently projected. **Benefits of using hacky solution to empty Holesky queue:** * No need to maintain another network. * No tooling would need to be redeployed. **Drawbacks of using hacky solution to empty Holesky queue:** * Code base changes that are hacky, one off and not really representative of a real way to fix the issue on mainnet. **Estimated code completion - few weeks (?) - Expected runtime EOL Holesky** ________________________________
Last changed by  
 
ethpandaops For the ethpandaops team, devops for EL/CL layers
837

Read more

peerdas-devnet-6 specs

:::info :mega: Devnet-6 targets launch in mid/late Mar 2025 ::: :::info :mega: Note: PeerDAS is activated at the FULU_FORK_EPOCH ::: Note, changes include:

3/13/2025
osaka-devnet-0 specs

:::info :mega: Devnet-0 targets launch at ... ::: EIP List for osaka-devnet-0 The list below links the specific commit versions of the EIPs included in devnet-0. Spec changes for eof-devnet-0: Execution Specs

3/13/2025
Hoodi testnet

This write up will help you understand the initial distribution of validators among the new hoodi testnet. This testnet will launch in case we decide to do plan A of this writeup. Given: Ethpandaops controls 33% of the validators. The remaining 67% should be split among:11 client teams (each with approx. the same share). 5 staking operators (each with a slightly smaller share). Total staked ETH: At least 20M ETH. Each validator balance: Between 32 ETH and 2048 ETH.

3/12/2025
Holesky path forward

Issue: While holesky is stable and finalizing now, a large amount of damage has already been done: ~1M validators have been either slashed or exited from the network. These exits are lined up in the exit queue and would take until June 2026 to completely clear up. Even with completely full deposit queues, we cannot reach the older validator sizes in a reasonable amount of time. The consolidation feature in pectra relies on the source validator to completely exit before the balance accures in the target validator. With a full exit queue, we can no longer test consolidations on Holesky until the queue has cleared. Implications: The community and staking pools would not be able to test consolidations on a public network for a long time

3/11/2025
Read more from ethpandaops
Published on HackMD