The liquid staking protocol Lido has launched the long-awaited Curated Module v2 update, which I assess as the most significant step in the platform's development since the release of the second version. The essence of the upgrade is the transfer of over 8 million ETH (approximately $16 billion) to new validators of the 0x02 format.

The key change is the expansion of the ETH limit per node from 32 to 2048 coins. This fundamentally changes the economics for Lido node operators, allowing them to manage a significantly larger volume of staked tokens with fewer network participants. After the migration is complete, the share of ETH staked under the new standard will grow from ~32% to ~52%. An even more impressive effect is the reduction of the total number of validators in Ethereum by roughly a third, which will significantly reduce the load on the blockchain.

New Security and Incentive Model

Isidoros Passadis, head of staking at Lido Labs Foundation, rightly called this update the most significant change in Lido Core since V2. The Curated Module, operating since 2020 and providing about 90% of all coins staked on the platform, has so far been based solely on a reputation model: the DAO selected professional operators, relying on their integrity.

CMv2 adds financial collateral to this. Operators are now required to deposit their own ETH as a bond, which can be slashed in cases of slashing, prolonged downtime, or other violations. The collateral amount is smaller than in Lido's open modules, but it puts the operator's capital at risk, providing stakers with measurable protection. The reputation model is retained as a supplement.

The second important innovation is the categorization of operators:

  • Decentralization Operators — run nodes in underrepresented regions using rare combinations of clients and infrastructure;
  • Extra Effort Operators — invest in the protocol beyond validator maintenance: through capital, service roles (Lido oracle, Deposit Security Committee), and participation in votes;
  • Public Good Operators — develop and maintain Ethereum consensus and execution layer clients.

The last category formalizes what the DAO has been doing previously: seven client development teams are already working in the Curated Module and, by July 1, 2026, have received 8,710 stETH (~$21 million) in rewards.

The third block of changes is management optimization. Routine administrative actions (e.g., changing an operator's address) no longer require on-chain voting, speeding up responses to urgent issues. The DAO retains control over the operator pool composition, key parameters, and veto power.

Timelines and Other Modules

The migration will take a long time — the queue for activating validators on Ethereum exceeds 40 days. According to developers' estimates, the full transition will take about six months, and the missed rewards will amount to approximately 738.5 ETH. The previous module will remain as a fallback option and will be gradually phased out.

Simultaneously, the third version of the Community Staking Module (CSM) has been released — an open module for solo stakers, which accounts for over 770,000 ETH and about 335 active operators. The key change is a new participant type, Identified DVT Cluster, for launching distributed validators via Obol or SSV with a bond of 1.5 to 0.5 ETH per key and capital efficiency up to 3.1 times higher than solo staking.

The Simple DVT module is being wound down: 72 regular clusters have been closed, and their operators can move to CSM. Super Clusters, where advanced operators and Curated Module participants operate, remain unaffected.

My analysis: This update is not just a technical upgrade but a fundamental shift in Lido's security and governance model. The introduction of financial collateral for operators is a direct response to growing centralization risks and market demands for more reliable mechanisms to protect stakers' funds. The categorization of operators fosters healthy competition and incentivizes contributions to the ecosystem, rather than just passive validator maintenance. In the long term, this should strengthen trust in the protocol and make it more resilient to potential failures.