AprScope

Aave V3 · Ethereum

USCC (horizon-market)

Current APY

0.00%

base 0.00% · reward —

TVL

$121.51M

APY +0.00% 7d

Risk signals

0.00% single asset stablecoin

Overview

This is an Aave V3 lending pool on Ethereum where USCC serves as the underlying asset. The pool currently offers zero base APY with no reward APY component, and trend data shows zero percent change over both the 7-day and 30-day periods. The pool holds USD 121,510,339 in total value locked, with no recorded change over the past seven days. As a stablecoin pool, the primary risk exposure relates to depeg risk, where the USCC asset may lose its peg to its intended value.

Generated 2026-05-18 from the structured pool data on this page. No external claims, no hand-edited text. See methodology.

APY history

No history data yet.

TVL history

No history data yet.

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.

  • Depeg risk

    The pool is built on stablecoins. A depeg of any underlying asset would impact returns and principal.

  • 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 V3 USCC on Ethereum?

The current total APY is 0.00%.

What is the TVL of this pool?

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

Is there impermanent loss risk?

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

Is this a stablecoin pool?

Yes. The pool is built on stablecoins, so the primary risk is depeg events rather than directional price moves.

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-05-18. See methodology for how we collect and refresh this data.