# 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](https://notes.ethereum.org/@ethpandaops/post-finality-path-forward-holesky). ### 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**. --- ## Plan A - Smaller than mainnet ## Stake Distribution - **Ethpandaops** **6.6M ETH** (33% of 20M ETH). - **Others:** **13.4M ETH** (67% of 20M ETH). Since client teams should get **~1.1x** the share of a staking operator, let: - Each **client team** get **X** ETH. - Each **staking operator** get **0.9X** ETH. --- ## Final Allocation: | Group | ETH per entity | Total ETH | |---------------------|--------------|-----------| | **Ethpandaops** | 6.6M | 6.6M | | **Each Client Team** (11x) | 864.5K | 9.5M | | **Each Staking Operator** (5x) | 778K | 3.9M | **Total Staked ETH: 20M ETH** --- ## Validators Per Group Each validator holds between **32-2048 ETH**, so: ### If using **32 ETH validators**: - **Ethpandaops**: **206 000 validators** - **Client teams**: ~**27 000 validators** each. - **Staking operators**: ~**25 000 validators** each. - **Total number of validators**: ~**625 000** ### If using **2048 ETH validators**: - **Ethpandaops**: ~**3200 validators** - **Client teams**: ~**422 validators** each. - **Staking operators**: ~**380 validators** each. - **Total number of validators**: ~**10 000 validators** --- # Hoodi Testnet - Plan B (Increased Validator Count) This write-up details an alternative validator distribution for the Hoodi testnet, where the total number of validators reaches **1.2M** (assuming 32 ETH per validator). This plan follows the same proportional stake distribution as **Plan A**, but increases the total staked ETH accordingly. ## 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 number of validators:** **1,200,000** - **Each validator balance:** **32 ETH** - **Total staked ETH:** **38.4M ETH** --- ## Plan B - Bigger than mainnet Start with a bigger state than mainnet -> consolidate later -> big queue ## Stake Distribution - **Ethpandaops**: **12.67M ETH** (33% of 38.4M ETH). - **Others:** **25.73M ETH** (67% of 38.4M ETH). Since client teams should get **~1.1x** the share of a staking operator, let: - Each **client team** get **X** ETH. - Each **staking operator** get **0.9X** ETH. --- ## Final Allocation: | Group | ETH per entity | Total ETH | |---------------------|--------------|-----------| | **Ethpandaops** | 12.67M | 12.67M | | **Each Client Team** (11x) | 1.66M | 18.26M | | **Each Staking Operator** (5x) | 1.49M | 7.45M | **Total Staked ETH: 38.4M ETH** --- ## Validators Per Group ### If using **32 ETH validators**: - **Ethpandaops**: **396,000 validators** - **Each Client Team**: **51,875 validators** each. - **Each Staking Operator**: **46,562 validators** each. - **Total number of validators**: **1,200,000** ### If using **2048 ETH validators**: - **Ethpandaops**: ~**6188 validators** - **Client teams**: ~**811 validators** each - **Staking operators**: ~**729 validators** each - **Total number of validators**: ~**18,750 validators** ---