Lido proposes Curated Module Committee with delegated operating authority

What happened

Lido proposed creating a Curated Module Committee to replace LNOSG and manage routine operations across CMv1, CMv2, and the Simple DVT Module.

What changed

If approved and implemented, a dedicated 5-of-9 multisig committee would receive bounded on-chain permissions for penalties, parameter updates, registry management, and operator administration.

What did not change

No committee deployment or permission grant is confirmed. The proposal says high-impact decisions such as node-operator onboarding would remain subject to DAO Snapshot votes, with routine actions subject to Easy Track objections.

Confirmed

• The proposed committee has nine named members and a 5-of-9 signing quorum.
• The proposal would deprecate LNOSG and transfer its responsibilities to the new committee.
• The proposed scope covers CMv1, CMv2, and SDVTM operations.
• High-impact node-operator onboarding would remain subject to DAO voting under the proposed model.

Still open

• The Snapshot outcome and any on-chain execution.
• The final multisig address, signer set, permissions, and permission ceilings.
• The exact boundary between routine committee actions and high-impact DAO decisions.
• The final CMv2 deployment and transition schedule.
• Whether emergency, revocation, and monitoring procedures are adequate after delegation.

What it means for an advisor

• Review the Lido memo's node-operator and staking-module control map before the committee becomes operative.
• Verify the final multisig, permissions, veto path, reporting duties, and transition from LNOSG after execution.