Core differences

Category CMv1 CMv2 What this means for you
Validator type 0x01 withdrawal credentials 0x02 withdrawal credentials You must generate 0x02 keys for CMv2 validators
Operator admin 1 entity = 1 operator 1 entity may have multiple sub-operators You manage multiple sub-operators
Bond Not required Bond required per sub-operator You must plan bond capital allocation and post bond per sub-operator
Operator types No differentiation PTO / PO / PGO / DP / VMODVC / DVSC Different types have different parameters/requirements. (see FAQ for more details)
Monitoring Standard validator monitoring Monitoring must support fewer, higher-balance 0x02 validators (up to 2048 ETH) You must adjust alerting thresholds and dashboards. Each validator represents more stake, so missed duties/outages have larger consequences.
Validator Exit • VEBO + voluntary exit messages • VEBO + voluntary exit messages (same)
• Support Triggerable Exit (7002) • Validator exit infra still need to be maintained same as now. (for regular validator exit apply to both 0x01 and 0x02 validators)
• ??

Migration execution

Category Migration change What this means for you Suggested specific items
EasyTrack • specify the CMv1 source operator and CMv2 target operator
• set the consolidation manager address which will be allowed to initiate consolidation actions This is a new type of easy track you are responsible to execute.
EasyTrack Consolidations executed in batches This is a new type of easy track. You will prepare + submit consolidation requests in batches).
Monitoring CMv1 + CMv2 overlap You’ll need dashboards/alerts that cover validators in both CM v1 and CM v2.
Monitoring Consolidation progress tracking Track which of your validators are queued, in progress, or completed.
Other Source and target validators mapping • Overview of how your validators map to infrastructure (hosts, clusters, signers)
• Overview of source validators (CM v1) and target validators (CM v2) On source validators:
• Active-ongoing

What stays the same