Lido approves the CSM v2 final rollout

What happened

Lido tokenholders approved the final rollout plan for Community Staking Module v2.

What changed

The approval finalized a migration and operating framework with permissionless, Legacy Early Adopter, and Identified Community Staker operator types, EIP-7002 support, revised performance accounting, and committee reimbursement funding.

What did not change

CSM v2 was not deployed in July, existing operators were not yet migrated, and pending audits and later on-chain execution remained necessary.

Confirmed

• The Snapshot ended on July 28, 2025 with approximately 52.35 million LDO voting for and about 12 LDO against.
• The approved rollout defines three initial node-operator types.
• The design includes EIP-7002 support and an updated Performance Oracle.
• The Identified Community Stakers framework uses address-ownership proofs and published eligibility scoring.
• The proposal includes 10 stETH of committee funding for eligible reimbursement of incorrectly penalized operators.

Still open

• Final audit findings and remediation.
• The on-chain upgrade vote, execution date, and deployed contract state.
• Final operator classifications, bond curves, module allocation, and committee permissions.
• Effects on validator concentration, performance-oracle errors, penalties, reimbursements, and withdrawal behavior.

What it means for an advisor

• Supersede the May architecture-stage interpretation with final-rollout approval while retaining a non-operative posture.
• Review final code, audits, operator classifications, committee authority, performance accounting, and executed module limits before updating Lido suitability conclusions.

Previous interpretation

The May event established approval of the CSM v2 architecture and fee structure but not the final rollout plan, finalized operator framework, reimbursement authority, or production authorization.