- [x] I have read the EDF Operator Key Custody Policy and my setup follows it
- [x] I created a dedicated owner multisig, at least 2-of-3, with signers held by different people on different devices
- [x] The multisig is used for nothing except this delegation contract
- [x] I deployed my DelegationContract from the official DelegationFactory, with a 48-hour(172800 s) cooldown
- [x] I verified on-chain that owner(), getDelegate(), getCooldown() and isTerminated() are what I intended
- [x] I set up 24/7 alerts on DelegateNominated, DelegateRevoked and Terminated
I have read the EDF Operator Key Custody Policy and my setup follows it
I created a dedicated owner multisig, at least 2-of-3, with signers held by different people on different devices
The multisig is used for nothing except this delegation contract
I deployed my DelegationContract from the official DelegationFactory, with a 48-hour (172800 s) cooldown
I verified on-chain that owner(), getDelegate(), getCooldown() and isTerminated() are what I intended
I set up 24/7 alerts on DelegateNominated, DelegateRevoked and Terminated
The new DSM is configured with 6 guardian DelegationContracts and a quorum of 4. Both contracts will be activated by the upcoming on-chain vote; until then the current DSM and Locator implementation stay in use.
Item 1 submits one Dual Governance proposal that atomically switches the protocol to EDF and DepositSecurityModule v5 in a single Agent.forward call (78 actions):
for each of the four oracle committees and each of the nine oracle operators: remove the operator’s EOA hot key from the HashConsensus and add the operator’s DelegationContract, keeping the quorum of 5 (72 actions);
upgrade the LidoLocator implementation so that its depositSecurityModule entry points to the new DSM v5, all other entries stay the same (1 action);
move STAKING_MODULE_UNVETTING_ROLE on StakingRouter from DSM v4 to DSM v5 (2 actions);
move TOP_UP_ROLE on TopUpGateway from the depositor bot EOA to the depositor bot DelegationContract (2 actions);
grant BUFFER_RESERVE_MANAGER_ROLE on Lido to the Easy Track EVMScriptExecutor (1 action).
Item 2 is executed by the Aragon Voting directly: add the SetDepositsReserveTarget Easy Track factory with the permission limited to Lido.setDepositsReserveTarget(uint256), per the CMC deposit reserve target proposal.
DSM v5 is already deployed with the guardian set moved to DelegationContracts (see the deployment post), so the vote does not touch the guardians: it only switches the protocol to the new module. The guardian quorum stays 4 of 6, Stakely takes the seat of Kiln.
The on-chain vote is planned to start on Wednesday, September 16. Once the vote is live, a link to it and instructions for verifying the vote items will follow in this thread.