KVORUM
lidoSource: Snapshot · #0x7cbd5e9cb95bda9581831daf8b0e72d1ad0b068d2cbd3bda2a2f6ae378464f26

CSM: Enable Permissionless Phase and Increase the Share Limit

succeededDec 23, 2024, 04:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

405 words

Tl;DR

It is proposed to complete the Early Adoption phase and transition CSM to a fully permissionless mode by activating public release alongside a share increase from 1% to 2% to ensure further expansion of the Lido protocol decentralization.

Preface

Community Staking Module (CSM) was added to the Lido on Ethereum protocol on October 25, 2024, via on-chain vote #180. This was a significant step towards decentralization of the Lido protocol. Since adding the module, more than 230 Node Operators have joined the protocol (see Community staking dashboard → Node Operators).

One of the main factors limiting further decentralization of the Lido on Ethereum protocol is the current share limit of the CSM. Due to security and safety considerations, the initial share limit was set to 1% of the protocol Total Value Locked (TVL). Today, CSM has already occupied ~0.56% of the protocol TVL and keeps growing (see Community staking dashboard → Current share), making the question of raising the share limit increasingly relevant.

On-chain data about CSM validators’ performance collected by the Rated network shows that, on average, CSM validators perform slightly below Lido Curated operators.

CSM is currently in its Early Adoption phase, which ensures that most Node Operators are independent participants, each runs up to 12 validators, with an average validator count of slightly fewer than 7 validators per Node Operator.

According to the on-chain data, the number of new operators joining CSM weekly has decreased, indicating that most of the addresses eligible for Early Adoption had already joined. Also, several participants have expressed interest (in Lido Discord) in running more than 12 validators, which is currently restricted.

To sum up, the Early Adoption phase means that only eligible participants can join the module and they have a limit of 12 validators per Node Operator. These two factors, in turn, mean that CSM is not yet fully permissionless. And the Lido DAO faces an important topic to consider - turning off the Early Adoption phase to make the module fully permissionless.

The current distribution of validators among Node Operators in the CSM and the module's generally acceptable performance suggest a stable foundation. Based on this, it is reasonable to assume that the risks of the proposed changes can be effectively evaluated using the existing risk assessment research.

Next steps

If this proposal is supported by the DAO, these actions will be included in one of the upcoming 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

Voters115
VP participating0
Outcome (current)For
Current support100%

06Voters

115 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bFor022.22%—2y ago
810x8172…922eFor010.51%—2y ago
7E0x7ee0…bb6cFor08.63%—2y ago
LIlido.banteg.eth0x55bc…f0faFor06.19%—2y ago
6D0x6d8d…0cccFor06.11%—2y ago
A40xa418…b737For06.07%—2y ago
510x510a…8d0eFor05.91%—2y ago
B90xb933…8dd1For04.60%—2y ago
3D0x3ddc…05b0For04.39%—2y ago
FF0xff41…a67bFor04.30%—2y ago
110x1109…43daFor03.51%—2y ago
CE0xce3b…2e55For03.44%—2y ago
BE0xbeb3…7646For03.27%—2y ago
6A0x6a39…4bd2For02.29%—2y ago
1F0x1f76…5ed6For01.93%—2y ago
7A0x7a59…8e22For01.19%—2y ago
A20xa2ff…7be9For01.07%—2y ago
B60xb664…f890For00.60%—2y ago
870x8787…ea52For00.56%—2y ago
E80xe80e…28e8For00.55%—2y ago
2C0x2cc1…4df1For00.48%—2y ago
F50xf5e3…6e42For00.48%—2y ago
6F0x6f9b…8a1dFor00.34%—2y ago
290x29b5…2c2fFor00.29%—2y ago
100x10a2…36f3For00.24%—2y ago
620x624d…2cd0For00.21%—2y ago
980x9830…bd94For00.14%—2y ago
060x06a9…bba0For00.14%—2y ago
3D0x3d63…4afcFor00.11%—2y ago
780x78d1…753aFor00.07%—2y ago
610x61cc…87d1For00.05%—2y ago
5F0x5fdc…b69fFor00.04%—2y ago
3F0x3fb1…4c8aFor00.02%—2y ago
500x50ed…e1b2For00.02%—2y ago
9E0x9e0b…da3aFor00.01%—2y ago
050x0579…4048For00.00%—2y ago
420x42e6…3fb0For00.00%—2y ago
8A0x8ab6…e0baFor00.00%—2y ago
7A0x7af3…8df3For00.00%—2y ago
DB0xdbbc…1cb6For00.00%—2y ago
3D0x3d5a…b97fFor00.00%—2y ago
5E0x5e45…3248For00.00%—2y ago
6A0x6a2d…03e0For00.00%—2y ago
5A0x5a51…347cFor00.00%—2y ago
2F0x2f15…631fFor00.00%—2y ago
580x5820…a011For00.00%—2y ago
060x0638…b602For00.00%—2y ago
B70xb792…89d7For00.00%—2y ago
ED0xed95…68a6For00.00%—2y ago
520x5243…3440Against00.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.