Lido approves CMv2 and CSMv3 architecture and rollout plan

What happened

Lido DAO approved LIP-33's architecture, parameters, governance model, and rollout plan for Curated Module v2 and Community Staking Module v3.

What changed

The approved design adds 0x02 withdrawal-credential support, large validators, new bonding and penalty mechanics, more granular roles, weighted Curated Module allocation, and a proposed 15% CSM stake-share upper bound.

What did not change

The vote did not deploy the modules, migrate validators, or prove that the audited production code and live parameters match the approved design.

Confirmed

• The vote closed on June 22 with all recorded voting power in favor.
• CMv2 and CSMv3 share substantial code and depend on Staking Router v3.
• CSMv3 introduces reward splitting, semi-automated penalties, and more granular operator-type roles.
• CMv2 introduces bonding, weighted stake allocation, a node-operator meta registry, and foundations for a validator marketplace.

Still open

• Security audits, final production code, deployment timing, and live Easy Track permissions remain unconfirmed.
• The realized effect on operator concentration and the combined CSM and Simple DVT share is unresolved until rollout.

What it means for an advisor

• Review module-level governance roles, bonding, penalty, and allocation controls before recognizing the upgrade as operative.
• Track whether the rollout improves or weakens operator diversity relative to Lido's memo criteria.
• Verify deployed parameters, especially the CSM stake-share limit and Easy Track permissions.