Skip to main content

Risk Disclaimer

Providing liquidity on YieldBasis and participating in leveraged liquidity provision carries inherent risks. Before depositing or engaging with the protocol, users must research and understand the risks involved. This document catalogues the primary risk categories.

Audits & documentation​

YieldBasis smart contracts have undergone multiple comprehensive security audits by reputable firms: Statemind, ChainSecurity, Quantstamp, MixBytes, Electisec, and Pashov. Additionally, a public security contest was hosted with Sherlock. All identified issues have been remediated. Audit reports are listed at Audits & Bug Bounties.

Audits play an important role in mitigating risk but do not eliminate it. Users should exercise caution regardless.

Technology risk​

Smart contract risk​

YieldBasis relies on self-executing smart contracts. While designed to be secure and reviewed by multiple independent firms, no audit eliminates all risk — vulnerabilities, bugs, or novel attack vectors could exist. Malicious actors exploiting such issues could cause loss of funds or other adverse outcomes. Users should conduct due diligence and review the smart contracts and audit reports before depositing.

  • Vyper 0.4.3 implementation throughout.
  • Core YB contracts are immutable — they cannot be upgraded.
  • Parameter updates (fees, allocations, gauge weights) go through the DAO.
  • A migration path exists from legacy to current markets via LTMigrator.vy.

Oracle risk and price-feed dependency​

YieldBasis uses a composite oracle to price LP tokens and maintain leverage:

  • Curve Cryptopool LP oracle — 2 × virtual_price × √price_scale × p_agg (see Oracle Design).
  • crvUSD price aggregator — samples from multiple major liquidity pools and takes an EMA.
  • Bound check — at Factory init and on aggregator updates (Factory.vy::set_agg), the crvUSD oracle price must fall within (0.90,0.90, 1.10) (exclusive on both ends). The aggregator setter reverts outside the band; routine deposit, withdraw, and exchange operations do not re-validate it.

The EMA dampens flash-loan manipulation: you cannot move price_scale within a single block enough to spoof the oracle. However, oracles are not infallible. In extreme market conditions, price feeds may experience latency, temporary unavailability, or genuine disagreement between the oracle and live market price. Such disruptions could impact the protocol's ability to maintain the target leverage ratio, result in unfavourable trade execution, or temporarily destabilise the system.

Leverage mechanism and rebalancing risk​

YieldBasis maintains a constant 2× compounding leverage via an arbitrage-driven rebalancing mechanism (see Compounding Leverage). LEVAMM posts quotes via its invariant; arbitrageurs trade against those quotes when they diverge from Cryptoswap spot, which simultaneously restores the leverage target.

This mechanism depends on economic incentives:

  • Normal conditions — arbs execute rebalancing trades for profit; the target 50% debt-to-value ratio is maintained continuously.
  • Extreme volatility / network congestion — rebalancing may be delayed. High gas costs can make small arb trades economically unviable, letting the leverage drift from its target for longer periods.
  • crvUSD depeg — if crvUSD deviates significantly from $1.00, the effective leverage ratio can temporarily deviate from the target even when arbs are active.

Self-correction via arbitrage is not instantaneous. It depends on market participants responding to economic incentives under prevailing gas and volatility conditions.

Spread fluctuations and withdrawal variability​

Users may observe that withdrawal amounts fluctuate between blocks. This is a consequence of the Cryptoswap-vs-LEVAMM gap (TRD) — LEVAMM's quote adjusts to the debt-to-value ratio, and Cryptoswap's live pool state shifts with trades. When the leverage drifts from 50%, the effective spread widens to incentivise rebalancing; as arbs respond, the spread narrows.

What this means for users:

  • The amount received on withdraw can vary between a pre-trade quote and execution, depending on other activity in the block.
  • During rapid price movement, spread adjustments are more pronounced and TRD can widen.
  • Always review transaction previews (preview_withdraw) and set a realistic min_assets parameter to protect against unfavourable execution.
  • TRD normally resolves within hours via arbitrage. See Temporary Redemption Discount.

Immutability and irreversibility of transactions​

Transactions on Ethereum and EVM-compatible chains are immutable and irreversible. Once confirmed on-chain, a transaction cannot be modified, reversed, or deleted. If funds are sent to a wrong address, signed for the wrong amount, or routed to a malicious contract, recovery is typically impossible. Verify transaction details, use trusted wallets, and double-check contract addresses against Contract Addresses before confirming.

Counterparty risk​

Access control​

YieldBasis smart contracts are intentionally immutable and noncustodial. They cannot be upgraded, and liquidity providers always retain control of their funds. This limits protective action in emergencies but strengthens user assurance over custody.

Protocol governance is handled by a DAO of veYB holders (see Proposals):

  • 1 veYB minimum to create a proposal.
  • 30% quorum (minimum participation of total veYB supply).
  • 55% support threshold.
  • 7-day voting window with linear decay after 50% of duration.

The DAO controls the implementation of new system contracts and parameter adjustments. Users considering deposit should be comfortable with decisions being made collectively by veYB holders.

Emergency procedures​

YieldBasis does not implement a traditional emergency-pause function or circuit breaker at the protocol level. This design prioritises user custody and access — liquidity providers can always exit, regardless of protocol state.

Caveats:

  • Market kill-switch — YB's emergency_admin can call set_killed on an AMM to block new deposits and normal withdrawals (LT.withdraw reverts with "We're dead. Use emergency_withdraw"). When a market is killed, emergency_withdraw remains available so users can always unwind — this path does not depend on oracle or AMM health. Use only when the standard path is unavailable; returns may be suboptimal.
  • Curve Emergency DAO — since YB markets are built on Curve Cryptoswap pools, the Curve Emergency DAO can pause the underlying Curve pool in extreme situations. This may affect swap functionality (including arbitrage-based rebalancing), but withdrawals from YieldBasis remain possible even if the underlying Curve pool is paused.

Users should understand the dependency: YB itself has no pause, but the upstream infrastructure it builds on does. Emergency safeguards at the Curve level could temporarily affect certain functions while preserving withdrawal capability.

Dependency on Curve Finance infrastructure​

YieldBasis is fundamentally built on top of Curve Finance:

  • Cryptoswap pools provide the underlying liquidity and LP token semantics.
  • crvUSD is the debt asset.
  • LP pricing and the refueling mechanism rely on Curve's infrastructure.

YieldBasis inherits both the benefits (battle-tested audits, years of production usage, mature oracle design) and the risks of this dependency. Changes to Curve pool parameters, upgrades to Curve contracts, or issues with Curve infrastructure could affect YieldBasis markets without direct control by YieldBasis governance. Any vulnerability, exploit, or failure in Curve contracts could directly impact YieldBasis users.

Economic risk​

Unstaked LPs​

  • PPS drag — if net rebalance losses (after the refueling subsidy from borrower interest) exceed trading-fee inflow over a sustained period, PPS grows more slowly or stagnates. Borrower interest itself does not directly drag PPS; the drag is the residual slippage cost donations do not cover. Recovery requires forward fees to outpace forward drag. See PPS vs Redemption Value.
  • TRD on withdrawal — normal, self-resolving via arbitrage; typically takes hour. See Temporary Redemption Discount.

Staked LPs​

  • Watermark drawdown — the main staked-specific exposure. If rebalance losses outrun fees (see Fee Mechanics), the staked side drops below ideal_staked. The parameter set is tuned to keep rolling 60-day APY positive, so drawdown is rare and the safety net rarely triggers; when it does, recovery is forward-fee-dependent and YB emissions are the compensation for the wait. See Watermark and Recovery.
  • Forfeited PPS growth — staked positions do not earn unstaked PPS growth. Their only economic return is YB emissions (valued at YB/USD). The opportunity cost versus staying unstaked is real.
  • YB price risk — YB emissions are the compensation for watermark exposure and forfeited PPS growth; if the YB token's market price is low relative to realised protocol yield, emissions under-compensate.
  • Gauge weight risk — emissions per gauge are allocated by veYB vote. If your market's gauge weight is low, emissions to stakers in that market are low.

Asset risk​

BTC and ETH wrapper token risk​

YieldBasis supports multiple wrapped BTC and ETH variants across its markets — cbBTC, WBTC, tBTC, WETH, etc. Each wrapped token represents the underlying asset held by a specific custodian or bridge mechanism, and each carries its own trust assumptions:

  • Wrapped BTC tokens are not native Bitcoin. They depend on the solvency and operational integrity of issuers or bridge protocols (custodian risk for cbBTC/WBTC; bridge risk for tBTC; etc.).
  • If a wrapped token loses its peg to the underlying (custodian insolvency, bridge exploit, regulatory action, technical failure), liquidity providers in the corresponding yb-LP market experience the full effect.
  • Markets are isolated from each other. A depeg in one wrapped variant does not directly affect LPs in other YB markets.

Carefully evaluate the trust model of the wrapper you choose before depositing.

crvUSD stability and peg risk​

YieldBasis borrows crvUSD through a dedicated collateralised debt position (CDP) line to achieve 2× leverage. The leverage mechanism assumes crvUSD trades near $1.00:

  • The oracle validates crvUSD price within (0.90,0.90, 1.10) (exclusive on both ends) when the aggregator is set; routine operations do not re-check the band.
  • Short-term crvUSD volatility inside the band can still affect effective leverage ratios and position values.
  • Significant depeg events (substantial under- or over-peg) would distort the protocol's effective leverage and the value of user positions.
  • Permanent depeg due to systemic issues with crvUSD collateral or redemption would cause losses proportional to the severity and direction of the depeg, as YB debt is denominated in crvUSD.

Market dynamics and liquidity risks​

  • Underlying volatility. The value of user positions is driven by the underlying asset (BTC, ETH). Cryptoassets are historically volatile — rapid and substantial price moves within short windows are normal. YB is designed to deliver 1:1 exposure to the underlying via 2× leverage with IL cancelled; you remain fully exposed to the underlying's price direction.
  • Flash crashes and rapid moves. Sudden market events can produce substantial gains or losses.
  • Rebalancing efficiency depends on liquidity. In thin liquidity or extreme stress, arb trades may be less efficient and the leverage target can drift for longer. Oracle-safety-band edges may also temporarily gate arb, extending drift.

Flash loan dependency​

YieldBasis's arb-based rebalancing uses flash loans to enable capital-efficient trades. VirtualPool.vy integrates with a flash lender (configured on Factory.flash) so arbitrageurs can rebalance without upfront capital.

  • If flash-loan infrastructure is unavailable or experiences technical issues, the protocol's ability to rebalance quickly is impaired.
  • If flash-loan fees rise significantly, rebalancing arbitrage becomes less profitable and the leverage target can drift further before arbs respond.
  • Flash-loan protocols have been reliable historically, but any disruption delays return to optimal leverage during volatile conditions.

Governance risk​

  • The DAO can alter critical parameters (admin fee floor, emission schedule, gauge approvals, factory allocations, stablecoin fraction for Hybrid Vaults, etc.) subject to the 30% quorum / 55% support thresholds.
  • veYB voting weight concentration at launch creates a vote-centralisation risk until distribution matures.
  • Emergency admin can kill individual markets (see above). This is a fast-path tool for broken oracles or insolvency that cannot wait for a full DAO vote.

Regulatory risk​

Standard DeFi regulatory uncertainty applies. Users are responsible for understanding the legal and tax status of yb-LP positions, veYB, and YB emissions in their jurisdiction.

Disclaimer​

The information provided within this document does not constitute financial, legal, or tax advice personalised to individual circumstances. It is for informational purposes only and should not be relied upon as a substitute for professional advice. The protocol is provided "as is" without warranties of any kind, and users engage with YieldBasis entirely at their own risk.

Users are strongly encouraged to seek advice from qualified professionals regarding financial, legal, and tax matters before engaging with YieldBasis. Past performance is not indicative of future results, and users may lose some or all of deposited capital. Only deposit funds you can afford to lose, and carefully consider your risk tolerance, financial situation, and investment objectives before participating in leveraged liquidity provision.