0x02 CSM Landscape

This proposal presents 0x02 CSM to the DAO and broader community as a new module for Community Stakers who want to run validators with 0x02 credentials.

TL;DR

0x02 CSM is proposed as a new permissionless module in the Lido protocol. It is part of a protocol-wide effort to support the widespread adoption of 0x02 credentials.

If approved, it will complement the currently active CSM (referred to as “0x01 CSM” from here on) by giving Node Operators the option to run validators through either 0x01 or 0x02 CSM, with the latter allowing for validators with a maximum effective balance of 2,048 ETH.

0x02 CSM will not have the node operator types that 0x01 CSM has (like ICS and IDVTC), but will offer a stronger capital multiplier for operators and improved protocol economics.

This document explains the new module, its parameters, and how it will coexist with 0x01 CSM.


1. Background

Today’s CSM is built around 0x01 credentials, where each validator can only have a maximum effective balance of 32 ETH. The Pectra hard fork introduced 0x02 credentials last year, raising a validator’s maximum effective balance up to 2,048 ETH. This enables reward compounding, reduces the number of keys needed for the same amount of stake, and lowers consensus-layer overhead—an important requirement for future Ethereum features like faster finality.

Contributing to 0x02 credential adoption is a priority for Lido contributors; stVaults are 0x02-native, and the Curated Module v2 will use them exclusively. Now it’s CSM’s turn to offer a clear path for independent operators to permissionlessly participate in the Lido operator set with 0x02 credentials.

It’s also important to keep CSM accessible, but technical limitations make it difficult to support both 0x01 and 0x02 credentials in a single module, or to achieve the granularity needed to cap 0x02 validators at different balances in a single module and therefore across a range of bonds.

Under these two modules, 0x01 CSM would continue serving smaller operators and the existing types such as ICS or IDVTC, while 0x02 CSM would let operators run higher-balance 0x02 validators.


2. Objectives

This proposal is made with the following objectives:

  • Give Node Operators a permissionless path to run 0x02 validators through the Lido protocol.
  • Improve DAO economics while offering competitive economics for Node Operators.
  • Expand Lido support for 0x02 credentials by adding 0x02 CSM as a complementary module, while preserving access for operators via the different operator profiles of 0x01 CSM.

3. Understanding 0x02 CSM

At a high level, 0x02 CSM is for Node Operators who want to run validators with 0x02 withdrawal credentials in a permissionless way. As with 0x01 CSM, Node Operators are expected to provide a bond for each validator key they upload.

The key difference is that each 0x02 key can represent up to 2,048 ETH. Unlike in 0x01 CSM—where a validator is either pending deposit or fully deposited with 32 ETH—0x02 CSM validators are first seeded with 32 ETH and can later be topped up toward the 2,048 ETH maximum effective balance. As a result, an active 0x02 CSM validator may not always run at full MAX_EB.

The module will be deployed using the updated CSM codebase, the same version that will power the Curated Module v2 and 0x01 CSM. This makes 0x02 CSM part of the broader evolution of Lido staking modules while preserving CSM’s specific operator model and open access.

The rest of this section explains how the module is expected to work in practice, from stake allocation and parameters to module limits and governance responsibilities.

Stake allocation

In 0x01 CSM, each key only needs 32 ETH. But because 0x02 validators are significantly larger, stake allocation in 0x02 CSM is split between an initial deposit queue and a top-up queue.

The initial deposit queue is where uploaded keys wait for their first 32 ETH deposit. This seeds the validator, allowing it to begin the activation process without waiting for the full 2,048 ETH balance.

Once active, the top-up queue is where validators will continue receiving stake toward 2,048 ETH. It follows the order set in the initial deposit queue, but to balance initial-deposit and top-up dynamics, only a limited number of validators can be in the top-up queue at the same time.

The exact number of seats in the top-up queue will be proposed closer to launch. To illustrate the mechanism, the diagram below uses 16 seats as an example:

In this example, the top-up queue has all seats occupied, with Validator A at the front of the queue receiving all incoming stake until it reaches 2,048 ETH. Once full, it leaves the queue and frees a seat.

At that moment, Key P, which was waiting in the initial deposit queue, can receive its 32 ETH deposit and, once active, enter the top-up queue in the newly available seat.

This design lets validators start operating as early as possible with the minimum 32 ETH deposit, while giving them a dedicated path toward the full 2,048 ETH balance, subject to module capacity and protocol inflows.

Bond structure and parameters

Pectra changed the risk profile of validators by reducing the initial slashing penalty. At the same time, not all risks scale proportionally with validator balance. As described in the CSM risk assessment, risks such as slashings and EL rewards rerouting need to be considered separately when designing bond parameters.

This makes it possible to consider a parameter structure with a meaningfully lower bond per 32 ETH of validator balance and a better take rate for the DAO, while maintaining a competitive capital multiplier for Node Operators.

With that in mind, the proposed parameter set is:

Parameter Proposed value
Bond 32 ETH first key, 30 ETH subsequent keys
Rewards Rate 2% NO, 8% DAO
Capital multiplier up to ~2.26x
Key removal fee 0.02 ETH
Performance leeway 3%
General penalty fee 0.1 ETH
Strikes 3 strikes / 6 frames lifetime
Bad performance penalty 0.258 ETH per 32 ETH, up to 16.512 ETH for a full 2,048 ETH validator
Exit delay penalty 0.1 ETH per key after 4 days

For a fully topped-up 2,048 ETH validator, the proposed bond is equivalent to 0.5 ETH of bond per 32 ETH of balance for the first key, and approximately 0.47 ETH of bond per 32 ETH for subsequent keys, a ~3x improvement over 0x01 CSM.

In combination with the 2% rewards rate, Node Operators get an initial capital multiplier of approximately 2.18x, which can increase up to 2.26x as more keys are added.

These figures describe the common full-balance scenario. Actual capital efficiency and rewards depend on each validator’s current effective balance, module capacity, and protocol inflows.

The rest of the proposed parameters are aligned with the Default type in 0x01 CSM, scaled where necessary for the x64 balance of 0x02 validators.

Combined CSM stake share limit

LIP-33 introduced changes that allow module stake share limits to be adjusted more gradually via EasyTrack motions, within predefined bounds. This allows CSM capacity to be adjusted over time without requiring a full governance vote for each change.

This proposal sets a 20% maximum combined capacity for 0x01 CSM and 0x02 CSM. The CSM Committee could then manage the balance between the two modules as the conditions to scale 0x02 CSM (described at the end of this proposal) are met.

The exact stake share limit for 0x02 CSM, along with a more detailed framework for these adjustments, will be shared closer to mainnet deployment.

Governance

0x02 CSM includes some functions that require frequent use or a quick response, such as:

  • Reporting or canceling penalties associated with protocol violations like EL stealing via REPORT_GENERAL_DELAYED_PENALTY_ROLE and MANAGE_GENERAL_PENALTIES_AND_CHARGES_ROLE
  • Settling confirmed General Delayed Penalties through EasyTrack via SETTLE_GENERAL_DELAYED_PENALTY_ROLE
  • Rolling back the top-up queue in case of invalid top-up information being delivered by the Depositor Bot via REWIND_TOP_UP_QUEUE_ROLE
  • Change the bond curve for a particular Node Operator via SET_BOND_CURVE_ROLE
  • Pausing CSM in case of emergency via CircuitBreaker

It is proposed that the CSM Committee take on these roles for 0x02 CSM as it does for 0x01 CSM, since the users, functions, and expected responsibilities remain largely the same.


4. What this means for CSM

Introducing 0x02 CSM would expand CSM from a single permissionless module into a set of modules spanning both 0x01 and 0x02 credentials.

The main change is that CSM would no longer be limited to 32 ETH validators. In the near term, 0x01 CSM would remain the lower-bond path for node operators, while 0x02 CSM would give operators with more available capital a way to run fewer, higher-balance validators with better capital efficiency.

If included in a future Ethereum upgrade, EIP-8148 could enable more flexible 0x02 validator balances, expanding the bond options in CSM and eliminating the need for two modules.

The sections below outline how 0x02 CSM fits into the broader CSM experience and how existing 0x01 CSM operators should think about moving to 0x02 CSM.

The unified CSM experience

From the operator’s point of view, 0x02 CSM will be treated similarly to a Node Operator type such as ICS or IDVTC, even if under the hood it is a separate module.

Users will be able to manage validators in 0x02 CSM together with their existing 0x01 CSM setup through the same interface.

Putting it together, this is what the CSM landscape would look like after adding 0x02:

0x01 Default 0x01 ICS 0x01 IDVTC 0x02 CSM
Entry Permissionless Permissionless / verified Verified DVT cluster Permissionless
Target operator Home stakers / Small-to-medium independent operators Home stakers / verified community operators Verified DVT clusters of Independent Community Stakers More capitalized independent operators
Limitations on who can use this mode None (open even to professionals) Must be a verified Independent Community Staker as per the ICS requirements (cannot be a professional node operator) Must be a cluster of independent participants each with ICS None (open even to professionals)
Validator balance 32 ETH 32 ETH 32 ETH Up to 2,048 ETH
Bond, first key 2.4 ETH 1.5 ETH 1.5 ETH 32 ETH
Bond, subsequent keys 1.3 ETH 1.3 ETH 0.5 ETH 30 ETH
Node Operator reward 3.5% 6% for the first 16 keys, 3.5% for subsequent keys 3.5% for the first 64 keys, 2% for subsequent keys 2%
DAO fee 6.5% 4% 6.5% for the first 64 keys, 8% for subsequent keys 8%
Capital multiplier up to ~1.76x up to ~2.36x Up to 3x up to ~2.26x
Withdrawal credential type 0x01 0x01 0x01 0x02

Consolidations

Unlike in the Curated Module, existing 0x01 CSM operators should not expect support for consolidations to migrate directly into 0x02 CSM.

Using consolidations for 0x01-to-0x02 CSM migrations would require operators to maintain bond in both modules during the transition. It would also introduce significant coordination overhead, making this approach difficult to support in a permissionless module like CSM.

This means an existing 0x01 CSM operator would need to either operate in both modules or exit their 0x01 CSM validators and fund keys in 0x02 CSM.


5. Proposed timeline

0x02 CSM should be understood as a first step toward supporting 0x02 credentials in CSM.

It is also important to recognize that 0x02 CSM would be introduced during a broader transition toward 0x02 credentials, alongside improvements across Lido staking modules.

For that reason, the stake share limit of 0x02 CSM should be raised only once the following conditions are met:

  • Curated Module v2 operators have enough seeded and active keys to support the consolidation of stake from v1 to v2, plus sufficient capacity for a reasonable amount of net protocol inflows.
  • The Ethereum validator queue and Lido protocol inflows support a reasonable experience for new operators and potential 0x01-to-0x02 CSM migrators.
  • The Glamsterdam hardfork is either activated on Ethereum or delayed long enough to avoid requiring an immediate module upgrade shortly after release.

6. Summary of proposal

To summarize, this proposal is to:

  • Deploy an instance of CSM v3 configured to support 0x02 credentials.
  • Set a 20% maximum stake share for 0x01 and 0x02 CSM combined.
  • Launch the module with the proposed parameter set, including:
    • A 32 ETH bond for the first key, and a 30 ETH bond for subsequent keys.
    • A 2% / 8% fee split between the operator and the DAO.
    • The exact number of seats in the top-up queue to be proposed closer to mainnet deployment.
  • Assign the relevant operational and emergency roles to the CSM Committee.
16 Likes

Great summary of the 0x02 landscape, @enti. Native compounding is a huge win for CSM stakers and makes perfect sense. No objections from my side; I’ll be following the thread closely to see how the technical details develop. :rocket:

5 Likes

Strong +1 on this, @enti — thanks for laying out the landscape so clearly.

0x02 credentials are the direction Ethereum has now ratified, so it’s great to see Lido moving to support them this soon. Aligning the module roadmap with where the protocol itself is heading is exactly the right instinct.

CSM (0x01) has been an enormous success — it proved that permissionless validation in Lido works and that there’s real, sustained demand from independent stakers. That community deserves a contemporary path that carries the same permissionless spirit forward, now with exposure to 0x02 creds and the increased MAX_EB. Native compounding alone is a meaningful capital-efficiency and quality-of-life upgrade for community operators.

The capital multiplier is what makes this genuinely stand out, though. It turns 0x02 CSM into a fairly unique product offering and keeps incentives well aligned between stakers and the protocol — which is hard to get right and worth calling out explicitly :droplet:

4 Likes

Thanks for the proposal @enti!

I want to voice my strong support here. 0x02 credentials are the path moving forward for Ethereum and Lido. It is great to see that now the permissionless part of the Lido protocol will also join the 0x02 track alongside the upcoming CMv2.

It is worth noting that the current scope of 0x02 CSM might seem limited to hole stakers with 32+ ETH, which is essentially true. However, Lido contributors do not plan to stop here. Should EIP-8148 (or any alternative with a similar outcome) be implemented on the core Ethereum level, 0x02 CSM will evolve into a module that will be able to offer access to 0x02 credentials for home stakers with any capital. The flexible upper stake limit described in EIP-8148 will allow 0x02 CSM to accommodate 0x02 validators of a different size. Hence, the minimal bond requirement and the bond step will be drastically reduced, opening the possibility of running 0x02 validators with an almost arbitrary bond amount.

6 Likes

Snapshot vote started

Please get your wallets ready to cast a vote :white_check_mark:, the 0x02 CSM: New Permissionless Module Launch Snapshot has started! The Snapshots ends on Mon, 20 Jul 2026 16:00:00 GMT.

4 Likes

Snapshot vote ended

The 0x02 CSM: New Permissionless Module Launch Snapshot has reached a quorum and completed successfully!
The results are:
For: 58.0M LDO
Against: 0 LDO

:white_check_mark: Winning option: For

2 Likes

0x02 CSM testnet is live at csm.testnet.fi

4 Likes

A small note that Exit Delay Penalty is also scaled with the validator balance. 0.1 ETH is the value for the 32 ETH validator. For 2048 ETH validator it will be 6.4 ETH

Deployment parameters for the new module and the preliminary values for the upcoming vote connecting it to the protocol are published in the CSM proposal thread, see Community Staking Module - #240 by madlabman

1 Like

0x02 CSM Rollout plan update

Given that the Ethereum entry queue is still very long (>23 days at the moment of writing), ongoing stake migration from CMv1 to CMv2, and a continued focus on protocol efficiency, resilience, and security, Lido contributors propose the updated rollout plan for 0x02 CSM.

Phase 1. Seed deposits for the very first keys in the module

It is proposed to launch 0x02 CSM with the stakeShareLimit = 1 BP (0.01% of protocol TVL) and a top-up queue limit of 32 validators. This will ensure that all of the initial stakeShareLimit is utilized by seed deposits (initial 32 ETH deposits) only. Top-up deposits are only possible for active validators. With the current Ethereum Entry Queue, it will take 23+ days for these keys to get activated. Hence, stakeShareLimit = 1 BP (0.01% of protocol TVL) is reasonable to allow for the seed deposits on these ~32 keys during Phase 1.

Phase 2. Gradual increase of the stakeShareLimit

Once the first batch of 32 keys is seed deposited and activated on the Ethereum Consensus Layer, CSMC (Community Staking Module Committee) will propose an increase of the stakeShareLimit (via ET motion) to the value that can be immediately (provided sufficient stake inflow to the protocol) filled by allocating top-up deposits to the already active keys. As soon as the first key is fully topped up, it will be removed from the top-up queue and free up the space for the additional seed deposit. Since seed deposits have priority over top-up deposits, this key will be the next in line to get a seed deposit. The process will continue in the same way until 0x02 CSM reaches its stakeShareLimit.

Once stakeShareLimit is reached, and a sufficient number of new validators are active to receive top-ups, CSMC will repeat the process of proposing a stakeShareLimit increase via ET motions.

Operator UX in the proposed plan

For the Node Operators in 0x02 CSM, the proposed plan means that if they get seed deposits during one iteration of the stakeShareLimit increase, they will receive top-up deposits that will bring their validator to 2046 ETH (2 ETH leeway is by protocol design and aimed to avoid validator overfill), not earlier than in the next iteration of the stakeShareLimit increase.

The picture below illustrates the approximate validator deposit cycle in 0x02 CSM. If you upload your key when there are available spots in the top-up queue, you will start with step two without a stakeShareLimit increase required to get a seed deposit.

Given the extended entry queue, the proposed solution is aimed at balancing:

  • Ensuring the fastest start for the brand-new validators in 0x02 CSM
  • Not interrupting the current CMv1 to CMv2 stake migration

Changes to the upcoming on-chain vote

To implement the plan described, the following changes and additions should be made to the planned 0x02 CSM activation on-chain vote:

  • Change initial stakeShareLimit from originally proposed 200 BP (2%) to 1 BP (0.01%) to ensure a smooth start, with further increases to stakeShareLimit via ET motions
  • Add a call to set topUpQueueLimit to 32 items

Community feedback and questions

The proposed updated rollout plan is now open for community discussion. Lido Contributors will be happy to provide more detailed answers to any questions you might have in this thread or in the official Lido Discord.

11 Likes

GM!

The upcoming on-chain vote is expected to include the following items to connect CSM 0x02 to the protocol, reflecting the updated rollout plan.

Expected vote items

1. Submit a Dual Governance proposal to connect and activate CSM 0x02

Register the module in the Staking Router with the following parameters:

Parameter Value
Module name Community Staking 0x02
Module address 0x792Cd25e4aE3578375031FB55e048E163A804F7B
Initial stake share limit 1 BP (0.01%)
Priority exit share threshold 240 BP (2.4%)
Staking module fee 200 BP (2%)
Treasury fee 800 BP (8%)
Maximum deposits per block 30
Minimum block distance between deposits 25 blocks
Withdrawal credentials type 0x02

The proposal also includes:

  • Grant REQUEST_BURN_MY_STETH_ROLE on Burner to CSM 0x02 Accounting and ADD_FULL_WITHDRAWAL_REQUEST_ROLE on Triggerable Withdrawals Gateway to CSM 0x02 Ejector.
  • Resume CSM 0x02, temporarily granting and then revoking RESUME_ROLE for Aragon Agent.
  • Set the HashConsensus initial epoch to 494,340, so the first oracle report can be submitted on Dec 7, 2026, covering the 28 days starting from Nov 9, 2026.
  • Register CSM 0x02 Module, Accounting, FeeOracle, Verifier, and Ejector on CircuitBreaker with the CSM Committee as pauser.
  • Set the CSM 0x02 top-up queue limit to 32 validators, temporarily granting and then revoking MANAGE_TOP_UP_QUEUE_ROLE for Aragon Agent.

Execution is restricted to 14:00-23:00 UTC. Before enactment, the current AccountingOracle report must be fully processed, including all extra-data chunks, and the next reference slot must not have been reached.

2. Add ReportWithdrawalsForSlashedValidators to Easy Track

Register the CSM 0x02 factory at 0x8D74020d8EACCdFf0366dAAFfb96e6c98CDFc112, with permission to call reportSlashedWithdrawnValidators on CSM 0x02.

3. Add SettleGeneralDelayedPenalty to Easy Track

Register the CSM 0x02 factory at 0x0B676AdEABcf4A696187cfAb90290Aa3ac51aFA2, with permission to call settleGeneralDelayedPenalty on CSM 0x02.

4. Add UpdateStakingModuleShareLimits to Easy Track

Register the CSM 0x02 factory at 0x5b0De22E65C068430f6e769754D51133775408cc, with permissions to call validateParams on the factory and updateModuleShares on the Staking Router.

The CSM Committee can adjust the module’s shares through this factory, with the following limits per motion:

Parameter Value
Maximum stake share limit increase 50 BP (0.5 %)
Maximum stake share limit decrease 50 BP (0.5 %)
Maximum priority exit share threshold increase 60 BP (0.6 %)
Maximum priority exit share threshold decrease 60 BP (0.6 %)

Mainnet deployment

CSM 0x02 has been deployed on Ethereum mainnet. The deployment artifacts include the following contract addresses:

Easy Track factories

The three CSM 0x02 Easy Track factories are also deployed on mainnet:

Factory Address
ReportWithdrawalsForSlashedValidators 0x8D74020d8EACCdFf0366dAAFfb96e6c98CDFc112
SettleGeneralDelayedPenalty 0x0B676AdEABcf4A696187cfAb90290Aa3ac51aFA2
UpdateStakingModuleShareLimits 0x5b0De22E65C068430f6e769754D51133775408cc

Audits and deployment verification

The CSM v3 code and supporting Easy Track factories were audited as previously shared:

MixBytes verified the mainnet deployments of CSM 0x02 and its three Easy Track factories. The full reports are available in the audits repository:

6 Likes

The on-chain vote #206 is now live and includes the proposal to enable 0x02 CSM in accordance with rollout plan, with an initial stake share limit of 0.01% and top-up queue limit of 32.

The vote will be open for your “For” or “Against” input until the end of the main phase: Oct 17, 13:13 UTC.

For instructions on how to verify the vote items, please follow this guide.

2 Likes

The on-chain vote #206 has reached the required support quorum and has been enacted. The 0x02 CSM activation will take effect once Dual Governance Proposal #15 is executed, currently scheduled for Friday, October 23, at 13:14 UTC.

2 Likes

0x02 migration seems to be moving fast, will the CSM still be worth it for LIDO when there’s no point on splitting eth on many validators, or am i missing something, besides widening adoption? for validators with not enough ETH, CSM is still valuable, but i’m trying to see LIDO’s side.

1 Like

The Dual Governance Proposal #15 has been enacted and the 0x02 CSM has been activated.

0x02 CSM is live on https://csm.lido.fi.

5 Likes

What was the fundamental reasoning for deploying 0x02? To get whale validators? They already had a forum to begin with. The small guys seem to get ignored - you can tell by looking at the long queue on 0x01.

1 Like

The queue in 0x01 CSM is not long at all compared to the historical values you can see here - https://dune.com/lido/lido-csm

The main reason for the queue to pile a bit is that protocol withdrawals are bigger than inflows. However, since the last weekend deposit reserve is enabled again - Motion #1209 | Lido and we expect at least 16 validators to get deposits every day strating from today in 0x01 CSM.

So the focus has NOT shifted towards so called whales. 0x01 CSM is still live and ready to accept deposits.

Happy validation!

3 Likes

All pending validators from 0x01 CSM deposit queue were deposited a few hours ago

1 Like

Thank you. I noticed that my keys that were in the queue were deposited earlier today.

1 Like