Overview

⚠️ This guide covers how existing Curated Module Node Operators will transition their mainnet validators to Curated Module v2 (CMv2). The process differs from Hoodi testnet in several important ways - please read carefully.

This 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: following the successful completion of the Hoodi testnet migration, Mainnet onboarding is expected to start in late July.

• Existing CMv1 validators are consolidated into new CMv2 validators, no validator recycling required
• Node Operators should be ready to onboard and submit all keys and bond as soon as the module is released
  • Validators must pass through the Ethereum entry queue before they are active, and delays in submitting keys will push back your consolidation start.
  • If incoming deposits are insufficient to cover the required seed deposits for 0x02 validators in a timely manner, NOM may ask NOs to voluntarily exit validators to help meet the requirements.
• To minimize the overall migration timeline, Node Operators may start consolidating as soon as CMv2 keys are available. Once sufficient CMv2 capacity is live, completing your migration will become mandatory.
  • NOM team will monitor progress and follow up with operators as needed.
• Please maintain at least 500 active keys in the old CM throughout the process to serve exits; the buffer of depositable keys should also be maintained until NOM confirms they won’t be needed anymore
• Additionally, NOs should keep ~10 extra depositable keys across their CMv2 group at all times to maintain capacity for incoming stake deposits
• The technical migration progresses through defined periods (see below)
  • Migration Periods

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, IODC) 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 CM to CMv2:

Node Operator Changes: CMv1 > CMv2

</aside>

Migration Plan