TDP 35: Q1 Signer Rotation & Offboarding Clause

Summary:

It is proposed to rotate a signer in both the TreasuryDAO and the ProtocolDAO.

With this rotation, it is also proposed to add a new offboarding clause that allows the respective multisigs to eject a signer from the group without prior governance approval, should the corresponding vote on the internal Snapshot page of the DAO be unanimously in favour.

Onboarding a new replacement signer will still have to go through governance as before. This is done to be able to act swiftly in case of unexpected adversary behaviour.

It is suggested to replace the signer who owns the addresses 0x4B37BbC8CAb32aade27Ce8b1bb2A9E614de81E03 & 0xD8baE7d96df905E46718B6ceE3410F535e11bF20 in both groups with a different core contributor.

For the ProtocolDAO, it is suggested to onboard 0xb4dB24A77db4A77242F1e7E6Aa346aeCC440f6Df to the group. This applies to the ProtocolDAO Safe on Ethereum Mainnet as well as on Polygon.

For the TreasuryDAO, it is suggested to onboard 0xB27a7bD98421EB9eAEE522335F45A6F5B65C5C8d to the main signer group and also to the Asset Management subDAO, both in which he will act in the capacity of lead signer moving forward. This applies to the TreasuryDAO Safe on Ethereum Mainnet, as well as the Asset Management subDAO Safe on Ethereum Mainnet and Polygon.

Links

• RFC: Q1 Signer Rotation & Offboarding Clause
• Proposal: TDP 35: Q1 Signer Rotation & Offboarding Clause
• Discussion: TDP 35: Q1 Signer Rotation & Offboarding Clause

Should the outlined signer rotation for the TreasuryDAO and the ProtocolDAO be performed and the offboarding clause be implemented as proposed in TDP 35?