# Lido approves CMv2 and CSMv3 architecture and rollout plan

> 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.

- URL: https://riadefi.com/on-chain/2026-06-22-lido-lip-33-cmv2-csmv3-architecture-approval/
- Type: Upgrade or migration
- Stage: Approved, not executed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-06-22
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2026-08-26
- Advisor-relevant: no
- Affects: Lido (protocol)

## 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.

## Sources

1. [LIP-33: CMv2 and CSMv3 Architecture, Key Parameters, Rollout Plan](https://snapshot.org/#/lido-snapshot.eth/proposal/0x7b07bc31f0b38b69a117473031bc126becc70b9fa37246b53d9fe5a841c814f5) · Lido DAO via Snapshot · 2026-06-15


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.