Overview

This guide explains how existing Hoodi Curated Module Node Operators will transition their validators to Curated Module v2 (CMv2).

The migration uses Ethereum validator consolidations to move stake from 32 ETH (0x01) validators into higher-balance 0x02 validators (max. 2048 ETH), reducing validator count while preserving stake and operator responsibility.

Timeline: Mainnet migration is expected to start in Q2-Q3 2026 and will run for several months. In anticipation, Hoodi migration will start in early April.

• Existing CMv1 validators are consolidated into new CMv2 validators, no validator recycling required
• Node Operators initiate migration one by one, following the migration schedule (*** see Hoodi Migration Schedule)
• Consolidation is a two-step process: 1) Create a 0x02 key and seed it with 32 ETH 2) Consolidate 0x01 keys into the new 0x02 validator up to the limit
• Stake moves gradually over the migration window. The testing period concludes after 1,000 keys are successfully migrated

Concepts

1. 0x01 vs 0x02 validators: CMv1 uses standard 32 ETH (0x01) validators. CMv2 runs only 0x02 validators, which hold higher effective balances (up to 2048 ETH) and reduce validator count.
2. Validator consolidations: Migration uses Ethereum's validator consolidation mechanism to move stake from existing 0x01 validators into newly created 0x02 validators, no exits or redeposits required. Each consolidation takes approximately 256 epochs (~1.14 days) to complete plus the variable queue time.
3. Sub-operators: In CMv2, a Node Operator can create multiple Sub-operators that represent a sub-section of their infrastructure, each with its own configuration, bond, and operator type. Sub-operators are the primary unit for bonding and operational enforcement.
4. Node Operator types: CMv2 introduces operator categories (e.g., PTO, PO, PGO, DO, VMODVC) that determine key parameters like fee caps and bonding requirements.
5. Node Operator group: the CMv2 structure that defines how stake allocation is distributed across one or more Sub-operators (and optionally external operators). It groups related operators together and assigns them relative shares, which are used to calculate their effective weight in stake distribution.

Key Dates & Milestones

What Changes for You

<aside> 💡

Please carefully read and confirm the expected changes for Node Operators migrating from CMv1 to CMv2:

Node Operator Changes: CMv1 > CMv2

</aside>

Migration Plan

Phase 1 - Preparation

Phase 2 - CMv2 Setup and Initial Seeding

Phase 3 - Consolidation Migration