[RFC] - DAO GOVERNANCE OVER TREASURY ACTIONS AND STRATEGY
- Yes, Support Enhanced DAO Governance for Treasury
- No, Allow full discretion to Treasurer / Founding Team (no change)
0 voters
Scope:
This RFC examine the proposal made to create limitations on Treasury Investments such as capital allocation risk limits, and also DAO approval on actions such as token voting delegation.
Link to previous [DAO Discussion]: “[DAO Discussion] - Defining Stronger DAO Control Measures on Treasury Management”
Objective:
This proposal aims at enhancing DAO control over:
- Illiquid Investment Activities
- Voting or Voting Delegation (exerting voting power on other protocols)
- Risk Limits
1) Re-Allocation of liquid Assets to Illiquid Assets
The DAO should decide whether liquid assets (such as USDT, USDC, MIM, WBTC, WETH, etc) can be turned into which illiquid assets, which includes non-liquid staked tokens or VC investments. These are decisions that TM (or anyone) should not be making unilaterally.
If this proposal isI suggest explicit DAO approval (YES/NO) is obtained through an official vote and if passed, to vote on item 1A and 1B below.
-
A) For example, should have CVX been staked into vlCVX? I would propose that we would vote on this retro-actively as there are un-staking events in July and August. (YES/NO) <- This will be a WIP X.1
B) A VC Allocation headroom (excluding current ones) should also be voted for. This can be for example max 5.0% of the Treasury before a TM would seek for more headroom for example. (YES/NO) ← This would be WIP# X.2
2) Voting or Voting Delegation
Currently, this is directly related to vlCVX voting, but this may apply to other situations. A TM (or this protocol) should not acquire assets for the sole purpose of influencing a vote in another protocol. A key control factor is having the DAO to determine the voting or vote delegation action.
The two questions to be asked here is:
-
A: Should the DAO determine through a vote on how WL should vote with held tokens. Such voting direction request should come from the TM ?
B: Provided the answer to 2A is favorable, should the vlCVX votes be delegated to Votium and to the Bribe Pool Optimizer with the earliest possible Gauge Vote ?
Note that the previous vote into Votium would have yielded US $380,000 by my calculations and votes occur every two weeks.
3) Risk Limits
Should the DAO give certain risk limits over % of asset holdings in its Treasury as proposed below ?
Provided this proposal passes, below are the proposed risk limits:
- Non Stable-coin Directional Exposure 30% of Liquid Assets (BSGG Excluded)
- Stable-coins risk:
a. USDT 25% (about 52 mm USD)
b. USDC 30% (subject to temporary raise for redemption)
c. DAI 25%
d. MIM 25%
e. Combination of all others (or any) 15%, and among these max individual limit 10%
With these DAO decided limits, the treasury manager will have better guidelines to limit conflict of interest, and manage risk. wMEMO holders can be also rest assured that material changes to the liquidity or risk profiles would have to be proposed to the DAO for approval.
Business and/or technical requirements of the implementation of the proposal:
None are needed.
Since an RFC is a “work in progress” Proposal, not all of these points need to be filled out from the beginning. They can be added over time as the RFC evolves into a mature Proposal.