AprScope

Aave V4 · Ethereum

LBTC (Core)

Current APY

0.00%

base 0.00% · reward -

TVL

$720.0K

APY +0.00% 7d

Risk signals

0.00% - single asset

Overview

The Aave V4 LBTC pool on Ethereum is a single-asset lending position where suppliers earn variable interest on Bitcoin-backed token deposits. Aave routes borrowing demand against pooled LBTC liquidity and pays suppliers from the resulting interest spread. The pool competes with other multi-collateral BTC lending venues on Ethereum mainnet.

The total APY stands at 0%. Trend data is not available for this pool, so there are no recent changes to report.

TVL currently sits at $0. Given the lack of liquidity, any minor shifts in market sentiment could lead to significant fluctuations. The primary risk exposure here involves smart-contract vulnerabilities, as with most DeFi lending protocols. Aave's core lending mechanism ensures that supply-side rates adjust according to borrower demand, although this pool lacks active liquidity.

Composed 2026-05-23 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 Aave V4 LBTC on Ethereum?

The current total APY is 0.00%.

› What is the TVL of this pool?

Total value locked is $720.0K 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-10-04. See methodology for how we collect and refresh this data.