With the introduction of Curated Module v2 (CMv2), the governance framework of the Lido protocol’s Curated Module is shifting toward a more structured, committee-driven operational model. While the Lido Node Operator Sub-Governance (LNOSG) historically provided guidance to tokenholders in matters of Node Operator due diligence, selection, and broad operator set oversight, CMv2 introduces on-chain permissions that allow for finer governance-based operational processes. As such, given that there will likely be additional routine operational tasks in this regard, this document outlines a proposed transition of these responsibilities to the Curated Module Committee (CMC) while maintaining the DAO’s final authority over the composition of the Node Operator set and parameters related to Node Operators.
TL;DR
- This proposal establishes the CMC and fully deprecates the LNOSG, transferring its responsibilities across the Curated Modules (including CMv1, CMv2 and Simple DVT) to the CMC.
- The CMC manages standard operational workflows, including Node Operator administration, penalty reporting, registry updates, and parameter management, within its delegated on-chain permissions (including via Easy Track where applicable).
- Although due diligence and technical review are conducted by the CMC, Node Operator onboarding remains subject to a direct Snapshot vote by the DAO, after which onboarding is executed on-chain via Easy Track.
Motivation
The LNOSG was introduced to provide technical expertise and decentralized input into Node Operator onboarding decisions for the Curated Module, with its scope later expanded to cover similar activities for the Simple DVT Module. With CMv2, this role is largely superseded by clearly scoped on-chain permissions, Easy Track execution, and the CMC with explicit mandates.
As a consequence, Curated Module governance under CMv2 is expected to become more operational and execution-heavy, with recurring actions related to penalties, parameter updates, registry management, and operator administration. An advisory sub-governance structure such as LNOSG is not well suited for this type of ongoing operational responsibility. The CMC provides a clearer and more sustainable framework for delegated execution, while retaining the value of distributed expertise, including non-contributor subject-matter experts, within a formally mandated committee structure
At the same time, Node Operator onboarding remains a high-impact decision with long-term implications for decentralization and protocol security, necessitating direct DAO involvement.
The Curated Module Committee (CMC)
The CMC is a specialized body established to facilitate the day-to-day technical and operational health of Lido’s Curated Modules. The committee acts as a “fast-response” unit, handling routine administrative tasks such as penalty management and Node Operator registry updates without requiring a full DAO vote for every minor change.
The CMC will operate via a dedicated multisig wallet with a proposed 6-of-9 signing threshold to ensure broad consensus before any action is executed. The multisig will be composed of:
-
Core Contributors: The committee will primarily consist of active contributors from the Node Operator Mechanism (NOM) and technical workstreams to ensure protocol alignment.
- Will Shannon - Head of Node Operator Mechanisms
- Aleksandra Gusakova - Lido Core Product Lead
- Dmitry Gusakov - Staking Modules Tech Lead
- Sven Brekelmans - Senior NOM Analyst
- Sabrina Hsu - Senior NOM Analyst
- Alexander Movsunov - VROOM Lead
-
LNOSG Transition: in addition, existing LNOSG members were asked if they would like to transition their expertise as part of the committee, and three members volunteered to participate:
- Edouard Lavidalle - Head of Staking at Stakin by The Tie
- Ignacio Iglesias - CTO & Co-founder of Stakely
- George Bunea - CEO of Syncnode
Reporting and Communication
CMC actions will be communicated in a timely and transparent manner via the Lido Research Forum. Any operational action initiated by the CMC, including the creation of an Easy Track motion related to penalties, parameter changes, or operator management, will be publicly shared on the Lido Research Forum.
Node Operators participating in CMv2 may also use a dedicated section of the Lido Research Forum to contact the CMC with questions, issues, or escalation requests.
The Committee’s Lifespan
It is proposed that the Curated Module Committee will exist until:
- The Curated Modules (including CMv1,CMv2 and SDVT) are sunset or materially changed through a future tokenholder voting, which may supersede the CMC’s role.
- Lido token holders decide to modify or dismantle the committee by relevant vote(s) to update its composition, or alter / revoke the CMC’s roles in CMv2.
Proposed Operational Model
The transition to CMv2 and proposed usage of the CMC restructures accountability by dividing responsibilities into three distinct tracks: CMv2 Standard Operations (managed by the CMC, with any critical or sensitive operations sitting behind optimistic governance), CMv2 Operator Set Expansion (vetted by the CMC but decided by the DAO), and SDVT Standard Operations which will then be executed by the Simple DVT Module Committee.
The following sections detail how these authorities are distributed across the protocol’s active modules.
Curated Module v2 Standard Operations
In CMv2, the CMC will serve as the operational gatekeeper for Node Operator administration and penalty workflows. In practice, this means the CMC will handle incident reporting, and registry updates, while final oversight and settlement in most cases remain on the DAO side via optimistic governance mechanisms (Easy Track).
In CMv2, the CMC will be responsible for the following:
- Report and revoke general delayed penalties (locking/unlocking the Node Operator bond), with penalty settlement overseen by the DAO via EasyTrack
- Set general delayed penalty parameters (ex., minPenaltyAmount)
- Report slashing penalties, including the amount of losses for validators proven as slashed, via Easy Track
- Assign Node Operator types, create Node Operator Groups (a mapping of all sub-node-operators under a given entity (Node Operator)), and define sub-operator shares within the group (the proportion of stake that may be allocated to each sub-operator), via Easy Track
- Update Node Operator names and descriptions (also updatable by the Node Operator)
- Pause creation of new Node Operators for a specific Node Operator Type
Curated Module v2 Operator Set Expansion
Node Operator onboarding is treated as a special case due to its long-term protocol impact.
Official onboarding to the CMV2 is controlled by DAO voting processes, generally in one of two ways:
(1) The CMC and contributors from the Node Operator Mechanisms workstream monitor protocol stake distribution, and publicly open an onboarding round via announcement on the Lido Research forum with amplification across Lido-related social channels; or
(2) The DAO votes to start an onboarding round or consider a specific applicant.
- Either of these scenarios would be followed by a a full technical and operational review of Node Operator applicants by the CMC, following similar due diligence undertaken by the LNOSG as described in the Node Operator portal
- The CMC would submit an onboarding proposal to Snapshot
- Upon DAO approval, the CMC executes onboarding to CMv2 via Easy Track
This preserves DAO control over Node Operator set expansion while improving operational efficiency for DAO voters.
Simple DVT (SDVT) Module Operations
In addition to Curated Module responsibilities, the Curated Module Committee (CMC) will assume oversight of the Simple DVT (SDVT) Module following the deprecation of the LNOSG. This ensures continuity of technical expertise for DVT clusters within the same committee structure. Easy Track and operational execution would continue to be handled by the Simple DVT Module Committee.
For the Simple DVT Module, the CMC will be responsible for:
- Reviewing and evaluating all Node Operator applications and DVT cluster configurations.
- Coordinating with DVT providers to ensure the technical health and security of the module until its scheduled sunset.
- Coordinating with the Simple DVT Module Committee for changes to the SDVT Node Operator registry.
Next Steps
Following the publication of this proposal, we invite the community to engage in a period of open discussion and review on the Lido Research forum. Once the feedback period is complete, the proposal will be put forward for a DAO-wide Snapshot vote during the next available cycle in April 2026.
Pending a successful Snapshot outcome, the necessary permissions and technical shifts to formalize the CMC’s role and deprecate the LNOSG for curated operations will be included in a subsequent on-chain Aragon vote for final implementation.