The Beets Treasury exists to safeguard the long-term stability, sustainability, and growth of the protocol. This framework defines strategic goals and risk classifications to guide treasury management. It establishes clear priorities, allocation limits, and operational processes to ensure responsible stewardship of DAO assets:
Main changes compared to the previous treasury framework:
Beets Treasury contains both assets fully controlled and manageable by the DAO and assets with specific limitations and/or restricted use cases. Based on this, the following definitions are used:
Allocation limits expressed in this framework are based on the Active Treasury.
## Risk Classification Treasury assets are categorized under four risk levels, each with a maximum allowable allocation. If a higher-risk category is not fully utilized, the unused portion may be reallocated to lower-risk categories.
Risk level 0 (Minimal) - Assets with minimal exposure to smart contract risk and minimal attack surface. Max allocation: N/A Examples: Assets in DAO multisig, assets earmarked for grants, lending on Aave
Risk level 1 (Low) - Simple or yield-bearing assets with low composability risk. Max allocation: 50% Examples: Non-boosted pools on Balancer/Beets, Balancer concentrated liquidity pools (ECLP, reCLAMM), lending on established protocols, sGHO, stS, wstETH
Risk level 2 (Moderate) - Assets in more complex yield strategies with moderate smart contract exposure. Max allocation: 30% Examples: Boosted pools with proven track record, Aave umbrella, liquidity providing on external protocols
Risk level 3 (High) - High-yield, experimental, or leveraged strategies with significant risk exposure. Max allocation: 20% Examples: Pools with experimental boosts, multi-strategy contracts, leveraged positions
Beets Treasury management is defined based on the following goals:
Objective: Maintain sufficient liquidity to fund a critical bug bounty payout as per BIP-26. Amount: 200,000 USD Allocation: Native stablecoins (Risk level 0).
Objective: Ensure funding for 6 months of core contributor and infrastructure expenses (per BIP-92, BIP-40, BIP-56). Subject to change with future BIPs. Amount: 327,000 USD (based on current expense structure) Allocation: Stablecoins or pools composed of only stablecoins (up to Risk level 2).
Objective: Utilize protocol-owned assets on Beets to generate revenue and/or promote protocol growth. Amount: N/A Allocation: Assets on both Sonic and Optimism deployments. Can be staked on external protocols (e.g., AURA) to maximize returns.
Objective: Deploy treasury assets into external protocols (non-BPT assets) to enhance revenue. Amount: N/A Allocation: Every new protocol must be whitelisted by DAO vote.
Review Cycle: Treasury composition will be reviewed at least every six months by the Music Directors, with rebalancing as required.
Emergency Action: Music Directors may exit positions immediately if risks are deemed unacceptable.
Treasury rebalancing: Music Directors may reallocate up to a maximum of $200k per month of the treasury balance. This would include entering and exiting liquidity pools, moving funds cross chain and/or adding to existing deposits. Any reallocation greater than $200k will require a treasury vote.
Protocol whitelisting: Music Directors are required to raise a governance vote the first time they seek to deposit assets into a new protocol. That proposal shall define the maximum exposure the treasury will have to that protocol's smart contract risk.
Transparency: Transaction hash with a short description will be provided on Discord for transaction from Beets treasury wallets:
Operations: Music Directors ensure the timely payment of governance approved expenditures and bug bounty claims.