Lido has introduced 0x02 CSM, a new permissionless version of its Cross-Shifted Staking Module designed for validators that use 0x02 withdrawal credentials. The module allows operators to run validators through Lido with a maximum effective balance of 2,048 ETH, creating another route for independent operators to participate in Ethereum validation at larger scale.
As with Lido’s existing 0x01 CSM setup, operators are not required to supply the full validator stake themselves. Instead, they post a bond and the protocol allocates stake to the validator, lowering the upfront capital needed to run higher-balance validators through the system.
Bond model and capital efficiency
Under 0x02 CSM, the bond is set at 32 ETH for the first validator key and 30 ETH for each additional key. Lido says that, when rewards from bond rebasing are included, the estimated capital multiplier at full effective balances begins at 2.18x for the first validator and rises toward 2.26x as more validators are added, compared with solo staking.
The new module is aimed at operators who want exposure to higher-balance validators without fully self-funding them. Lido presents it as a lower-barrier way to access validators with larger effective balances while still using a permissionless onboarding path.
Two-stage allocation process
Unlike a 0x01 CSM validator key, which receives its full 32 ETH in one deposit, a 0x02 CSM validator key is funded in stages through two queues. Lido says this structure is meant to balance the onboarding of new validators with the topping up of validators that are already active.
In the initial deposit queue, submitted keys wait for a 32 ETH seed deposit. That deposit lets the key enter Ethereum’s deposit queue and wait for activation before receiving its full target allocation. After activation, the validator can enter the top-up queue, where additional stake is assigned according to the order established in the initial queue.
The top-up queue has a fixed number of seats. Once a validator reaches its target top-up level, it leaves the queue and its seat becomes available for another key. Lido said seed deposits take priority, meaning the next eligible validator receives its initial 32 ETH before active validators receive more top-ups.
Limited initial rollout
The rollout begins with a stake share limit equal to 0.01% of Lido Core TVL and a 32-seat top-up queue. According to Lido, that initial configuration is enough to seed about 32 validator keys, with further allocations coming later.
After those validators receive seed deposits and become active on Ethereum, the CSM Committee may propose increases to the stake share limit so more stake can be allocated to validators waiting in the top-up queue. Lido noted that any additional allocation remains subject to protocol inflows.
As validators hit their top-up targets and leave the queue, seats are freed for new seed deposits. That cycle continues until the module reaches its share limit.
How 0x02 fits with existing CSM options
Lido said 0x01 and 0x02 CSM will operate in parallel on the same codebase, with a combined maximum capacity of 20% of Lido Core TVL. In the CSM widget, 0x02 CSM appears as another operator option, and users can manage keys and bonds for both modules through the same interface.
There is no native migration path from 0x01 to 0x02 CSM based on consolidation. Existing 0x01 operators that want to use the new module must either run both modules at the same time or exit 0x01 validators and use the released bond for new 0x02 keys. Lido added that 0x01 CSM will remain available and there are no near-term plans to deprecate it.
The broader CSM lineup now includes four routes: 0x01 Default, 0x01 ICS, 0x01 IDVTC, and 0x02 CSM. Lido said ICS and IDVTC operators keep their preferential parameters within 0x01 CSM, but those benefits do not carry over to 0x02.
What comes next
Lido framed 0x02 CSM as a complement to, rather than a replacement for, its existing 0x01 module. For now, the immediate next step is the phased expansion of capacity, with any stake share limit increase requiring a proposal from the CSM Committee and depending on available protocol inflows.
The project also pointed to EIP-8148 as a possible longer-term development. The draft proposal would let 0x02 validators use custom balance thresholds and automatically sweep funds above those thresholds to the withdrawal address. Lido said that, if the proposal is included in a future Ethereum upgrade, it could eventually support more flexible validator targets such as 512 or 1,024 ETH. The EIP remains a draft, and its inclusion is not guaranteed.
Source: blog.lido.fi