Lido proposes DAO Ops Multisigs Policy 3.0

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.