[Temp Check] Start Building a Curve DAO Treasury

Summary

Curve’s current “treasury” consists of USD $16m in CRV tokens. All protocol revenue is currently redistributed to LPs, veCRV and scrvUSD and there are no mechanism to grow the treasury. This is not sustainable in the medium to long term. Currently, the only way to cover the costs of maintaining and growing the protocol (payroll, audits, services, etc.) is by selling this limited amount of CRV. The amount would only cover ~3 years of expenses at the current estimated burn rate and CRV price. To remedy this, this proposal introduces two mechanisms to redirect a part of protocols fees towards a treasury:

  1. Redirect all of 3pool revenue to the community fund
  2. Redirect 10% of veCRV fees to the community fund

The mechanisms are mutually exclusive and only one will be developed and presented for approval to the DAO as a result of this discussion.

State of the DAO’s Finances

Current Assets and Annual Expenditures

The DAO has ~$16m in assets and spends ~$5m per year. It currently only has three years of runway.

Curve has no formal treasury to speak of. The closest equivalent is the community fund, which was originally seeded with 151,515,151 CRV back in 2020. Later, 28 million CRV were allocated to the grant council (here and here), 75.5 millions were spent to refund victims of the re-entrancy hacks (here and here), and 21 million went to Swiss Stake to cover upcoming development (here).

Of the original amount, 26 million CRV (USD $12m at current prices) remain in the community fund and 9 million (USD $4m) in the grants council multisig. The DAO needs to spend $4m per year to support development and audits via Swiss Stake. The costs of other service providers (such as Llama Risk) and grants bring the total to over $5m/y. In addition to paying developers and auditors, the protocol could also use treasury funds for a variety of other purposes (cover bad debt if it threatens the protocol’s viability, incentivize new products, etc.). Being entirely denominated in CRV, the treasury is exposed to the price risk of the CRV token. Selling assets will also put downward pressure on the price of the token.

While the situation requires urgent action, it is far from being critical as the protocol generates a healthy amount of revenue.

DAO Revenue

The DAO has generated over $40m in revenue in 2024 and is on track to reach a similar amount in 2025. Basic operating costs represent only ~10% of this amount.

While Curve’s revenue fluctuates with the fortunes of the crypto market, the protocol generated over $40m in fees in 2024. Fees for the first two months of 2025 amount to ~$5.4m, which, with a crude projection, should get us above $35m this year. A typical startup’s operating expenses account for 60 to 90% of revenue, for Curve it is only about 10%. The protocol is lean, but is also underspending on sustaining its growth.

If the revenue is not used to cover the protocol’s growth and operating expenses, where does it all go? In short, veCRV. A baffling 70% of the DAO revenue is redirected towards governance token stakers:

This is capital that could be reinvested in development, security and marketing but instead goes to reward stakeholders who, since the rise of liquid wrappers, lack long-term incentives to steward the protocol’s growth. That is not to say that veCRV provides no value to the protocol, but this situation is akin to a four-year-old startup allocating 70% of its revenue to dividends.

Companies do not typically redistribute revenue to shareholders in the early years of their lifecycle. When tech companies do give dividends, the median dividend payout ratio is below 15%, 5 times less than what the DAO currently pays out. It’s also worth noting that while early contributors to the protocol received a sizeable CRV allocation they could lock to receive yield, the composition of the core team and other contributors has entirely changed since the early days of the protocol. Almost none of the current contributors have a veCRV position sizeable enough to generate sustainable income from yield.

Treasury Accumulation Strategies

The DAO can start accumulating a treasury by either taking a larger cut of the yield of certain DEX pools or a small cut of the distributed fees.

This has the advantage of diversifying the treasury beyond CRV, as fees will be paid either in yield bearing LP tokens or in crvUSD.

Strategy #1: Redirect Fees of Selected Target Pools, Starting with 3pool

Overview

Directing all fees from 3pool to the treasury via a new proxy owner contract would cover the majority of the protocol’s expenses, but would rely entirely on a single pool and its largest LP.

A recent DAO proposal raised the 3pool’s admin fees to 100%, meaning that all of its trading fees are now redistributed to veCRV. The 3pool is one of the highest earning pools on Curve and its revenue alone would cover most of the protocol’s operating expenses:

Recent changes to the pool’s parameters (higher A and higher trading fee), are also projected to increase revenue. While the changes are too recent to draw any definitive conclusion, the preliminary data is encouraging:

While a set of special circumstances make the 3pool an ideal candidate for this strategy, other pools could be targeted. For instance, to nudge LPs to migration out of obsolete pools, the fees could likewise be increased 100% to the benefit of the DAO and redirected towards the treasury. Or future pools could be deployed that split the 50% admin fee share between veCRV and the treasury.

Deployment

This strategy will require a contract akin to crvUSD’s FeeSplitter, but adapted to DEX pools and some of their specific characteristics (the contract for 3pool, for instance, would need to implement some way to access ownership admin functions). Newer factory pools present another set of challenges as the fee_receiver is shared among all pools, but the contract could likewise act to reallocate fees between veCRV and the treasury.

For 3pool specifically, 2 proposals will be needed, one to commit_transfer_ownership and another to apply_transfer_ownership to the new splitter contract.

Assessment

Pros Cons
• Relatively painless for veCRV holders, as half of funding will come from revenue previously redistributed to LPs • Risky and unsustainable: treasury will depend on fees from a single pool with one major LP rather than benefit from overall protocol growth
• Flexible: can redirect part of the fees on targeted individual pools or pool types • If other pools are added after 3pool, will need to handle burning as fees will be paid in LP tokens
• Strategy is not exposed to the upside of crvUSD growth

Strategy #2: Take a 10% cut of all DAO revenue

Overview

The cut would be applied directly on all revenue distributed to veCRV for a small decrease of 40bps in APR

The DAO currently generates $40m in revenue and 10% of that would start to cover operational expenses. This strategy yields steady stablecoin revenue that would grow with the protocol’s revenue. The cut would lower veCRV APR by an equivalent 10% which at current value is a small 40bps decrease.

There is currently USD $438 million in the veCRV contract, and the last weekly fee distribution was $333,121. Discounting lock times, this gives an APR of 3.95% ($333,121 / $438,000,000 * 52). With a 10% lower fee distribution, the APR would have been 3.55% instead. As a significant portion of the yield for CRV now comes from bribes and additional token emissions or incentives from liquid staking protocols, this should not decrease CRV’s attractiveness as a yield generating asset.

Deployment

This strategy would likewise use a FeeSplitter like contract which could be added as a hook to the Fee Collector’s Hooker contract. The contract would then take a portion of fees already converted to crvUSD and forward the remainder to the usual fee distribution contract for veCRV. Updating the hookers will require a single proposal/vote by the DAO.

Assessment

Pros Cons
• Straightforward and easy to keep track of as there is one single point for splitting (as opposed to potentially multiple individual pools for strategy #1) • Direct impact on incentives: each percentage point of fees redirected causes an equivalent percentage reduction in veCRV APR
• Protocol treasury grows proportionally to overall protocol revenue • Less flexible as we can’t target specific pools or products
• Burning already handled, treasury accumulates crvUSD
• The %age of the cut can easily be adjusted up or down

Final Destination of Funds

All funds taken from the protocol’s revenue will be redirected to the community fund.

This has the following advantages:

  • The DAO maintains control over the funds, and any allocation from the treasury will require DAO approval
  • The community fund has hitherto acted as an all-purpose money stash to pay for development, grants and insurance at the DAO’s discretion. This flexibility and vagueness of purpose are desirable features.

What this proposal is NOT about

  • This proposal is NOT meant to start a debate on treasury management (what assets to hold in the treasury, what yield strategies to use)
  • This proposal is NOT meant to start a debate on how to allocate the funds (Swiss Stake, grant council, autobribes, etc.)

While these are potentially interesting discussion topics, they are only worth discussing if the DAO has money. The DAO currently has no money. Let’s keep the discussion focused on ways the DAO can start making money.

2 Likes

This is a great proposal, and I’m happy to see this push toward a healthier and more sustainable DeFi path for the Curve DAO. This will form the cornerstone of a strong and resilient long-term DeFi ecosystem.

Strategy 2 seems better aligned with long-term goals and is more future-proof. There should be clear KPIs, and the allocated funds should ultimately contribute to increasing revenue for the Curve DAO as a whole.

I would love to see Strategy 2 combined with an execution mandate establishing a working group to explore the best ways to allocate these funds. IMO, subDAOs are the way forward in this proposal. From @WormholeOracle, some groundwork is already being laid to form subDAOs. These subDAOs will have governing groups with members who can be voted in or out by the overall Curve DAO.

2 Likes

This is not the only way to generate revenue for DAO. The idea may have been considered, but I’ll voice it here.

Curve currently has an interface that:

  1. Doesn’t protect against MEVs in any way
  2. Doesn’t give the best rates on the markets
  3. Doesn’t take any additional commissions

We can improve the user experience and increase fees in favor of DAO at the same time and not have to change anything in pool fees, or we can combine the two and see what happens.

I suggest adding a CowSwap / ODOS / OKX DEX widget to the swap page with a small 0.05-0.1% commission. These widgets allow you to do this in the settings.

For example:

  • Safe Wallet takes Safe App License Fee (0.1%) for swap widget
  • Uniswap takes 0.25% UI fee
  • MetaMask takes 1% interface swap fee
  • Rabby takes 0.1% interface swap fee

This way the user will be able to get better exchange rates, maybe even better than on Curve directly. The current Curve direct exchange widget can also be left on, allowing the user to choose the best rate. The interests of all parties will be taken into account and everyone will benefit from this integration.

An additional convenience that users suggested when collecting feedback in Telegram: adding such a widget to the page adding liquidity to Curve pools. This is a Zap In feature. The user adds any token to any pool, and the exchange widget itself changes to the desired token, which will give the largest number of LP tokens at the output. You can also charge a small commission for this. I assume that any service for the benefit and convenience of the user will have a positive feedback. For those who do not want to use convenience, there will always be a standard method without additional commissions.

What do you think?

1 Like

Just today I was thinking that other projects have significantly larger development budgets than Curve. When you consider it, that 10% will definitely pay off. And if development is underfunded, veCRV holders will surely lose out over time.

I support the proposal. The second option seems more appropriate because it will further motivate the DAO to enhance all aspects of CURVE, and since the DAO’s yield directly depends on its performance, this approach will create a self-reinforcing cycle.

2 Likes

I really prefer option 2 since it diversifies the revenue generation. Option 1 needs too much manual tweaking in the feature (and seems slightly more complex) hence making it more expensive to develop/maintain. And the laid out points make sense, the protocol should also accrue some of the fees for development!

@hell0men
I like the idea of integration a swap widget, but on the other hand how many people really use the curve UI for swaps? I remember there was some data published on this about a year ago.
But I feel like the DAO should first integrate a revenue stream from the core product itself. So option 2 seems a great first step!

1 Like

Somebody use it because we see sandwich alerts for big stable swaps in Curve monitor bot :slight_smile:

I think these are good ideas that we should definitely consider in addition to the current initiative. Trading volume coming from the UI is proportionally low (about 10% of all DEX volume) but still significant enough that a UI fee would generate good revenue. Taking fees on zaps (for leverage) for instance has also been considered.
Suggestions for ways to generate more revenue are welcome and can be submitted in a separate forum thread or on tg/discord, but I’d rather keep the discussion focused on the current proposal.

the way Curve governance is set up with permalocks which forfeit governance to external orgs exposes a treasury to raids. This is largely negated as nothing to raid, but a significant amount of incentives are already directed to propping up these external orgs non governing wrappers.

better to do 2, but lock as veCRV to limit the impact of raids, and ensure that external orgs are incentivized to grow veCRV revenue to increase the value they gain access to from treasury.

even if only 10% use Curve UI for swaps, still makes sense to have MEV resistant options in UI, to attract more usage of Curve’s frontend, and grow stronger relationships with traders

I don’t really understand this, what external orgs are raiding the protocol?
Some liquid wrappers have voting power but for instance with Convex, their voting follows the votes of vlCVX voters, who are ultimately Curve stakeholders as their CVX position depends on Curve being successful.

There are also a number of drawbacks to the idea of using veCRV to fund the DAO:

  • There is not enough CRV in treasury to reach a level where yield would cover current expenses so it’s in effect impractical
  • The veCRV position has to be owned by someone, so you are transferring control away from the DAO over to a single organization and giving them rent in perpetuity. This is not desirable as
    1. No one should own the DAO treasury but the DAO
    2. Giving anyone perpetual yield without a clawback mechanism encourages rent seeking behavior. Implementing a clawback mechanism for a locked position is technically possible but impractical vs the current solutions.
  • There is no control/flexibility over how much money flows to the treasury. Say you lock enough CRV to capture 10% of veCRV yield. This gives us ~$3m per year currently. If revenue increases to $200m, the treasury gets $20m. With the current solution, we could reduce the treasury cut to increase yield for stakers. This is not possible with a fixed locked allocation. Likewise if revenue decreases and the treasury cut needs to be increased.

Sidebar

really not intending to throw shade at any protocol.
My intent is to explore the state of exposure, the side effects, and the risks they pose in the context of amassing the treasury from a mechanism point of view.
Hindsight 20/20 kinda stuff more than any view on current trajectory of any protocol

Boost as a Service

Some liquid wrappers have voting power but for instance with Convex, their voting follows the votes of vlCVX voters, who are ultimately Curve stakeholders as their CVX position depends on Curve being successful.

I don’t have exact numbers, but for arguments sake, lets assume Convex holds a minority of cvxCRV relative to users. Likewise for Yearn relative to yCRV holders.

In both cases,

  • the Users holding Liquid veCRV Tokens (LVTs) are exposed to CRV price

    • The DAO directly holds relatively minimal veCRV
  • the DAO earns profit off of selling the boost of these users.

    • this revenue stream has diminishing returns over time as inflation reduces
  • the LVTs can can never leave with their veCRV

    • there is 0 risk to DAO of losing existing deposits.
    • the LVTs hold no governance rights in either system
  • the DAO passes on veCRV revenue to the LVTs

    • The DAO is upgradeable which can change this arrangement
    • LVT holders have no negotiating power in this arrangement
  • The DAO has no formal obligation to incentivize liquidity of its LVTs

    • While currently incentivized, this is subject to change
    • At present CRV issuance is more heavily directed at incentives for LVT/CRV pairs than there is directed towards supporting CRV/ETH or CRV/USD,
      • demonstrating a natural tendency to favor the most direct exposure, rather than underlying exposure
  • The DAO has diversified their dependencies to include other protocols.

    • Largely the same deal as with Curve
    • Largely provides option to reduce relative Curve exposure

At least in the case of vlCVX holders, the only yield they earn is from bribes.
These voters, hold no direct exposure to CRV, nor its revenue.

How this relates to Treasury

Treasury raids are the primary risk to DAO’s which hold assets.

Convex currently pays for cvxCRV incentives via non formal bribes.
They could use treasury to pay for these bribes which benefit cvxCRV but not the broader Curve ecosystem.

They can use the savings to focus on growing non Curve ecosystem exposure to reduce their reliance on Curve Boost As Service Revenue.

As Incentives reduce, the benefits of incentivizing cvxCRV reduce. Likely take a cut of cvxCRV revenue if not all of it to incentivize deposits (cvxCRV holders rekt and can’t truly exit). Where else can vlCVX use their influence to benefit their ecosystem? By tapping the treasury.

Using Curve to Fund DAO

There is not enough CRV in treasury to reach a level where yield would cover current expenses so it’s in effect impractical

Agree. Makes sense for them to drive a share of revenue to the Treasury.

The veCRV position has to be owned by someone, so you are transferring control away from the DAO over to a single organization and giving them rent in perpetuity. This is not desirable as

  1. No one should own the DAO treasury but the DAO
  2. Giving anyone perpetual yield without a clawback mechanism encourages rent seeking behavior. Implementing a clawback mechanism for a locked position is technically possible but impractical vs the current solutions.
  1. The position can be a whitelisted gnosis safe set to be governed by veCRV.
  2. DAO held assets that cannot be spent generate revenue. This revenue stream can be directly governed by the DAO. If the Team does not perform, the DAO could direct the revenue somewhere else. Using veCRV revenue limits runway distributed at any given time, which prevents funding very long epochs.

There is no control/flexibility over how much money flows to the treasury. Say you lock enough CRV to capture 10% of veCRV yield. This gives us ~$3m per year currently. If revenue increases to $200m, the treasury gets $20m. With the current solution, we could reduce the treasury cut to increase yield for stakers. This is not possible with a fixed locked allocation. Likewise if revenue decreases and the treasury cut needs to be increased.

Not super clear about intent here. I may be misinterpreting.

I believe you are suggesting that if revenue of Curve generates goes up, the Treasury earns more funds than in needs

  1. in the case of veCRV denominated Treasury (as I suggested), the Team gets it all.
  2. if the case of other asset denominated Treasury (as you suggested), we can reduce the cut of yield such that stakers earn more.

But in both veCRV and other Denoms approach, the treasury growing by your suggested point

  1. Redirect 10% of veCRV fees to the community fund

This rate captured for the Treasury can be adjusted regardless of denomination all the same.

So maybe more focused on the Treasury is growing w/ yield sourced from its principle at a faster rate than necessary, but I don’t really see a problem with Treasury holdings grow fast. Holding scrvUSD instead would hold similar risk.

Can always set specific funding amounts for team while treasury grows. If really ridiculously large, could stream excess revenue to veCRV rewards contract to beef up veCRV user rewards, or buy ownership of Convex/Yearn/StakeDAO to expand to other revenue sources in the vertical, but that feels like a good future problem and less related to current discussion.

At least in the case of vlCVX holders, the only yield they earn is from bribes.
These voters, hold no direct exposure to CRV, nor its revenue.

Bribes are a direct function of CRV price since they pay for emissions. If CRV price goes down so does bribe value and vlCVX yield. vlCVX also earns a share of platform fees which are 90+% coming from Curve. The whole protocol is dependent on Curve, so I don’t see how they would be less aligned than direct veCRV lockers (not many of those left anyways) and history shows they are not.

In any case, the risk you are describing, while possible, is not specific to this proposal. If they can force a treasury-raiding proposal to pass (after there is a treasury), they can also force a proposal to redirect all revenue to cvxCRV holders (even if there’s no treasury). In each case, that’d kill both protocols

  1. The position can be a whitelisted gnosis safe set to be governed by veCRV.
  2. DAO held assets that cannot be spent generate revenue. This revenue stream can be directly governed by the DAO. If the Team does not perform, the DAO could direct the revenue somewhere else. Using veCRV revenue limits runway distributed at any given time, which prevents funding very long epochs.

Well the fundamental problem with the locking option is that there is not enough CRV in the DAO coffers to make it a viable option. So there really is no point discussing it. Furthermore handling a DAO owned safe as you suggest adds complexity when we already have a contract meant to be used by the DAO to allocate funds to contributors with vesting options (the community fund contract).

Can always set specific funding amounts for team while treasury grows. If really ridiculously large, could stream excess revenue to veCRV rewards contract to beef up veCRV user rewards, or buy ownership of Convex/Yearn/StakeDAO to expand to other revenue sources in the vertical, but that feels like a good future problem and less related to current discussion.

Yes the issue is that with veCRV it’s much harder to control how much money you are getting for the treasury. Both when there is too much of it, but also when there is too little (if the dev team punctually needs more revenue to pay for an audit, where are we going to find the CRV we already don’t have to lock and get more yield?). With a fee cut, all you need is a proposal to adjust the size of the cut.

the point is that locked veCRV is more secure than a generalized treasury of liquid assets as the risk limits the exposure of a raid to the revenue stream but not the principle.

The whole protocol is dependent on Curve, so I don’t see how they would be less aligned than direct veCRV lockers (not many of those left anyways) and history shows they are not.

As I had mentioned, history shows they prefer to spend incentives supporting their wrappers peg than actually supporting the price of CRV, which demonstrates that alignment isn’t always prioritizing Curve

I truly feel like we are talking through each other here. No one has suggested taking existing held CRV, locking it, and that being that. The veCRV discussed comes from the very same source of the fee cut you described in your proposal 2. Its just holding the treasury in a different denomination.

where are we going to find the CRV we already don’t have to lock and get more yield?). With a fee cut, all you need is a proposal to adjust the size of the cut.

You can literally increase your fee cut if necessary if you need to spend liquid funds here too.
Hell you can have a fee cut 3 ways if its really that problematic for you.

Entity | Weight
veCRV Holders | X%
Treasury | Y%
Immediate Spend | Z%

I truly feel like we are talking through each other here. No one has suggested taking existing held CRV, locking it, and that being that. The veCRV discussed comes from the very same source of the fee cut you described in your proposal 2. Its just holding the treasury in a different denomination.

Ah I indeed had not understood this. This is still unpractical, at the current level of fee cut, the revenue accrued by the Treasury would barely cover dev and audit expenses. Locking it all would mean no liquidity to pay for expenses. And the yield from the locked position would still be insufficient to cover expenses. Whatever revenue is taken has to cover a large portion of expenses. And the treasury has to keep this amount in a sufficiently liquid form so that it can be sold to pay for expenses when needed.

If there is some surplus after covering expenses we should certainly look for way to invest it and get yield. Buying CRV to lock is certainly an option. However, as highlighted in the original post, this discussion is not meant to turn into a debate on treasury management. Happy to have that discussion later, once the treasury is established.