Create a crvUSD credit line to Yield Basis

Summary

Yield Basis removes impermanent loss in Curve cryptopools by automatically keeping constant leverage via a special-purpose AMM.

For operation, Yield Basis needs a credit line (implemented as a pre-mint allocation) of crvUSD, similarly to how crvUSD mint markets and PegKeepers operate. I propose to start from 60M crvUSD credit limit which will be enough to safely create 3 pools - for WBTC, cbBTC and tBTC capped for deposits up to $10M worth of BTC each. This is a comfortable minimum to have pools operating well on Ethereum mainnet.

The proposal below shows that:

  • Yield Basis does not require any supply sinks for crvUSD (it is a supply sink for itself);
  • Yield Basis returns value equal to 35%-65% of what veYB is getting back to Curve / veCRV;
  • An efficient use for YB tokens granted to Curve is proposed (vote incentives for crvUSD stablecoin pools).

Borrowing, supply sinks and scalability

In typical borrow markets (such as crvUSD mint markets), a user who borrows any amount of debt d will sell it for one or other purpose (for example, to sell it for redeemable stablecoins, or for more collateral if they use borrowing to create a leveraged position). This creates a price pressure -d on crvUSD which gets absorbed by crvUSD pools and PegKeepers but increases borrow rate. In order to zero out this effect on crvUSD, part of the borrow rate is given to Savings crvUSD, or incentives are given to create some other supply sink for crvUSD, hopefully to absorb +d amount of crvUSD. The latter is not too easy, so this presents a fundamental challenge of scaling crvUSD (or any other CDP), not being able to satisfy the demand for loans without creating a corresponding demand to HODL the stablecoin.

When Yield Basis borrows crvUSD, the supply sink problem is solved. Curve cryptoswap AMM consists of x amount of stablecoin and y amount of cryptocurrency (a bitcoin wrapper). Yield Basis AMM borrows d amount of debt which on average is having the size of half TVL of the pool: if price of Bitcoin is p, time-averaged values for a pool with constant TVL \left<x\right>_t=\left<py\right>_t=\left<d\right>_t.

This means that Yield Basis simultaneously borrows and makes a supply sink for the same amount of crvUSD. Therefore, TVL and debt in Yield Basis can scale up to any size without affecting crvUSD peg negatively.

Borrow rate usage

In Yield Basis, 100% of borrow rates paid by LPs are directed to refill the budget used for rebalances in Curve cryptopools. In addition, 50% of trading fees in this pool, as usually, also refill the same budget.

The other 50% of the fees generated in the pool are the revenue which gets split between Yield Basis (veYB holders) and liquidity providers (who hold liquidity as ybBTC tokens). So, 100% of the borrowing fees are going back to support the pool’s liquidity. So Curve ecosystem is not getting value from this stream. Instead, it gets value via different ways: crvUSD<->redeemableUSD exchanges, and having a part of YB token allocated to Curve ecosystem.

crvUSD stableswap trading fees

Yield Basis earns fees from BTC wrapper trades, for example BTC<->crvUSD. However, crvUSD is rarely the final stablecoin users (mostly arbitrage traders) need. Typical arbitrage paths can look like:

wBTC->crvUSD->USDT or USDT->crvUSD->WBTC.

Therefore, the same volume as happening in wBTC<->crvUSD pool (which has no admin fee) also occurs in crvUSD<->USDT and similar pools. Those trading volumes contribute to system revenues as:

  • 50% of stablecoin pool fees go to veCRV holders;
  • the other 50% of stablecoin pool fees go to LPs of those pools.
  • That makes pools more attractive for deposits and, therefore, as a supply sink for crvUSD, which eventually results into more mints of crvUSD which get revenues to veCRV holders.

Therefore, it is fair to say that all the fees which get charged by crvUSD stableswap pools will eventually end up as revenues for veCRV holders, one or other way.

Let’s calculate revenues which Curve will get from those. Let’s assume that fee of stablecoin pools is equal to what it is now (f_s=0.01\%=10^{-4}), and all the trading volumes happening in cryptopools related to Yield Basis will also create the same trading volumes in crvUSD stablecoin pools.

Stablecoin pool which had volume V over time t earning rate per TVL can be found as:
r_s=\frac{f_s V}{t\cdot TVL_{yb}}=2 f_s \frac{V}{t\cdot TVL_{cryptopool}}.

For the sake of an estimate, let’s assume that the ratio of this rate to YB fundamental earnings rate (APR) is constant:
R_s=\frac{r_s}{r_{YB}}=\text{const}.

We can find this ratio from simulations over historic data from 2023 till July 2025. Growth of deposits based on these simulations is provided:

From these simulations:

  • Total time simulated: 905 days;
  • V/(t\cdot TVL_{cryptopool})=23.57~\text{year}^{-1};
  • r_{yb}=14.87\% - average fundamental APR in Yield Basis pool;
  • r_s=0.47\%;
  • R_s=0.03172 - fraction of stableswap returns vs returns of Yield Basis pools before any admin fee mechanics is applied.

Yield Basis as a system applies admin fee which ranges between 10% and 100% to r_{yb} (10% is when nothing is staked to earn YB token). So earnings for Curve from crvUSD pools can reach up to 31.7% of what Yield Basis earns (that is if nothing is staked).

YB allocation for Curve

In order to get more incentives for Curve ecosystem as well as to pay a fee for having Curve technology (cryptopools) powering its core, Yield Basis makes an allocation equal to 25% of YB which Yield Basis liquidity providers are getting to Curve. One can count that as inflation, so Curve ecosystem will always get 20% of total YB inflation (let’s call this number i_c). That already allows to estimate value which Curve ecosystem will be routinely getting from Yield Basis.

Total revenues for Curve ecosystem

Let’s calculate how much Curve is getting from inflation as well as the total value which one gets for Curve. For that, we will need to have a loosely set parameter k which has a meaning of ratio of YB token inflation to the revenues which the Yield Basis system is getting. In DeFi projects which generate and distribute value derived from their operation this parameter is currently around k=2 while sustainable operation would assume k=1. We’ll calculate revenues generated for Curve for k ranging from 0.5 to 3.

YB inflation is dynamic and depends on fraction staked s (which can range from 0 to 1):
I=I_0 \sqrt s;

Admin fee in Yield Basis is also dynamic:
f_a = 1 - (1 - f_0)\sqrt{1 - s},
where f_0=10\% is minimal admin fee (which is reached when s=0).

Return rate which LPs in Yield Basis are getting earns from what is left after charging admin fee, but only gets distributed to those who did not stake (1-s of all):
r_{unstaked} = \frac{(1-f_a)\cdot r_{yb} \cdot TVL_{yb}}{1-s}.

As we hypothesized, the value of emissions should be k times larger than the admin fee which gets into pockets of veYB holders. Let’s also normalize it to the fraction of depositors who staked (s).:
r_{staked}=\frac{k\cdot TVL_{yb}\cdot r_{yb}\cdot f_a}{s}.

In efficient markets, both staked and unstaked rates should equalize, e.g. r_{unstaked}=r_{staked}. This leads to:
\frac{1-f_a}{1-s}=\frac{kf_a}{s}.

When we substituting f_a, we arrive at:
k=\frac{s(1-f_0)}{\sqrt{1-s}\left(1 - \left(1 - f_0 \right)\sqrt{1-s} \right)}.

We solve it for s graphically and calculate rate of returns which Curve is getting from emissions normalized to what veYB is getting, summarized in the table:

k Optimal staked s crvUSD stableswap returns R_s YB inflation returns Total Curve returns from Yield Basis
0 0% 31.7% 0% 31.7%
0.5 7.1% 23.9% 10% 33.9%
1 19% 16.7% 20% 36.7%
1.5 38% 10.9% 30% 40.1%
2 60.7% 7.28% 40% 47.3%
2.5 76% 5.67% 50% 55.7%
3 84.5% 4.91% 60% 64.9%

In this table, k=2 is typical for revenue-distributing projects, k=1 is sustainability (e.g. when inflation = distributed revenues) and k=0 is a corner case of YB token being valued at 0.

So, Curve is realistically getting total value somewhere from 35% to 65% of what veYB holders are getting from fees.

Efficient use of YB tokens in Curve

Inflation-like stream of YB tokens given to Curve can be used in multiple ways (initially controlled by veCRV). I propose to use this stream to incentivize votes for stablecoin pools like crvUSD/USDC, crvUSD/USDT, crvUSD/pyUSD, crvUSD/USDf, crvUSD/frxUSD and alike. This will improve crvUSD supply sinks (which will eventuall create more revenue via crvUSD minting), increase crvUSD liquidity and provide revenues to veCRV and vlCVX as vote incentives.

The emissions are to be controlled by veCRV holders initially although they can grant access to distribute those to anything (smart contract, multisig etc) in a later proposal. The suggestion to use YB tokens for crvUSD stableswap vote incentives is not a part of this particular proposal but a suggestion for next proposals.

12 Likes

Is there a way to do this without minting crvUSD out of thin air? The beauty of crvUSD is that’s backed by real assets. This proposal damages the crvUSD trust. And I’m not the only one who feels this way.

launch a pre-deposit crvUSD vault is better than pre-minting

2 Likes

as the founder and creator of curve, i think nobody else, in this scenario especially, deserves more support than you, however, it’s important here to consider the implications of a ‘free mint’ vs crafting a structure that’s sustainable with a model that relies entirely on free-market economics that’s healthier on all timeframes. maybe it grows slower at first? maybe it grows insanely fast? maybe you start it with a lower / tighter cap and increase it steadily? maybe demand is unrelenting as the model proves consistent and secure?

The beauty of crvUSD is that’s backed by real assets.

The crvUSD would be backed by BTC when utilized in the pool though, so not a concern? And given that it isn’t sold, so doesn’t affect the peg, in a way the pre-mint is just a borrowing cap.

Also in the same way, peg keepers have pre-allocated crvUSD to support the peg, which we don’t count as part of the circulating supply.


If Yield Basis can only scale when it doesn’t have to pay the borrow rate, then don’t see an issue supporting this. Especially as the crvUSD for Yield Basis doesn’t require a supply sink, it’s self-contained.

The benefits of increasing liquidity for crvUSD has tons of benefits for the Curve ecosystem on the other hand, which is why this is so interesting, it will increase demand for crvUSD itself and better support Llamalend. The trading fees and YB incentives are also quite nice for the Curve DAO.

Interested in the crvUSD<>USDstablecoin pools, how many would the ecosystem actually need? And would a metapool with the strategic reserve be interesting, or since these will use a lot of incentives, cleaner to do standard pools?

1 Like

Hi Mich,

Thank you for this proposal. I really want to see Yield Basis do well, and hope it can increase demand and supply for crvUSD, and increase veCRV revenue.

However, I believe a key assumption in your analysis is that every BTC → crvUSD swap will have a corresponding crvUSD → USDT (or USDC) swap. I’m not sure that’s fair to make and would welcome your thoughts on a few scenarios:

  1. A significant portion of this volume will likely come from arbitrage bots. Why wouldn’t they simply hold small amounts of crvUSD (e.g., 2-3 bots holding ~$1M each) and rebalance their inventory only when required, rather than completing a full crvUSD → USDT swap each time? This seems likely when the extra swap costs precious gas, and crvUSD peg is super strong.
  2. Currently, the crvUSD/USDT and similar pools have fees around 0.01%. We can sustain this relatively high fee because there is limited competition. If demand for this liquidity increases, so will competition. Why wouldn’t a protocol like Ekubo offer a highly concentrated crvUSD/USDT pool with a lower fee? This could capture a large share of the volume and revenue without significantly increasing crvUSD supply (Their pool would most likely be $1-5M TVL max). (For reference, their USDC/USDT pool has a 0.0005% fee, with only $11M TVL, and handles over $500M in daily volume, generating only $2-3k in fees).

In either of these scenarios, Curve’s own crvUSD volumes would certainly be higher, but likely not as high as the simulations suggest.

My other major concern is the protocol risk. What happens if YB is hacked, and is there an insurance or mitigation plan? This unbacked crvUSD mint would represent a significant counterparty risk for the DAO. We only need to look at the Resupply incident: it was audited, yet a vulnerability was missed. While it was unfortunately hacked, crvUSD’s peg was unaffected because it was their own isolated stablecoin. In contrast, if YB were hacked, Curve would be left with the bad debt, the crvUSD peg would be negatively affected, and trust in our stablecoin would erode.

I guess we have to decide if that risk is worth 20% of YB perpetual inflation?

6 Likes

Hi, Andrew from Coinbase here!

I’m very excited for the Yield Basis protocol and to see cbBTC proposed as an initial pool asset. :slightly_smiling_face:

If helpful, I’m happy to answer any specific questions the community may have as it relates to cbBTC. I’ve also included a brief summary of cbBTC below for your convenience.

cbBTC Summary

cbBTC is a wrapped token backed 1:1 by BTC held by Coinbase.

Docs:
Project - https://www.coinbase.com/cbbtc
Proof-of-Reserves - https://www.coinbase.com/cbbtc/proof-of-reserves
Other resources: Whitepaper | Help page

Details:

  • cbBTC is fungible 1:1 with a dedicated reserve of BTC held at Coinbase.

  • Minting - When a user initiates a withdrawal of BTC held in their Coinbase account to a specified destination address / wallet, an equivalent amount of cbBTC is minted on the specified network and sent to the user’s address / wallet

  • Burning - When cbBTC is deposited to a user-specific Coinbase address, the cbBTC is burned and the corresponding amount of BTC is released from Coinbase’s reserve and assigned to the user’s account.

  • There are currently no burn or mint fees on cbBTC

1 Like

hard agree. Pre-deposit vault with a cap provides many advantages.

  1. it’s backed by real assets
  2. it’s iterative. You can adjust and provide changes as time goes by
  3. it’s also a safer approach security speaking.

My question @michwill is : what’s your rationale of a pre-mint crvUSD? Is there any advantage that alternatives can not provide?

I believe there to be a misunderstanding, crvUSD is fully backed. The $60M acts as a credit line that’s only drawn when BTC deposits arrive. I like how @Llamaste referenced how it’s like PegKeepers, they too have pre-allocated crvUSD.

We’ll have deposit caps of $10M for each pool (wBTC, cbBTC and tBTC) but we need more to ensures that when the price of BTC increases the AMM has the necessary crvUSD to maintain constant 2x leverage.

On the security side of things, we do take it very serious as we did have 6 independent auditors take a look at the codebase with now also a competition running with Sherlock. And when YB wants to expand the allocation, it requires explicit Curve DAO governance approval.

6 Likes

Please explain how holders of cbBTC are treated in a a bankruptcy of Coinbase. Specifically, are these assets issued in a bankruptcy remote SPV? have you confirmed with written opinion of counsel that cbBTC holders will be senior creditors entitled to BTC backing?

Very excited about Yield Basis and the potential for a highly mutually beneficial relationship with Curve. I’m broadly supportive of the direction and would like to offer two constructive adjustments that address concerns raised while helping to improve alignment.

1) Limit Risk: Phased Growth

The proposal above asks to pre-mint 60M crvUSD to spin up three BTC pools (WBTC, cbBTC, tBTC). This amount is too high for day one. Let’s de-risk with clear, time-boxed phases.

Proposal: Introduce a phased approach on the growth of the crvUSD credit line. Each phase having a ~1 month duration and requiring a Curve DAO governance proposal:

  • Phase 1: $10M crvUSD total
  • Phase 2: $20M crvUSD total
  • Phase 3: $60M crvUSD total

YB is responsible for determining when individual collaterals are introduced and how to manage the allocated credit line.

This staggers the scaling while limiting the risk to Curve as YB contracts grow battle-tested. Slow scaling also allows for a less painful migration if determined to be necessary.

At each phase, Curve DAO should closely monitor any affects on the crvUSD peg and crvUSD trade volumes being routed through Curve stable<>stable pools versus competitor pools.

2) Improve Terms: Higher YB allocation to Curve

As the proposal is written, Curve’s upside is primarily trading fees in stableswap paths plus a recurring YB allocation sized such that Curve receives ~20% of total YB inflation.

Two notes:

  • Because no interest revenue is directed to Curve, and doing so may have negative effects on the system, YB emissions are a key tool to compensate Curve for the crvUSD credit line.
  • As Saint Rat flagged above, the fee-flow assumption (every BTC↔crvUSD swap also triggers a crvUSD↔stable swap on Curve) is optimistic and should not be relied upon given the user incentive to avoid extra hops and how competitive the DEX landscape has become.

Proposal: increase Curve’s share from 20% → 35% of total YB inflation (i.e., redirect an additional 15% of emissions otherwise going to stakers).

With this additional YB, Curve can elect to:

  • Lock the incremental share in veYB, or
  • Direct it to vote incentives for crvUSD stable pools.

Either way, it tightens alignment and fairly compensates the DAO for the crvUSD credit line.

—

Happy to work together and iterate on these ideas to make the proposal a positive fit for all sides.

10 Likes

These are probably the most reasonable and level-headed suggestions for the proposal I have seen yet. Thanks for the excellent ideas and the thoughtful, sophisticated level of discourse, @wavey0x.

1 Like

This is great. Thank you for taking the time to put this together. These adjustments resonate with many of us, and we truly appreciate your voice in this matter.

Mostly agree with the ideas here, but I think given that YB will need further lines of credit (beyond even the 60m), it would be fair to ask that they allocate 35% for all lending needs, and that Curve initially gets a much smaller %.

This way, both Curve and Yield Basis have opportunities to evaluate and negotiate increases fairly, rather than YB committing to 35% without future guarantees of additional lines of credit.

1 Like

I don’t believe phase rollouts help meaningfully. A phased rollout is to contain risk, but any breach of a protocol, even if contained, is catastrophic to the brand; existentially. The reality for DeFi protocols is they either work or they don’t, there’s no in between.

2 Likes

Agreed. I think this 60M initial credit line is essentially the same as a phased approach. (The other phases just weren’t outlined in the proposal.)

You don’t want to slow growth too much while you deliberate each phase.

I see it like this:

Ramp up Phase: 60M credit line with interest paid in YB token emissions.

  • Risks are smart contract and bad debt. 6 audits with an ongoing bug bounty feels acceptable for this risk.
  • Require at least a month live before more credit can be extended.

Growth Phase: After ramp up phase another proposal can be submitted to create a floating credit line with a cap (i.e 1B). This ensures the protocol can grow without needing proposals for incremental credit line increases.

YB will have to submit a new proposal for the growth phase. At this time, Curve will have a much better idea of the value driven to Curve and also have more ability to ask for more YB emissions to cover the interest payments. (It will be harder to move to a different stablecoin after the fact)

I would keep the 20% allocation the same for this proposal but ensure than an additional 15% can be directed to the Curve DAO if it makes sense in following proposals.

1 Like

YB Rollout Proposal

Here we offer a rollout proposal that seeks to balance YieldBasis’ desire to scale quickly with Curve’s requirement to manage its risk exposure responsibly.

The rollout is divided into three phases, with debt ceiling increases every two weeks upon meeting certain KPIs. In short, we suggest one month of scaling to the 60m requested in this proposal and one more month maintained at that level. After proving stable performance at full scale, the debt ceiling may continue to be expanded rapidly as YieldBasis pools reach capacity.


The scaling beyond Phase 3 in the chart above is hypothetical, being actually dictated according to the needs of YieldBasis protocol

Phase 0 – Governance & Safeguards (Pre-Launch)

The pre-launch phase includes several pre-requisites we recommend Curve require YieldBasis to fulfill before approving crvUSD minting.

  • Governance Clarification: Deploy DAO/access control configurations and clearly document privileged functions controlled by the factory and emergency admins, timelocks and other governance mechanics.
  • Guardian multisig: Include LlamaRisk signers with veto authority on YieldBasis governance proposals pertaining to crvUSD.
  • Bug bounty: Have a live bug bounty program active at launch.
  • Transparency: Ensure there is a dashboard tracking deployed vs unused credit, per-pool ceilings, and crvUSD in circulation.

Pending these items, LlamaRisk recommends Curve DAO to approve 20M crvUSD mint to YieldBasis as part of the initial rollout.

Phase 1 – Initial Pilot (Weeks 0–2)

Phase 1 proposes to onboard 2 of the 3 desired BTC pools with a reduced overall debt ceiling (20M total). The small scale for a short duration is intended to ensure YieldBasis is working as intended upon launch.

  • Pools onboarded:
    • WBTC/crvUSD pool with 10M crvUSD ceiling.
    • cbBTC/crvUSD pool with 10M crvUSD ceiling.
    • Total exposure: 20M crvUSD.
  • KPIs to monitor (1-week checkpoint):
    • Rebalancing budget solvent under live trades.
    • Routing: ≄50% of BTC–stable trades (e.g. WBTC → USDC) route through Curve stableswap pairs.

Upon successful observation of the initial pilot after one week in production, LlamaRisk recommends that Curve initiate a vote to approve the expansion of the debt ceiling.

Phase 2 – Early Scaling (Weeks 2–4)

Phase 2 proposes to add the third BTC pool and to expand the overall debt ceiling from 20M to 40M. The reduced scale for a short duration is intended to ensure YieldBasis is working as intended upon launch.

  • Pools onboarded:
    • tBTC/crvUSD pool with 10M crvUSD ceiling.
  • Debt ceiling expansion:
    • WBTC/crvUSD pool increase to 15M crvUSD ceiling.
    • cbBTC/crvUSD pool increase to 15M crvUSD ceiling.
  • Total exposure: 40M crvUSD.
  • KPIs: Maintain Phase 1 thresholds.

Upon successful observation of Phase 2 after one week in production, LlamaRisk recommends that Curve initiate a vote to approve the expansion of the debt ceiling.

Phase 3 – Full Scale (Weeks 4–8)

Phase 3 expands the debt ceiling of the onboarded pools to the full scale requested in the YieldBasis onboarding proposal (60m total). This phase allows us to observe how the system performs with the pools operating at the expected minimum viable size.

  • Debt ceiling expansion:
    • WBTC/crvUSD pool increase to 20M crvUSD ceiling.
    • cbBTC/crvUSD pool increase to 20M crvUSD ceiling.
    • tBTC/crvUSD pool increase to 20M crvUSD ceiling.
  • Total exposure: 60M crvUSD.
  • KPIs:
    • No crvUSD peg problems related to YieldBasis operations.
    • No critical security issues.
    • Curve total returns (crvUSD stableswap returns + YB emissions) are at least 35% of what veYB earn in fees.

Upon successful operation during phase 3, further increases to the debt ceiling can be initiated as the pools reach capacity. Consider expanding YieldBasis further with additional BTC assets (e.g. LBTC) and consider onboarding additional assets that may be suitable for use with YieldBasis (e.g. ETH). Consider deploying ybBTC as collateral on LlamaLend.

Beyond Phase 3 - Full Deployment (Week 8+)

Assuming strong performance and high demand for YieldBasis at this point, stakeholders may expect to double the debt ceiling every two weeks until end of year (requiring a cap increase proposal and Curve DAO vote at each stage). The debt ceiling by end of year may reach upwards of 960M crvUSD in particularly bullish circumstances. Actual expansion will depend on unknown factors, including BTC market performance, demand to LP on YieldBasis, and appetite to onboard and expand additional pools.

7 Likes

The biggest unknown here is not technical. Technically contracts are pretty solid safety-wise, and multiple audits agree with it.

The biggest unknown is performance in real world which also depends on gas proportion of the transactions. Due to this, fully evaluating this requires order of 60M allocation which, though, makes 3 x 10M max TVL pools and 30M crvUSD actually used.

I propose what you call “full rollout” (60M) to be done right away and done before the end of September. After that, can start scaling reaching 1B towards end of year (but looking at what the demand will be).

5 Likes

Hello from Threshold Network! We’re thrilled to see tBTC selected as one of the initial collaterals for YB and the decentralized, trust-minimized Bitcoin of choice.

Here is a quick summary of Threshold’s tBTC for anyone not already familiar.

Summary:

tBTC is a trust-minimized, 1:1 Bitcoin-backed asset that lets users bring real BTC onchain. Secured by threshold cryptography, tBTC makes Bitcoin programmable and usable across DeFi and capital markets while always remaining redeemable for native BTC.

  • Transparent and trust-minimized with every process verifiable onchain, no hidden custody, and no reliance on opaque intermediaries. Your Bitcoin remains yours.
  • No centralized keys or blacklist/freeze functions. Collateral is secured by decentralized threshold cryptography and the token cannot be arbitrarily blacklisted or frozen.
  • Lindy and batte-tested with five years of secure operations with no exploits or protocol compromises through multiple market cycles.
  • Permissionless minting and redemptions with no daily caps and no volume restrictions so you can scale your positions without artificial barriers.

If you want to learn more:

I second this! Scaling in is almost always a good idea

1 Like