SETUP-43 - Update the Operators multisig (remove 2 addresses, add 2 addresses)

Governance
1

Summary

This proposal updates the Operators multisig plugin of the Protocol DAO on Ethereum mainnet: two addresses are removed and two addresses are added. The DAO executes the change on the multisig plugin itself. If it passes, the approval threshold is unchanged and the multisig’s address list reflects the two removals and two additions below.

Motivation & Context

The set of addresses allowed to approve proposals in the Operators multisig is being updated. This can only be changed by governance, so both changes are enacted through this DAO proposal.

Change Address
Remove 0x32f3D0D7E20Ca11Cad21f32Dad91506ea89f5897
Remove 0xE53e32a669357Ab0360103d8f294812B914AF9e4
Add 0xc49376C4D044011eEce6eE69eFAe06f0Cc2bd008
Add 0x27B1c34F2aeEc91F9704BD1CE288E5c667F29045

No specific execution ordering relative to other proposals is required.

Proposed Changes

Both actions target the Operators multisig plugin (0xE43c73aAb2b6aBBad6d0461997ce1cfea5ABe66f) on Ethereum mainnet, and are executed by the Protocol DAO (0xB6D69D5F334d8B97B194617B53c6aB62f8681Ef3), which holds the permission to update the multisig’s address list.

  • Action 1 — removeAddresses(address[]): removes 0x32f3D0D7E20Ca11Cad21f32Dad91506ea89f5897 and 0xE53e32a669357Ab0360103d8f294812B914AF9e4 from the multisig.
  • Action 2 — addAddresses(address[]): adds 0xc49376C4D044011eEce6eE69eFAe06f0Cc2bd008 and 0x27B1c34F2aeEc91F9704BD1CE288E5c667F29045 to the multisig.

Technical Details

  • Network: Ethereum mainnet.
  • Target contract: Operators multisig plugin 0xE43c73aAb2b6aBBad6d0461997ce1cfea5ABe66f — verify against protocol-registry. This is the standard Aragon OSx Multisig plugin; addAddresses/removeAddresses are restricted to the DAO.
  • Executor: Protocol DAO 0xB6D69D5F334d8B97B194617B53c6aB62f8681Ef3 — verify against protocol-registry.
  • Encoded data / magic constants: None.
  • Cross-chain: None.

Other considerations

  • Approval threshold unchanged. Two addresses are removed and two are added, so the total count returns to its initial value; the number of approvals required is untouched. If the removal executes first, the count is temporarily 2 lower, still above the threshold.
  • Approval rights change on execution: the two removed addresses can no longer approve proposals, and the two added addresses can. Ensure the added wallets are provisioned and controlled by the intended members before approving.
  • Reversibility: fully reversible via a follow-up proposal.
  • No timelock or dependencies beyond normal DAO voting.

Resources

1 Like