Pendle · Ethereum
MHYPERBTC (For LP | Maturity 24SEPT2026)
Current APY
3.86%
base 3.86% · reward -
TVL
$2.15M
APY +1.75% 7d
Risk signals
Overview
The Pendle MHYPERBTC pool on Ethereum is an LP token for a yield-generating position with a maturity date of September 24, 2026. This protocol generates yield by splitting the underlying asset's time value into separate tokens.
Total APY stands at 2.99%, combining base yield and reward incentives. The 7-day trend shows a decline of 3.63% while no data is available for the 30-day trend; however, this current rate falls below the 30-day mean of 4.65%.
TVL currently stands at $3.17M with no reported change over the past seven days. The primary risk here involves smart-contract vulnerabilities given that it’s not a multi-asset or stablecoin pool. This liquidity depth supports efficient trading and swapping activities within the yield farming ecosystem.
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 3.86%; 30-day mean is 2.55%. Yields can change as TVL and incentive emissions change.
-
DefiLlama yield prediction
DefiLlama's model classifies this pool's yield as "Down" with 60% 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 Pendle MHYPERBTC on Ethereum?
The current total APY is 3.86%.
› What is the TVL of this pool?
Total value locked is $2.15M 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.