KVORUM
lidoSource: Snapshot · #0xc3f92bcdf8926cfa7528ca6a979c0fdce1e4d0cfaaa72dd6410a76a2e1e55766

CSM v2 Final Rollout

succeededJul 28, 2025, 04:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

1,071 words

TL;DR

Community Staking Module (CSM) v2 is a major Lido on Ethereum protocol’s Community Staking Module upgrade that enhances the module’s security, efficiency, and decentralization.

This proposal seeks Lido DAO approval for the final rollout of CSM v2, including the release plan, finalized key parameters, Community Stakers’ Identification Framework, an adjustment of the stakeShareLimit, and operational funding for the CSM Committee to process reimbursements.

This proposal builds on the prior DAO approval of the module’s architecture and design.

If this proposal is supported, the next step will be the on-chain vote to upgrade CSM to version 2, along with the coordinated rollout of accompanying measures outlined in this proposal.

CSM v2 Deployment Overview

Community Staking Module (CSM) v2 is an evolutionary step in the CSM development, which adds support for EIP-7002, enabling more secure and flexible validator withdrawals, includes an improved Performance Oracle for more accurate validator performance tracking, and introduces distinct Node Operator types to support a more structured and scalable operator model.

The detailed CSM v2 release plan description is posted on the Lido Research Forum including the latest version of the timeline. The main points for consideration are outlined below.

Parameters for Node Operator types

Upon release, CSM v2 will feature the following three Node Operator Types: Permissionless, Legacy EA (Early Adopters), and Identified Community Stakers (ICS).

The actual values for the NO type parameters are available on IPFS, and a detailed description and motivation are provided in the corresponding post on Lido Research Forum.

Note. The "Legacy EA" NO type is introduced to ensure a smooth migration from the current CSM v1 Node Operator structure. All existing CSM EA Node Operators will be automatically classified under this new type. This NO type will share all parameters with the "Permissionless" Node Operator type, except the bond curve, which will be the same as for the "ICS" Node Operator type.

Community Stakers Identification Framework

The Community Stakers Identification Framework is introduced to enhance the decentralization of both CSM and the Lido protocol by providing a clear pathway for community stakers to join CSM and receive beneficial conditions. The core idea of the identification framework is to assess verified applications from users.

Verification is performed by requiring applicants to confirm ownership of the submitted addresses by signing a message and publishing it.

The evaluation is based on three categories of proofs: Proof-of-Experience, Proof-of-Engagement, and Proof-of-Humanity. The list of assessment sources for each category with the corresponding scores is published on the Lido Research Forum (alongside a detailed description of the framework). If the addresses and additional information provided in the application result in a sufficient score in each category, the primary address from the application will be included in the next amendment batch for the ICS list.

Updates to the ICS list are proposed to be performed via a dedicated Easy Track motion type. As part of a recurring process for each update, CSM Committee members verify the amendment batch, prepare an updated version of the ICS list, and start an Easy Track motion to apply the update.

To reduce the time and effort required, the initial ICS list is proposed to be formed from the existing CSM EA Node Operators that pass a simplified assessment described in the corresponding post. Voters can find the proposed initial ICS list on IPFS and in the post on the Lido Research Forum.

If approved, this framework will be used by Lido contributors and CSM Committee members to identify independent community stakers and allow them to join CSM with the "ICS" NO type. Existing CSM operators will also be able to get qualified as identified community stakers and upgrade their NO type to the "ICS". Future maintenance of the framework, including source addition and removal, scores adjustment, updates, and pausing, is proposed to be managed by the CSM Committee.

CSM stakeShareLimit increase

To enable a meaningful usage of the great features of CSM v2 and increase decentralization of the Lido protocol, a phased increase of the CSM stakeShareLimit is proposed:

  • Increase CSM stakeShareLimit to 5% alongside CSM v2 release;
  • Following stake distribution and performance analysis, increase CSM stakeShareLimit to 10% by late 2025 or early 2026.

A detailed motivation and supporting considerations for the proposed increase schedule are provided in the corresponding post.

Audits

CSM v2 on-chain code is currently undergoing 3 security audits by Ackee, Statemind, and Code4rena to ensure code security and robustness. The required condition for the CSM v2 mainnet release is at least 2 finalized reports with no unresolved findings.

Budget allocation for MEV-stealing-related reimbursements

CSM includes a mechanism that allows for the burning of bonded funds in cases of operator misbehavior or non-performance. However, there may be edge cases where an initial assessment triggers a penalty, but a more thorough post-incident review reveals that the Node Operator acted correctly and in accordance with Lido protocol guidelines.

To account for such situations, it is proposed that the CSM Committee be granted the discretion to compensate affected operators using a dedicated budget if it is determined that the penalty application was unjustified. The compensation fund is proposed to be initially supplied with 10 stETH from the Gas Supply Committee, specifically allocated to cover slashed Node Operators’ bonds under CSM. Should this budget be depleted, any additional funding would be requested from the Lido DAO.

Next Steps

If the Lido DAO supports the proposed changes, Lido contributors will:

  • Initiate an on-chain vote to upgrade CSM to version 2 on the Ethereum mainnet, following the completion of at least two security audits with no unresolved findings;
  • Use the approved parameters for Node Operator types and the initial ICS list during the CSM v2 deployment;
  • Apply the approved Community Stakers Identification Framework to assess user applications and add eligible applicants to the ICS list in CSM v2, and continue using the framework for future list adjustments;
  • Grant the CSM Committee the right to maintain and adjust the Community Stakers Identification Framework;
  • Include the necessary steps to increase the stakeShareLimit to 5% in one of the upcoming on-chain votes;
  • Perform stake distribution and performance analysis of CSM v2 in Q3-Q4 2025, and, based on the results, move forward with proposing a stakeShareLimit increase to 10% via an upcoming on-chain vote;
  • Allocate the 10 stETH MEV-stealing-related compensation budget from the Gas Supply Committee to the CSM Committee multisig.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters109
VP participating0
Outcome (current)For
Current support100%

06Voters

109 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bFor024.36%—1y ago
420x42e6…3fb0For019.11%—1y ago
810x8172…922eFor011.20%—1y ago
6D0x6d8d…0cccFor07.69%—1y ago
9C0x9ca8…36afFor06.00%—1y ago
510x510a…8d0eFor05.78%—1y ago
B90xb933…8dd1For04.71%—1y ago
A40xa418…b737For04.44%—1y ago
3F0x3fb1…4c8aFor03.19%—1y ago
1F0x1f76…5ed6For02.69%—1y ago
B60xb664…f890For02.57%—1y ago
6F0x6f9b…8a1dFor02.32%—1y ago
7A0x7a59…8e22For01.37%—1y ago
390x3983…777aFor01.34%—1y ago
870x8787…ea52For00.72%—1y ago
E80xe80e…28e8For00.61%—1y ago
2C0x2cc1…4df1For00.54%—1y ago
6A0x6a39…4bd2For00.32%—1y ago
290x29b5…2c2fFor00.32%—1y ago
3D0x3ddc…05b0For00.19%—1y ago
980x9830…bd94For00.15%—1y ago
060x06a9…bba0For00.15%—1y ago
3D0x3d63…4afcFor00.12%—1y ago
4D0x4d6c…5aaeFor00.06%—1y ago
8A0x8ab6…e0baFor00.03%—1y ago
1A0x1a2f…1c0aFor00.03%—1y ago
7A0x7af3…8df3For00.00%—1y ago
C50xc554…7759For00.00%—1y ago
270x27d3…f70aFor00.00%—1y ago
DB0xdbbc…1cb6For00.00%—1y ago
3D0x3d5a…b97fFor00.00%—1y ago
C60xc634…3c18For00.00%—1y ago
5B0x5b65…3789For00.00%—1y ago
B10xb1f8…4250For00.00%—1y ago
DD0xdd9d…3804For00.00%—1y ago
B70xb792…89d7For00.00%—1y ago
EC0xecc2…6ac9For00.00%—1y ago
C10xc1c2…24f8For00.00%—1y ago
530x53c4…3584For00.00%—1y ago
A40xa40d…14a9For00.00%—1y ago
C40xc48b…75b6For00.00%—1y ago
050x0579…ca09For00.00%—1y ago
9D0x9d57…65a5For00.00%—1y ago
D50xd5d7…3c4dFor00.00%—1y ago
2D0x2d67…ac5cFor00.00%—1y ago
2F0x2f2f…f78aFor00.00%—1y ago
5A0x5a2c…fdcfFor00.00%—1y ago
390x396d…c3ddFor00.00%—1y ago
7D0x7d3b…f16aFor00.00%—1y ago
140x14af…2531For00.00%—1y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.