KVORUM
lidoSource: Snapshot · #0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e

CSM: stakeShareLimit and keyRemovalCharge parameters adjustment

succeededApr 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

496 words

In the light of active development and preparations for Community Staking Module (CSM) v2 it is proposed to adjust several parameters for the current version of CSM, namely: increase stakeShareLimit from 2% to 3% upon reaching certain conditions and reduce keyRemovalCharge from 0.05 ETH to 0.02 ETH.

1. Increase stakeShareLimit to 3%

CSM has reached its stake share limit of 2%. This means that new validators in CSM can be deposited to only if the total Lido protocol TVL increases or some of the current validators exit. This fact limits the future growth of the Lido on Ethereum Node Operator set. Currently, it is estimated that about 50 net-new Node Operators are in the CSM deposit queue.

Proposal: If the below-stated conditions are met, increase the CSM stake share limit (stakeShareLimit) from the current 2% to 3%.

To maintain consistency of the stake share limit parameters in the Staking Router, it is also proposed to set the priorityExitShareThreshold to 375 BP (3.75%) to maintain the existing ratio.

Conditions for further on-chain implementation:

Proceeding with a change to the CSM stake share limit should take into account stake distribution across other Lido on Ethereum modules:

But, if CSM v2 release is supported by the Lido DAO via a separate snapshot vote and ready before the conditions above are met, the CSM Stake Share Limit can be increased alongside the v2 on-chain release, regardless of whether those conditions have been fulfilled.

2. Reduce keyRemovalCharge to 0.02 ETH

The keyRemovalCharge is a safety parameter in CSM, initially set to 0.05 ETH, with the rationale detailed in the original post.

Since that time, Ethereum gas prices have significantly decreased — the 8-month average is ~11 Gwei. For conservative estimation, we use a higher value of 20 Gwei as the maximum expected gas price.

Following the same methodology used in the original calculation: Estimated gas cost for queue cleanup: 1,000,000 gas * 20 Gwei = 0.02 ETH

Proposal: reduce keyRemovalCharge from 0.05 ETH to 0.02 ETH to ensure the parameter remains aligned with current network conditions while maintaining its safety function and not adding unreasonable operational costs to CSM Node Operators.

Next Steps

If the proposed changes are supported by the Lido DAO:

  • the CSM Stake Share Limit increase (alongside priorityExitShareThreshold) will be included either in the next available on-chain vote once the outlined conditions are met, or can be a part of the CSM v2 release if CSM v2 release is supported by the Lido DAO in a separate Snapshot vote and happens before those conditions are fulfilled;
  • keyRemovalCharge parameter value will be changed in one of the next 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

Voters65
VP participating0
Outcome (current)For
Current support100%

06Voters

65 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bFor019.88%—2y ago
420x42e6…3fb0For015.66%—2y ago
6C0x6cd6…b52eFor011.19%—2y ago
810x8172…922eFor08.25%—2y ago
6D0x6d8d…0cccFor06.04%—2y ago
LIlido.banteg.eth0x55bc…f0faFor05.64%—2y ago
9C0x9ca8…36afFor04.92%—2y ago
510x510a…8d0eFor04.73%—2y ago
B90xb933…8dd1For03.84%—2y ago
A40xa418…b737For03.64%—2y ago
AE0xae09…256bFor03.60%—2y ago
3F0x3fb1…4c8aFor02.61%—2y ago
1F0x1f76…5ed6For01.99%—2y ago
B60xb664…f890For01.94%—2y ago
6A0x6a39…4bd2For01.69%—2y ago
7A0x7a59…8e22For01.26%—2y ago
6F0x6f9b…8a1dFor00.67%—2y ago
870x8787…ea52For00.60%—2y ago
E80xe80e…28e8For00.50%—2y ago
2C0x2cc1…4df1For00.44%—2y ago
290x29b5…2c2fFor00.26%—2y ago
100x10a2…36f3For00.22%—2y ago
980x9830…bd94For00.13%—2y ago
060x06a9…bba0For00.12%—2y ago
3D0x3d63…4afcFor00.10%—2y ago
3D0x3ddc…05b0For00.03%—2y ago
3C0x3c46…353fFor00.02%—2y ago
8A0x8ab6…e0baFor00.00%—2y ago
7A0x7af3…8df3For00.00%—2y ago
050x0579…4048For00.00%—2y ago
270x27d3…f70aFor00.00%—2y ago
3D0x3d5a…b97fFor00.00%—2y ago
B70xb792…89d7For00.00%—2y ago
B10xb1f8…4250For00.00%—2y ago
EC0xecc2…6ac9For00.00%—2y ago
C10xc1c2…24f8For00.00%—2y ago
530x53c4…3584For00.00%—2y ago
C40xc48b…75b6For00.00%—2y ago
500x500f…7d0bFor00.00%—2y ago
9D0x9d57…65a5For00.00%—2y ago
050x0579…ca09For00.00%—2y ago
2D0x2d67…ac5cFor00.00%—2y ago
140x14af…2531For00.00%—2y ago
B30xb3bf…6ce4For00.00%—2y ago
BF0xbfd1…4f66For00.00%—2y ago
BB0xbb02…2f78For00.00%—2y ago
CE0xce57…70f0For00.00%—2y ago
FD0xfdab…2b62For00.00%—2y ago
650x659f…dadcFor00.00%—2y ago
710x71f7…44c0For00.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.