Joe V2.1 · Avalanche
WBTC.E-BTC.B
Current APY
0.00%
base 0.00% · reward -
TVL
$223.9K
APY -0.14% 7d
Risk signals
Overview
The Joe V2.1 WBTC.E-BTC.B pool on Avalanche is a multi-asset liquidity position that generates yield through automated market-making trades. This DeFi protocol facilitates swaps between wrapped Bitcoin (WBTC) and a synthetic BTC-backed token, earning fees from trading volume.
Total APY stands at 0.33%, with no additional reward component. The 7-day trend shows an increase of 0.045% while the 30-day trend is up by 0.2%. This current rate is above the 30-day mean of 3.73%.
TVL in this pool is $321,374 with no recent change data available. The primary risk here involves impermanent loss exposure due to the multi-asset nature of the liquidity provision. Depth and stability of trading volume are key factors influencing yield potential for liquidity providers.
Composed 2026-05-20 from the structured data above. See methodology for the full pipeline.
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.00%; 30-day mean is 2.50%. Yields can change as TVL and incentive emissions change.
-
DefiLlama yield prediction
DefiLlama's model classifies this pool's yield as "Stable/Up" with 59% 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 Joe V2.1 WBTC.E-BTC.B on Avalanche?
The current total APY is 0.00%.
› What is the TVL of this pool?
Total value locked is $223.9K 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.