Adopt the Node Operator Type Assessment Framework for CMv2

Proposal

This proposal seeks DAO approval for the Node Operator Type Assessment Framework for Curated Module v2 (CMv2). The framework introduces six Node Operator types: Professional, Professional Trusted, Public Good, Extra Effort, Decentralization, and an additional Intra-Operator DVT Cluster type. It defines the inclusion criteria for each type, the assessment methodology, the operator-provided information used as the basis for evaluation and scoring, and the reassessment process.

The proposal aims to create a granular mechanism for reflecting strategic priorities by adjusting how different forms of Node Operator contributions to the Lido ecosystem are recognized and refining the qualification criteria in response to evolving protocol needs. Responsibility for maintaining and applying the framework is proposed to be delegated to the Curated Module Committee (CMC), which will periodically reassess Lido protocol needs and adjust the framework accordingly.

The proposed framework does not specify an exhaustive set of type assessment scoring parameters or thresholds, nor does it define economic incentives or fee-related parameters. The scoring parameters and thresholds will be defined by the CMC for each assessment round. Any fee values, incentive coefficients, or related parameters will be proposed through separate DAO governance votes and may change independently from the framework. While economic parameters are outside the scope of this proposal, Node Operator type assignments would determine the incentive configuration applied to operators within CMv2.

The full framework is available on the Research forum.

Framework Summary

NO Types

• Professional Operator — the onboarding/trial stage for new CMv2 operators, and a fallback type for operators downgraded from another type.
• Professional Trusted Operator — the default trusted state for established operators, including CMv1 operators migrating to CMv2 and CMv2 Professional Operators graduating from the trial stage.
• Public Good Operator — operators contributing to Ethereum core infrastructure, including Execution Layer, Consensus Layer, or validator client development or maintenance.
• Extra Effort Operator — operators demonstrating additional alignment with Lido through stake contribution (via stVaults or Lido Core), LDO holdings, governance voting, or participation in certain Lido protocol service roles (e.g., operating Lido Oracles or the DSM).
• Decentralization Operator — operators contributing to decentralization through client diversity, geographic distribution, and infrastructure setup.
• Intra-Operator DVT Cluster — an additional classification for operators running DVT clusters within the same entity.

Professional Operator and Professional Trusted Operator

New Professional Operators are onboarded through onboarding rounds proposed when the CMC, together with contributors to the Lido Node Operator Mechanisms workstream (NOM), determines that Lido protocol conditions and DAO strategy justify expanding the curated operator set. Applicants submit structured information on their background, staking experience, infrastructure, key management, operations, monitoring, incident response, security posture, and alignment with the Lido protocol. The CMC conducts a multi-dimensional, score-based assessment covering areas such as key security, infrastructure architecture, decentralization contribution, business alignment, operational performance, monitoring, and security posture. The final list of operators proposed for onboarding is submitted to the Lido DAO via a Snapshot vote. The CMC may also propose exceptional onboarding outside standard rounds where there is a strong strategic or ecosystem-aligned rationale, subject to the same assessment standards and DAO approval.

Professional Operators may graduate to Professional Trusted Operator upon CMC review and confirmation after demonstrating sufficient active participation in CMv2 (ideally 9 months), performance above the network average, no slashing or material inactivity penalties, no major operational incidents within the last 6 months, constructive communication with NOM contributors, and adequate security and operational maturity. Professional Trusted Operators may later qualify for another eligible type in accordance with the applicable assessment process for that type.

CMv1 operators migrating to CMv2 are treated as Professional Trusted Operators by default, based on their established track record within the Lido Protocol.

Public Good Operator

Public Good Operator status is application-based and reviewed by the CMC.

The assessment may consider several factors, including but not limited to operator’s involvement in Ethereum client development or maintenance, client release support, bug fixing, allocation of engineering resources or revenue to Ethereum client work, and broader engagement with the Ethereum technical ecosystem.

The full Public Good Operator assessment methodology is available on the Research forum.

Extra Effort Operator

Extra Effort Operator status is application-based and reviewed by the CMC.

Operators may qualify through different categories of contribution, including stake contributions to Lido Core or stVaults, LDO holdings (excluding borrowed or otherwise temporary positions) and governance participation via voting as a sign of long-term DAO alignment, or receive limited credit for operating certain critical protocol infrastructure such as Lido Oracles or the DSM.

The Extra Effort type is applied proportionally through five tiers, respectively corresponding to 20%, 40%, 60%, 80%, or 100% of the operator’s validator stake. The categories mentioned above contribute independently to the final tier, are additive, and are capped at 100%. Tier thresholds for each tier are expected to be reassessed periodically, typically before each reassessment cycle.

The full Extra Effort Operator scoring methodology is available on the Research forum.

Decentralization Operator

Decentralization Operator status is assessed using a score-based methodology that leverages Lido Validator and Node Operator Metrics (VaNOM) data. Node Operators must disclose information about their infrastructure setup in full detail and accept that this data may be used to report infrastructure setup publicly (at a disaggregated level).

Eligible operators are ranked across three pillars: CL/EL Client, Geographic, and Infrastructure diversity. Each pillar assesses a corresponding aspect of the validator setup's adherence to decentralization principles of Ethereum and the Lido protocol. For each reassessment cycle, the CMC defines a limited number of available Decentralization Operator seats in advance. The highest-ranked eligible operators would receive the type, subject to the number of available seats and exclusions from earlier assessment steps. If two Operators are materially tied for the final available seat, the CMC may split that final seat and assign the Decentralization Operator type to both, with each receiving the type for 50% of their keys.

The full Decentralization Operator scoring methodology is available on the Research forum.

Intra-Operator DVT Cluster

The Intra-Operator DVT Cluster type can be issued on request, in addition to other types, and may be assigned outside regular reassessment cycles.

Operators under this type must run DVT validators using Obol or SSV, generate keys via DKG ceremony, enroll in DVT-specific monitoring, maintain a testnet cluster, and coordinate with NOM contributors to verify DKG usage and monitor infrastructure diversity.

The full Intra-Operator DVT Cluster assessment methodology is available on the Research forum.

Reassessment cadence and order

The framework proposes reassessments twice per year, aligned with the availability of reliable VaNOM data.

For special operator types, reassessments are conducted in the following order:

1. Operators applying for the Public Good Operator type are assessed. Operators approved for the Public Good Operator type are excluded from being considered for the Decentralization Operator type in the same assessment round.
2. Operators applying for the Extra Effort Operator type are assessed. Operators receiving Extra Effort status on 100% of their keys would not be considered for Decentralization Operator status in the same reassessment round. Operators receiving Extra Effort status on only part of their keys may still be considered for the Decentralization Operator type on the remaining keys.
3. All remaining eligible operators are assessed for the Decentralization Operator type based on VaNOM data.

Reassessment outcomes are intended to be shared on the Research forum in an aggregated form.

Submitted data for assessment is assumed to be truthful and materially accurate. Any indication of inaccurate or misleading data may be investigated and could result in penalties, up to removal from the Curated Module.

The full reassessment cadence and order is available on the Research forum.

Downgrading path

If an operator no longer satisfies the criteria supporting its special type qualification (Extra Effort, Public Good, Decentralization operator), the CMC may reduce the operator’s tier or change its type to Professional Trusted Operator.

If a reassessment or material operational event indicates meaningful deterioration in reliability, security posture, operational maturity, or overall standing, the CMC may determine that the operator should be downgraded to Professional Operator, either temporarily or until the relevant concerns are remediated and verified in a later reassessment cycle.

Framework maintenance and implementation

If approved, the CMC would be responsible for maintaining and applying the framework, including:

• adjusting the scoring system, requirements, and methodology;
• defining thresholds and parameters for each assessment round;
• determining reassessment timing;
• assigning Node Operator types according to the current framework;
• communicating framework updates publicly on the Lido Research forum.

All CMC decisions shall be made in accordance with the framework set out herein. Where the framework does not expressly address a particular matter, decisions relating to NO onboarding or offboarding shall be submitted for DAO approval, while the CMC shall retain authority over operational matters related to maintaining and applying the framework.

The DAO retains the ability to modify, extend, remove, or reassign responsibilities granted under the framework through future governance votes.