AprScope

Lagoon · Ethereum

T9CBBTC

Current APY

0.53%

base 0.53% · reward -

TVL

$10.39M

APY +0.53% 7d

Risk signals

0.53% - single asset

Overview

The Lagoon T9CBBTC pool on Ethereum is a single-asset position where users hold a token that represents exposure to Bitcoin through an on-chain capital allocator protocol. This protocol generates yield by dynamically allocating funds across various DeFi strategies.

Total APY stands at 2.81%, with no additional reward component. Over the past week, this rate has decreased by 0.57% and over the last month it increased by 0.23%, placing the current APY below the 30-day mean of 3.40%.

TVL in the pool is $13.67M with no reported change over the past week. The primary risk here is smart-contract exposure, given that this is not a multi-asset or stablecoin-focused pool.

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

    Current APY is 0.53%; 30-day mean is 0.91%. Yields can change as TVL and incentive emissions change.

  • DefiLlama yield prediction

    DefiLlama's model classifies this pool's yield as "Stable/Up" with 91% 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 Lagoon T9CBBTC on Ethereum?

The current total APY is 0.53%.

› What is the TVL of this pool?

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