AprScope

YO Protocol · Ethereum

CBBTC (yoBTC)

Current APY

0.00%

base 0.00% · reward -

TVL

$1.41M

APY +0.00% 7d

Risk signals

0.00% - single asset

Overview

The YO Protocol CBBTC pool on Ethereum is a yield aggregator that generates returns from BTC deposits through various investment strategies within the protocol. Depositors hold liquid-staking receipts, known as CBBTC tokens, which represent their share of the underlying BTC assets.

Total APY stands at 5.5%, combining base and reward components exclusively. The 30-day trend shows a decline by 4.06%, while there is no data available for the 7-day trend. This current rate falls below the 30-day mean of 7.42%.

TVL in this pool stands at $2.31M, with no recent change reported over the past week. The primary risk exposure here is smart-contract risk due to the protocol's complex investment strategies. Given its role as a yield aggregator, liquidity depth within the pool supports stable operations despite market volatility.

Composed 2026-05-20 from the structured data above. See methodology for the full pipeline.

APY history
TVL history

Risk profile

  • Smart contract risk

    Funds are deposited into a smart contract. A bug or exploit in the contract could lead to total loss. Audits reduce, but do not eliminate, this risk. Check the protocol page for audit history.

  • Yield variability

    Yields can change as TVL and incentive emissions change. The current APY is not a guarantee.

These notes are derived from the pool's structured data, not editorial advice. See our methodology.

Similar pools

FAQ

What is the current APY for YO Protocol CBBTC on Ethereum?

The current total APY is 0.00%.

What is the TVL of this pool?

Total value locked is $1.41M as of the last data refresh.

Is there impermanent loss risk?

No. This pool is single-asset and has no impermanent loss exposure.

How often is this APY updated?

We refresh APY and TVL hourly from DefiLlama. Daily snapshots are stored to power the historical chart on this page.

Last updated 2026-07-06. See methodology for how we collect and refresh this data.