This page summarizes the operational changes introduced by Curated Module v2 (CMv2). It complements the Migration Guide and focuses on day-to-day operational impacts, not the migration process itself.
| Category | CMv1 | CMv2 | Operational Impact |
|---|---|---|---|
| Validator Type | 0x01 withdrawal credentials | 0x02 withdrawal credentials | Generate and operate a new fleet of 0x02 validators. Existing validator keys cannot be reused. |
| Operator structure | Node Operator | ||
| -> Validators | Operator Group (Entity) | ||
| -> Sub-operator(s) | |||
| -> Validators | Manage multiple Sub-operators, each with its own configuration, bond, rewards address, and validator set. | ||
| Bonding | No bond required | Bond required per Sub-operator | Allocate and maintain bonded capital for each Sub-operator before validators become depositable. |
| Operator Types | Standard / Client / Extra Effort | PTO / PO / PGO / DO / EEO / IODC / IODC+ | Module parameters (such as fee caps and bonding requirements) depend on your assigned Operator Type. |
| Monitoring | Standard validator monitoring | Compounding validator monitoring | Update monitoring dashboards and alert thresholds for 0x02 type validators. |
| Validator Exits | Monitor VEBO and operate Ejector | Monitor VEB and operate Ejector | Exit processing follows the updated Validator Exit Policy. Failure to process exit requests within the required SLA may result in protocol-enforced handling and bond-funded penalties. |
| Capacity Management | Upload depositable keys when needed | Maintain depositable 0x02 validators and sufficient bond | Capacity planning becomes an ongoing operational responsibility throughout the migration and beyond. |
The following changes apply only during the migration period:
| Area | What Changes |
|---|---|
| Dual Operations | CMv1 and CMv2 will operate simultaneously until migration is complete. Both environments must remain healthy throughout the transition. |
| Migration buffer | Maintain at least 500 active validators in CMv1 until instructed otherwise, to continue serving validator exits and provide operational fallback. |
| Seeding | Initial deposits prioritize activating CMv2 validators before stake migration begins. |
| Top-ups | Top-ups become available after Period 1.5, once CMv2 validators are active. |
| Capacity Planning | Keep approximately 10 depositable CMv2 validators available at all times, and ensure sufficient bond to support future deposits. |
| Stake Allocation | During migration, deposits may temporarily be directed to different modules depending on migration progress. After Period 2, CM v1 will no longer accept deposit. |
In addition to your existing operational responsibilities, CMv2 introduces several new workflows.
All regular operational activities can be performed directly through the new CMv2 UI.
Monitoring requirements expand during migration. In addition to existing validator monitoring, operators should track: