Lido (@LidoFinance): Curated Module v2: Node Operator Types

Curated Module v2: Node Operator Types During the May voting cycle, Lido DAO approved the Node Operator Type Assessment Framework for Curated Module v2 (CMv2), a major evolution in how the protocol recognizes and treats different Node Operators (NO). By introducing differentiated NO types, the DAO has more flexibility to balance performance, decentralization and risk dynamically adjusting staking parameters, as well as strengthen long-term protocol sustainability. Rather than applying a one-size-fits-all model, this categorization enables the validator set to evolve more intentionally, recognizing contributions to protocol security, infrastructure resilience and governance alignment, and Ethereum public goods and decentralization. Distinct Node Operator Types CMv2 allows NOs to qualify for one of the six distinct operator types: The article below provides a high-level overview of each CMv2 Node Operator type and how their distinctive characteristics contribute to the protocol’s resilience, decentralization, and align with Lido DAO strategic priorities. Check out Research Forum post for a detailed description and the full framework. 1. Professional Operator This type serves as the entry tier for newly onboarded NOs joining CMv2. It is designed as a trial stage for operators to demonstrate operational reliability, security maturity, and the ability to meet the protocol performance expectations before progressing into more profitable types. It will help preserve the high performance standards historically associated with the Curated Module, while also creating a transparent pathway for onboarding new operators into the Lido validator set. The category will also serve as a fallback for Node Operators that no longer comply with the requirements of another NO type following the reassessment or material operational incidents. 2. Professional Trusted Operator It represents the default category for established, for-profit Node Operators within CMv2. This type will include NO migrating from the current Curated Module as well as Professional Operators graduating from the onboarding stage after demonstrating sustained operational excellence. Professional Trusted Operators are expected to form the operational backbone of CMv2. This category reflects long-term protocol sustainability built on consistent validator performance, reliability and operational maturity. 3. Public Good Operator The Public Good Operator type recognizes entities meaningfully involved in the development, research, or maintenance of core Ethereum infrastructure, including Execution Layer, Consensus Layer, and validator clients. Clients are foundational to Ethereum’s stability and security. Supporting a healthy and diverse client ecosystem helps reduce systemic risks associated with client supermajority while improving the long-term resilience of the validator ecosystem. Lido DAO has historically supported client teams and public-good builders — explorers, tooling, etc. — through participation in the Curated Module and LEGO grants. CMv2 formalizes this approach by structurally recognizing Ethereum client teams within the module design itself. This category reinforces the importance of sustaining Ethereum’s open-source infrastructure and acknowledges the role public-good contributors play in maintaining a resilient and decentralized network. 4. Extra Effort Operator The type is designed to recognize Node Operators who contribute additional value to Lido beyond validator operations alone. This includes operators contributing to protocol growth through capital participation (stake into stVaults or Lido Core), protocol service roles such as the Lido Oracle or Deposit Security Committee, and long-term governance alignment through meaningful LDO holdings and voting activity. Formal recognition of entities that actively strengthen the protocol across multiple dimensions important to the DAO creates a mechanism to incentivize long-term Node Operator alignment with the protocol’s success and helps reinforce the sustainability of the Lido ecosystem. 5. Decentralization Operator Node Operators contributing to validator set resilience and decentralization through client diversity, geographic and infrastructure distribution qualify for this type. Running non-majority clients, operating infrastructure in underrepresented regions, and reducing reliance on concentrated cloud providers all help mitigate correlated risks within Ethereum’s validator ecosystem. Lido contributors have long empowered decentralization through research, ecosystem coordination efforts, monitoring and reporting, including the quarterly Validator and Node Operator Metrics (VaNOM) dashboard. With the introduction of this NO type, a public decentralization commitment transitions to a measurable and incentivized property within the CMv2. The framework allows operators to be formally recognized for strengthening Ethereum’s resilience, which allows for a more secure, fault-tolerant, and operationally resilient Lido validator set. 6. Intra-Operator DVT Cluster This category applies to CMv2 operators running DVT clusters that use @Obol_Collective or @ssv_network within their infrastructure setup and can be assigned alongside another NO type. DVT-based validator operations improve operational resilience and fault tolerance by distributing validator responsibilities across multiple nodes or infrastructure participants. By separating this into an independent type, CMv2 preserves flexibility for the DAO to evolve parameters and incentives related to DVT adoption over time as the technology matures and protocol priorities evolve. What’s Next Lido contributors are actively working toward the launch of Curated Module v2 with the Hoodi testnet already underway, security audits in progress, and additional DAO votes expected throughout June and July. If approved by LDO tokenholders through on-chain governance, CMv2 is expected to go live in July marking the next major evolution of the Lido Core. Find Out More Interested in learning more about CMv2 and the future of the Curated Module? Explore the materials below: Future of the Curated Module | CMv2 Landscape (Research Forum proposal) Operators Types taxonomy (Talk from Lido Day 2025) Node Operator Type Assessment Framework | CMv2 (Research Forum proposal) Node Operator Type Assessment Framework (Talk from Lido Day 2026) Bond values & approach suggestion (Research Forum proposal) Proposed CMv2 Parameters by Node Operator Type (Research Forum proposal)