# Lido proposes DAO Ops Multisigs Policy 3.0

> If approved, signer rotations would no longer have to preserve a simple majority of original signers, static signers would lose protected status, and the existing seven-day rotation objection period would be removed.

- URL: https://riadefi.com/on-chain/2026-04-06-lido-dao-ops-multisigs-policy-3-proposal/
- Type: Control change
- Stage: Proposed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-04-06
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2026-04-13
- Advisor-relevant: yes
- Affects: Lido (protocol)

## What happened

Lido proposed replacing DAO Ops Multisigs Policy 2.0 with Policy 3.0 and aligning related Lido Foundation bylaws with the new framework.

## What changed

If approved, signer rotations would no longer have to preserve a simple majority of original signers, static signers would lose protected status, and the existing seven-day rotation objection period would be removed.

## What did not change

The proposal does not itself rotate a signer, change a particular Safe threshold, or expand a specific multisig's transaction authority. The DAO would retain the ability to object through Snapshot voting.

## Confirmed

- The proposal would replace Policy 2.0.
- The original-signer-majority requirement would be deprecated.
- The static-signer rule would be deprecated.
- The seven-day objection period for member rotation would be removed.
- Related Foundation bylaws would require at least three multisig members.

## Still open

- The Snapshot outcome and effective policy text.
- Which existing multisigs and bylaws are ultimately updated.
- The final rotation, disclosure, emergency, and objection procedures.
- Whether removal of the safeguards materially increases signer-capture or rapid-rotation risk.
- Any subsequent signer rotations performed under Policy 3.0.

## What it means for an advisor

- Review the Lido memo's multisig rotation and delegated-control assumptions before Policy 3.0 is treated as operative.
- Inventory affected Safes and verify thresholds, owners, rotation procedures, disclosure exceptions, and DAO revocation paths after implementation.

## Sources

1. [Lido DAO Ops Multisigs Policy 3.0](https://snapshot.org/#/lido-snapshot.eth/proposal/0xde04e720b6c44e6d5a356021e464dc4d4b3036c6602c6088806f1f898cb7a56b) · Snapshot (Lido DAO space) · 2026-04-06


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.