Lido contributors have introduced a proposal for a new permissionless Community Staking Module designed specifically for Ethereum validators using 0x02 withdrawal credentials. Announced by the Lido community on July 1, 2026, the proposed module would operate alongside the existing Community Staking Module, which currently supports validators with 0x01 credentials.
Known as 0x02 CSM, the new module would give node operators another way to participate in the Lido staking ecosystem while supporting larger validator balances, reward compounding, and more efficient validator infrastructure.
The proposal remains subject to Lido DAO governance and should not be considered a finalized protocol upgrade.
What Is Lido’s Proposed 0x02 CSM?
The proposed 0x02 CSM would be a permissionless staking module for node operators who want to run Ethereum validators using 0x02 withdrawal credentials.
Lido’s existing Community Staking Module would remain active and would be referred to as 0x01 CSM. Rather than replacing the current module, 0x02 CSM would provide a complementary staking option.
Under the proposed structure, operators could choose between:
- 0x01 CSM: Supports traditional Ethereum validators with a maximum effective balance of 32 ETH.
- 0x02 CSM: Would support validators with effective balances ranging from 32 ETH to as much as 2,048 ETH.
Ethereum’s Pectra upgrade introduced support for 0x02 withdrawal credentials through EIP-7251. This change increased the maximum effective validator balance from 32 ETH to 2,048 ETH while enabling validators to receive balance top-ups and compound rewards more efficiently.
How 0x02 Validators Differ From Traditional Validators
Before Ethereum implemented EIP-7251, validators generally operated with a fixed maximum effective balance of 32 ETH. Operators managing large amounts of stake therefore needed to maintain many separate validator keys.
With 0x02 credentials, a single validator can hold an effective balance of up to 2,048 ETH, equivalent to 64 traditional validators funded with 32 ETH each.
This structure can reduce the number of validator keys needed to manage the same amount of stake. It may also lower consensus-layer overhead and simplify validator operations for participants managing larger staking balances.
Unlike a traditional validator that receives a complete 32 ETH deposit, an 0x02 CSM validator would initially be seeded with 32 ETH. After activation, it could receive additional stake through a separate top-up process until it approaches the 2,048 ETH maximum effective balance.
How Stake Allocation Could Work
The proposal introduces two separate queues for allocating ETH to 0x02 validators.
Initial Deposit Queue
Validator keys would first enter an initial deposit queue to receive their first 32 ETH allocation. This deposit would allow them to enter Ethereum’s validator activation process.
Validator Top-Up Queue
After activation, validators could enter a top-up queue and receive additional stake over time. This process would allow active validators to increase their effective balances without requiring operators to launch dozens of separate validator keys.
Only a limited number of validators would be allowed in the top-up queue at one time. The final number of available top-up positions would likely be proposed closer to the module’s potential mainnet deployment.
This design is intended to balance two priorities: activating new validator keys and efficiently increasing the balances of validators that are already online.
Proposed Bond and Fee Structure
As with the existing Community Staking Module, node operators participating in 0x02 CSM would be required to provide a bond for each validator key.
The initial proposal outlines the following parameters:
| Proposed Parameter | 0x02 CSM Structure |
|---|---|
| Bond for the first validator key | 32 ETH |
| Bond for each subsequent key | 30 ETH |
| Node operator reward share | 2% |
| Lido DAO reward share | 8% |
| Maximum effective validator balance | 2,048 ETH |
| Access model | Permissionless |
The relatively large bond reflects the amount of Lido-managed stake that could eventually be assigned to each 0x02 validator. According to the proposal, the module could provide operators with stronger capital efficiency while improving the economics generated for the Lido DAO.
These figures remain proposed parameters and could change during technical reviews or governance discussions.
Why Lido Wants Two Separate CSM Modules
Supporting 0x01 and 0x02 validators inside a single module would create technical and accounting complications.
Traditional 0x01 validators are based on fixed 32 ETH units. In contrast, 0x02 validators may hold any effective balance between 32 ETH and 2,048 ETH. Lido’s current validator-count-based accounting system was not originally designed to manage these variable balances.
Lido’s proposed Staking Router v3 upgrade would introduce balance-based accounting, top-up functionality, and support for reallocating stake between modules. Each staking module would still support only one validator credential type, making separate 0x01 and 0x02 modules the more practical architecture.
Maintaining two modules would also preserve different participation paths.
The existing 0x01 CSM would continue serving smaller operators and specialized operator categories, including Identified Community Stakers and Identified Distributed Validator Technology Clusters. The proposed 0x02 CSM would focus on operators prepared to manage larger validator balances under a different bonding and fee model.
What the Proposal Means for Community Staking
The new module could expand the range of choices available to independent Ethereum node operators.
Operators who prefer smaller, fixed-balance validators could continue using 0x01 CSM. Those with additional capital and infrastructure capacity could use 0x02 CSM to manage significantly more delegated stake through fewer validator keys.
Potential benefits include:
- Fewer validator keys required for large staking operations
- Native reward compounding within larger validators
- Lower operational and consensus-layer overhead
- Greater flexibility in allocating stake
- Permissionless access for node operators
- Improved capital efficiency
However, the proposed bond requirements of 30 ETH to 32 ETH may place 0x02 CSM beyond the reach of some smaller home stakers. For those participants, the existing 0x01 module would remain an important entry point into Lido’s permissionless operator ecosystem.
Proposed Stake Limits and Rollout Conditions
The proposal recommends establishing a combined maximum stake share of 20% for the 0x01 and 0x02 Community Staking Modules.
However, the 0x02 module’s stake allocation would not necessarily increase immediately. Contributors indicated that its limit should be raised only after several operational conditions are met.
These conditions may include:
- Sufficient validator capacity in Lido’s Curated Module v2
- Favorable Ethereum validator queue conditions
- Adequate Lido protocol staking inflows
- Greater clarity surrounding Ethereum’s planned Glamsterdam upgrade
- Successful deployment of the required Lido infrastructure updates
The proposed rollout would also depend on deploying an updated version of the Community Staking Module codebase capable of supporting 0x02 credentials and the accounting changes introduced through Staking Router v3.
What Happens Next?
The 0x02 CSM proposal must move through Lido’s governance and development process before the module can launch.
Community members are expected to review its bond requirements, operator incentives, stake limits, queue mechanics, and potential effects on Lido’s validator distribution. Technical development would also need to align with Staking Router v3, Community Staking Module v3, and other planned Lido Core upgrades.
If approved and successfully deployed, 0x02 CSM could become an important part of Lido’s transition toward larger Ethereum validators and balance-based staking infrastructure.
The proposal would not eliminate traditional 32 ETH validators. Instead, it would create an additional permissionless route for operators that want to take advantage of Ethereum’s newer validator capabilities.
Outlook for Lido and Ethereum Staking
Lido’s proposal demonstrates how liquid staking protocols are adapting to Ethereum’s evolving validator architecture.
Support for 0x02 credentials could allow Lido to manage stake more efficiently while reducing the number of validator keys needed across its operator ecosystem. At the same time, retaining 0x01 CSM would help preserve access for smaller operators who may not have enough capital to meet the new module’s proposed bond requirements.
The long-term impact will depend on governance approval, technical implementation, operator demand, and the pace at which the Ethereum staking ecosystem adopts 0x02 credentials.
For now, the proposal represents another step toward a staking system built around flexible validator balances, permissionless participation, and more efficient use of Ethereum’s consensus-layer resources.
This article is for informational purposes only and does not constitute financial or investment advice.
