AprScope

Aave V4 · Ethereum

CBBTC (Core)

Current APY

0.00%

base 0.00% · reward -

TVL

$8.10M

APY +0.00% 7d

Risk signals

0.00% - single asset

Overview

The Aave V4 CBBTC pool on Ethereum is a single-asset lending position where suppliers earn variable interest on BTC-backed borrowing tokens (CBBTC). The protocol generates yield by routing borrowing demand against pooled CBBTC liquidity and pays suppliers from the resulting interest spread. Total APY stands at 0.43%, with no reward component. Over the past week, the rate has decreased by 0.46% and over the last month it increased by 0.16%, placing the current rate below the 30-day mean of 0.57%. TVL is $1.4M; primary exposure is smart-contract risk due to the single-asset nature of the pool. Utilisation on this core lending pool reflects typical levels for Aave V4's protocol category.

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.

  • DefiLlama yield prediction

    DefiLlama's model classifies this pool's yield as "Stable/Up" with 76% confidence based on historical patterns.

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 Aave V4 CBBTC on Ethereum?

The current total APY is 0.00%.

What is the TVL of this pool?

Total value locked is $8.10M 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.