Lido approves intra-operator DVT rules for Curated Module operators

What happened

Lido tokenholders approved guidelines allowing Curated Module node operators to adopt self-run Obol or SSV distributed-validator clusters under specified limits and safeguards.

What changed

Operators may split up to the lesser of 1,000 or 20% of active validator keys after testnet validation, add DVT keys produced through vetted verifiable DKG, and participate under revised provider-incentive allocations.

What did not change

The approval does not require every operator to adopt DVT, does not itself migrate validator keys, and does not establish the security or performance of any specific operator cluster.

Confirmed

• Curated Module DVT adoption is optional and limited to intra-operator clusters.
• Migration by an operator is capped at the lesser of 1,000 or 20% of its active validator keys.
• Obol and SSV are the identified DVT providers.
• Curated Module operators receive 20% of provider incentives, with 80% directed to the Mellow Decentralized Validator Vault.

Still open

• Which operators opt in and how many validators migrate.
• The final contributor-vetting process for DKG and key-shard procedures.
• Operational concentration, correlated-failure, and slashing behavior of deployed clusters.
• Whether incentive routing changes after implementation.

What it means for an advisor

• Update Lido's validator and key-management control map to include intra-operator DVT, DKG review, migration limits, and provider dependencies.
• Monitor operator-level adoption and slashing performance before interpreting DVT approval as a reduction in operational risk.