Staking Modules Updates
Lido Core Upgrade
Lido Core continues to evolve alongside Ethereum, powering the next generation of staking.
This upgrade marks the protocol’s most significant evolution since Lido V2, launched following the Shapella hardfork. It introduces major changes across Lido’s staking modules architecture, including Staking Router v3, improvements to the CSM, and the new Curated Module v2 (CMv2).
Together, these changes strengthen protocol health and sustainability and improve its alignment with Ethereum's roadmap, while advancing decentralization that benefits both Lido and the broader ecosystem.
Discover what’s changing across Lido Core staking modules and how the upgrade lays the foundation for the next generation of Ethereum validator architecture.
Curated and Curated v2 Modules
Curated Module v2 Live, Migration Ahead
The new Curated Module v2 is now live on Ethereum mainnet. As of July 31, 12 Curated Node Operators (NOs) onboarded to the module, with other operators expected to finish the process till the end of August.
The migration of stake from the legacy Curated Module (CM) is also approaching, as the first 0x02 Lido validator keys continue to get deposits from the protocol. Given Ethereum’s current validator activation queue of approximately 40 days, the transition will take some time with the first deposited CMv2 validators scheduled to activate around September 13.
Throughout the migration, the CM will remain available as a fallback and will be gradually wound down as stake moves to the CMv2. This phased approach helps preserve operational continuity while transitioning Lido’s largest staking module toward a more flexible architecture designed to better recognize different operator contributions, strengthen accountability, and support a more resilient and decentralized validator set.
Round One Node Operator Type Assessment Results
The Curated Module Committee (CMC) completed the first assessment of Curated NOs applications for the Public Good, Extra Effort, and Decentralization Operator types, which recognize different contributions to Lido and the broader Ethereum ecosystem: from supporting client and geographic diversity to developing public goods and contributing additional resources to the protocol operations and governance.
The results can be found below and on the Research Forum.
Community Staking Module
0x02 CSM Coming
Lido DAO approved the launch of a dedicated 0x02 CSM, designed specifically to enable permissionless path for Node Operators to use 0x02 withdrawal credentials within Lido Core.
Instead of operating dozens of individual 32 ETH validators, operators using 0x02 CSM will be able to permissionlessly run validators with effective balances of up to 2,048 ETH, unlocking a more capital-efficient path for large-balance validators.
Alongside this, the DAO approved raising the total permissionless staking capacity to 20% providing
significantly more room for permissionless operators to participate in securing Ethereum network through the protocol.
While July’s Lido Core upgrade did not activate 0x02 validator support in the CSM, CSMv3 codebase now natively supports 0x02 withdrawal credentials, laying the technical foundation for the dedicated 0x02 CSM instance.
Once launched, 0x02 CSM will operate alongside the existing CSM as a separate operator category, offering operators full flexibility to choose their preferable validation path with Lido among four participation options.
From independent home and community stakers to DVT clusters and more capitalized actors, the expanded CSM architecture is designed to accommodate a broader range of participants while preserving permissionless access.
By making different operating models viable within Lido Core,
it help diversify operator participation and contribute to a more decentralized Ethereum validator set.
To dive deeper into the approved proposal, its parameters, and design rationale, read the full 0x02 CSM Landscape. The testnet is expected in late August or early September.
Simple DVT Module
Following Lido DAO approval of the proposal to wind down the Simple DVT Module (SDVTM) regular clusters, contributors began coordinating validator exits of Obol clusters on July 1. By July 6, all these clusters had exited, and on July 14, the wind-down of Simple DVT regular clusters was completed.
Super Clusters were not affected by the decision and continue operating according to the originally approved plan.
Lido x Obol
5 Super Clusters are active on mainnet, running 500 validators each
Lido x SSV
5 Super Clusters are active on mainnet, running 500 validators each
ICS Operator Type for Independent Simple DVT Operators
The approved proposal also established a pathway for home and community stakers from SDVTM to continue validating through Lido Core. Operators who did not already hold Identified Community Staker (ICS) status became eligible for this CSM operator type.
Following a review conducted by the Community Staking Module Committee, eligible Simple DVT operators were added to the ICS list and can now claim their status:
- If they already have a CSM operator, they may claim the ICS operator type directly in the UI,
- Operators without an existing CSM operator will have the ICS type assigned automatically upon creating their operator profile.
This gives independent operators, who proved themselves by running SDVTM validators, two paths to continue participating in Lido’s permissionless validator set: operate individually under the ICS operator type with its enhanced staking parameters, or join other eligible operators as part of an Identified DVT Cluster (IDVTC).
This approach provides a pathway to retain experienced home and community stakers within Lido Core while moving participation from the coordination-heavy Simple DVT model toward permissionless, more scalable options through the CSM.
Node Operator Community
ETH Belgrade
If you’re in Serbia, join Lido contributors in Belgrade on August 26–27 for the fourth edition of ETH Belgrade, taking place during Belgrade Blockchain Week. This two-day event brings the Ethereum community together in the heart of the Balkans for talks, workshops, a hackathon, and networking with builders and contributors from across the ecosystem. If you’re around, come say hi!
![ETH Belgrade [4]](https://images.spr.so/cdn-cgi/imagedelivery/j42No7y-dcokJuNgXeA0ig/ae9b0763-941e-4cfa-9681-263d62416270/eth-belgrade-og-2026/w=1920,quality=90,fit=scale-down)
Validator Ejector & Keys API Updates
With CMv2 now live, Curated operators need to update to the latest versions of the Validator Ejector and Keys API (KAPI) and update their configurations accordingly.
In particular, Curated NOs should use the new EJECTOR_SCOPE setting to ensure that all of their operator instances—across both the legacy Curated Module and their sub-Node Operators in CMv2—are set up correctly.
Validator Ejector
The latest validator-ejector version, initially released for Hoodi testing in May, is now also available for mainnet.
The release adds support for CMv2 and introduces multi-module and multi-operator configuration through the new EJECTOR_SCOPE setting. The existing STAKING_MODULE_ID, OPERATOR_ID, and OPERATOR_IDENTIFIERS settings are now deprecated.
With the new configuration, a single ejector instance can handle multiple staking modules instead of maintaining separate configurations. Other improvements include:
- Support for multiple Execution and Consensus Layer endpoints via comma-separated
EXECUTION_NODE/CONSENSUS_NODE - Improved cold start performance by batching CL validator info requests
- Additional logging, diagnostics, and configuration improvements
Curated Node Operators should review their configurations and make sure all CM and CMv2 operator instances are included in EJECTOR_SCOPE.Keys API (KAPI)
A new keys-api 4.0.4 is also available. This is a minor bugfix release addressing an issue with unexpected characters in Node Operator names. Release notes can be found here.
The KAPI update is not urgent, but Lido contributors ask all Node Operators running Keys API to upgrade by August 15.
Tapered Issuance Burn Proposal
A new issuance change Ethereum Improvement Proposal (EIP) has been introduced with tapered issuance burn, proposing changes to ETH issuance curve that, if adopted, will affect the entire Ethereum ecosystem.
The proposal has been proposed for inclusion in the Hegota upgrade in 2027, so it is now open to community input.
Given its potential implications for operators, and stakers, Lido Node Operators and the broader Lido community are encouraged to review the proposal and join the discussion.
Share questions and feedback in the Ethereum Magicians thread, where they can be considered and visible to the wider Ethereum community.
Bonus Content
Dmitry, Head of Lido Staking Engineering at the Lido Labs Foundation, joined the EthStaker Community Call #69 to discuss EIP-8148, a proposal for Custom Sweep Thresholds for validators.
The proposal explores giving 0x02 validators greater flexibility over when accumulated rewards are swept to their withdrawal addresses, particularly relevant for independent and community stakers who may otherwise need to wait a long time for rewards to reach the default 2,048 ETH threshold.
Tune in to hear about the motivation behind the proposal, how the mechanism could work, and what it could mean for Ethereum validators.