Summary:
Proposal to whitelist the Stake DAO multisig on Stake DAO.
Context:
Since the launch of liquid lockers, Stake DAO’s voting power has been handed back to users, and with the current bribing environment, the DAO didn’t manage to retain its votes for its different pairs (sdt/eth, sdTKN/TKN, etc).
The DAO itself owns a lot of CRV that are either locked through the CRV locker or staked in the sdCRV/CRV pool.
Until now, the sdCRV were not staked to allow the users to have an even greater yield and voting power, but since we need to maintain the yield in our pools, we recently staked our sdCRV. The DAO now benefits from unboosted voting power which it uses to incentivise its liquidity pairs.
Rationale:
To start getting back some yield to our different pools in a more efficient manner, it is relevant to allow the DAO to lock SDT and boost its voting power.
This proposal aims to whitelist the Stake DAO Gnosis Safe multisig: (0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063) to interact with veSDT contract.
This whitelisting will have several advantages for the protocol:
- Allow voting on Curve and Frax for pools in the best interest of the DAO;
- Potential protection against hypothetical governance attacks. The multisig will not normally vote on governance proposals, but having this possibility can be a good security protection in extreme cases;
- Possibility to vote on Stake DAO gauge votes in the best interest of the DAO.
Technical implementation:
Whitelist Stake DAO multisig address: 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063
on the following contract:
0x37E8386602d9EBEa2c56dd11d8E142290595f1b5
Voting option:
- Yes, for Stake DAO Multisig whitelist
- No, against Stake DAO Multisig whitelist
- Abstain
0 voters