Lido launched its 0x02 Community Staking Module on October 23, 2026, opening a permissionless route for operators to run higher-balance Ethereum validators. The announcement adds a second module alongside the existing 0x01 option.
TL;DR: Operators supply a bond while Lido allocates stake. Capacity expands gradually, and a validator’s initial activation comes before its full allocation.
Why a validator can now hold more stake
Ethereum’s EIP-7251 specification raised the maximum effective balance for eligible validators to 2,048 ETH while retaining a 32 ETH minimum for activation. The change lets a larger amount of stake sit behind one validator identity.
Previously, scaling an operator’s stake generally meant multiplying validator identities with the same effective-balance ceiling. The specification explains that consolidation can reduce redundant validator activity and the associated networking and signature-processing burden.
It also supports compounding within a higher-balance validator. Effective balance is the protocol’s accounting measure for participation and rewards; a larger maximum does not mean every new validator begins at that maximum.
Lido’s new module requires a 32 ETH bond for an operator’s first key and 30 ETH for each additional key. Existing 0x01 participants can remain where they are. There is no automatic migration between the two modules.
That distinction matters when comparing operating models. The validator’s allocated stake, the operator’s own bonded capital and the rewards earned over time are different quantities. A larger amount of stake managed per unit of operator capital should not be read as a guaranteed investment return.
How the staged allocation works
The rollout plan published on October 8 sets out the cautious opening structure: a stake limit equal to 0.01% of Lido Core’s total value locked and 32 places in the top-up queue. The October 23 launch announcement confirms those opening limits.
A key first receives a 32 ETH seed deposit and enters Ethereum’s activation process. Further deposits follow after activation. The CSM Committee can propose capacity increases through Easy Track motions, allowing the module to grow in stages rather than assigning its eventual capacity immediately.
This structure creates two separate dependencies for an operator’s timetable. The network must activate the validator, and the module must subsequently have room and available stake for additional allocation. Joining a permissionless module therefore does not determine when a key will reach its desired balance.
For operators assessing the new path, the meaningful comparison is the full lifecycle: initial capital, time awaiting allocation, ongoing duties and the process for leaving. Looking only at the maximum validator balance misses the period in which capital is committed but the validator is still being filled.
The launch creates another operating choice. Its practical scale will depend on how the staged capacity process develops and how much stake flows into the module.
Written by the News Desk and edited by Samuel Rae.
Leave a Reply