Lido Launches 0x02 CSM for Ethereum Staking with 32 ETH Bond

iconNS3
Share
AI summary iconSummary
Lido launched a new Ethereum staking module, 0x02 CSM, on October 23 under NS3. Operators can run validators with up to 2,048 ETH effective balance. The module requires a 32 ETH bond for the first validator and 30 ETH for each additional key. Lido holds the validator stake separately from the operator’s bond. Initial stake share is capped at 0.01% of Lido Core’s TVL, with a queue for 32 seed deposits. The CSM Committee may suggest capacity increases after activation. This ETH update introduces a new staking option for ETH news followers.

Lido activated a permissionless Ethereum staking module on October 23, enabling independent operators to run validators with effective balances up to 2,048 ETH. The 0x02 Community Staking Module (CSM) requires operators to provide a 32 ETH bond for the first validator key. Operators must bond 30 ETH for each additional key. Lido provides the validator's stake separately from the operator's bond.

Ethereum's 0x02 compounding withdrawal credentials let a validator's effective balance increase beyond the 32 ETH activation minimum to a maximum of 2,048 ETH. Lido estimates that the capital multiplier compared with solo staking is 2.18 times for a first validator. Lido estimates that the multiplier approaches 2.26 times as operators add validators. Lido's comparison includes staking returns earned on the operator's bond and assumes validators reach the full 2,048 ETH effective balance. Eventual stake allocations therefore determine whether operators can achieve the advertised economics. The launch follows the proposal stage on October 4, when mainnet activation remained pending.

Lido initially limits the module's stake share to 0.01% of Lido Core's total value locked, enough for roughly 32 seed deposits. The module also maintains a separate queue with 32 seats for validators waiting for top-ups. Each key receiving a seed deposit must activate before qualifying for additional funding.

The rollout plan places submitted keys in a queue for an initial deposit of 32 ETH. The plan calls for the CSM Committee to propose a capacity increase through Easy Track after the initial batch receives seed deposits and activates. A higher cap would allow additional stake to reach active validators if protocol inflows are sufficient. Seed deposits take precedence over top-ups. A validator that reaches the validator's top-up target frees a queue seat, allowing another key to receive a seed deposit. The committee can propose more capacity increases as newly seeded validators activate.

Ethereum's entry queue creates an additional delay. Validator Queue showed 1,295,748 ETH awaiting entry at the October 25 review. Validator Queue estimated a network-wide wait of 22 days and 23 hours. That estimate does not establish an activation date for an individual CSM validator.

Lido's operator documentation states that top-ups depend on the module's stake-share limit and deposit demand. The documentation warns that a validator may never reach the validator's target. A validator key with active status can still be receiving additional stake.

Existing operators can use 0x01 CSM alongside the new module. The launch does not provide a native migration mechanism based on consolidation from 0x01 to 0x02. The new module provides an additional operating option without removing the existing route.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.