KVORUM
lidoSource: Snapshot · #0xf7b718e7807f763ba826735781145dd06b79b0228b37b74a22dd5ac252e03c40

Community Staking Module v2. Architecture and Fee Structure

succeededMay 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

784 words

This proposal outlines the architecture description and staking rewards allocation (fee structure) for the proposed major upgrade of the Lido Community Staking Module called CSM v2.

Motivation

The current version of CSM has been immensely successful in pushing the decentralization of Lido on Ethereum. It allows Node Operators to join the Lido on Ethereum protocol permissionlessly and receive Node Operator rewards without needing to put up the entire 32 ETH minimum of a validator. However, some limitations and challenges remain that need to be addressed to make CSM more robust, flexible, and competitive.

One of the main challenges is the need to support different types of Node Operators, such as permissionless operators, identified community stakers, professional Node Operators, etc to allow for an incentive separation between these groups. One of the main incentives that CSM offers to Node Operators is Node Operator rewards. Currently, CSM allocates 6% of the staking rewards (pro-rata based on the share of active validators operated by each Node Operator within the module) to Node Operators. These conditions make the CSM reward structure way above the current permissionless staking solutions in terms of the bond required to rewards ratio and should be adjusted to fit the market.

CSM v2 Architecture

CSM v2 is a major upgrade of the currently operational CSM v1 aimed at making CSM more robust, flexible, and user-friendly. A detailed description of CSM v2 architecture and features can be found in LIP-29 and the corresponding landscape document.

The main changes and new features of CSM v2 are:

  • Introduction of Node Operator types defined by the bond curve. With the addition of the CSParametersRegistry.sol contract, most of the Node-Operator-related parameters (bond curve, rewards curve, performance threshold, ad hoc charges, penalty amounts, etc.) in CSM can now be individually configured for each Node Operator type for further usage by on and off-chain components of CSM;
  • Entry gates and extensions allow for customizable entry conditions for Node Operators. While maintaining permissionless entry via PermissionlessGate.sol, CSM will now be able to have customizable VettedGates deployed via VettedGateFactory.sol, which will essentially be responsible for assigning Node Operator types, and attached to the module based on the Lido DAO decision;
  • Improved Performance Oracle algorithm allows for more precise accounting of CSM validators' performance. In CSM v2, the Performance Oracle now features accounting for block proposals and sync committee participation with customizable weight coefficients for each duty in the overall performance score;
  • A strikes system is added to CSM v2 to protect CSM and the overall protocol from systematic bad performers (CSStrikes.sol). Simply put, in cases where CSM validators show sub-par performance over a sufficient period, it will be possible to eject them permissionlessly;
  • EIP-7002 support in CSM v2 serves as a technical enabler for the Strikes System while also allowing Node Operators to voluntarily eject their validators using EL-initiated triggerable withdrawals mechanism (CSEjector.sol);
  • Several improvements and clean-ups have been made in CSM v2 to further improve operational efficiency and extend possible use cases of CSM.

CSM v2 Fee Structure

The introduction of the Node Operator types will allow CSM v2 to offer differentiated protocol interactions between Identified Community Stakers and other permissionless participants, and other possible types in the future as well if the DAO chooses to enable them.

To keep CSM competitive with the permissionless staking market and continue enfranchising community stakers' participation in Lido on Ethereum protocol, it is proposed to:

  • Set the default Node Operator reward share to 3.5% while keeping bond requirements unchanged, fulfilling the goals set out in the CSM Evolution post, allowing CSM to scale while enabling competitive rewards with other modules and the rest of the market. This would result in a default maximum CSM v2 capital multiplier of 1.76, which is still market-leading but not overly unbalanced compared to other modules (where node operator share of rewards may also be reconsidered in the future).
  • Maintain the current Node Operator reward share (6%) for the first 16 validators (21 ETH worth of bond) while keeping bond requirements unchanged, for Identified Community Stakers in CSM v2.

A detailed description and motivation for the proposed changes are reflected in the following post and discussion on the Lido Research Forum.

Next Steps

If the proposed changes are supported by the Lido DAO:

  • Lido contributors working on CSM will proceed with the development, testing, and preparation of the CSM v2 mainnet release, adhering to the approved design.
  • The approved fee structure will be applied for CSM alongside testnet and mainnet releases.
  • CSM v2, together with the new fee structure, will be proposed for the final DAO approval through one of the upcoming Aragon on-chain votes.

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

Voters110
VP participating0
Outcome (current)For
Current support100%

06Voters

110 total
Filter:
VoterChoice% of totalRationale
420x42e6…3fb0For019.64%—2y ago
6C0x6cd6…b52eFor014.05%—2y ago
810x8172…922eFor010.35%—2y ago
7E0x7ee0…bb6cFor09.85%—2y ago
6D0x6d8d…0cccFor08.17%—2y ago
LIlido.banteg.eth0x55bc…f0faFor06.82%—2y ago
B90xb933…8dd1For04.84%—2y ago
A40xa418…b737For04.58%—2y ago
AE0xae09…256bFor04.52%—2y ago
3F0x3fb1…4c8aFor03.28%—2y ago
B60xb664…f890For02.39%—2y ago
6F0x6f9b…8a1dFor02.36%—2y ago
1F0x1f76…5ed6For02.13%—2y ago
7A0x7a59…8e22For01.57%—2y ago
390x3983…777aFor01.37%—2y ago
870x8787…ea52For00.76%—2y ago
E80xe80e…28e8For00.63%—2y ago
2C0x2cc1…4df1For00.55%—2y ago
290x29b5…2c2fFor00.32%—2y ago
620x624d…2cd0For00.28%—2y ago
100x10a2…36f3For00.28%—2y ago
B30xb3ba…ebc5For00.27%—2y ago
5D0x5df9…1b53For00.27%—2y ago
3D0x3ddc…05b0For00.16%—2y ago
980x9830…bd94For00.16%—2y ago
060x06a9…bba0For00.15%—2y ago
230x2345…dbeeFor00.14%—2y ago
490x49f1…6cdbFor00.04%—2y ago
8A0x8ab6…e0baFor00.03%—2y ago
230x23e6…fb17For00.02%—2y ago
CE0xcedf…614bFor00.01%—2y ago
7A0x7af3…8df3For00.00%—2y ago
C50xc554…7759For00.00%—2y ago
270x27d3…f70aFor00.00%—2y ago
DB0xdbbc…1cb6For00.00%—2y ago
3D0x3d5a…b97fFor00.00%—2y ago
B10xb1f8…4250For00.00%—2y ago
B70xb792…89d7For00.00%—2y ago
EC0xecc2…6ac9For00.00%—2y ago
430x431b…a303For00.00%—2y ago
C10xc1c2…24f8For00.00%—2y ago
530x53c4…3584For00.00%—2y ago
8B0x8bc8…7276For00.00%—2y ago
CE0xce4f…6cf3For00.00%—2y ago
C40xc48b…75b6For00.00%—2y ago
2D0x2d67…ac5cFor00.00%—2y ago
270x2748…ac26For00.00%—2y ago
9D0x9d57…65a5For00.00%—2y ago
050x0579…ca09For00.00%—2y ago
2F0x2f2f…f78aFor00.00%—2y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.