Ember Protocol · Sui
TBTC (BTC Vault)
Current APY
2.38%
base 2.38% · reward -
TVL
$707.9K
APY -0.04% 7d
Risk signals
Overview
The Ember Protocol TBTC on Sui is a single-asset lending position where suppliers earn interest on Bitcoin-backed tokens (TBTC). The protocol generates yield by allocating TBTC across various DeFi opportunities, such as lending and staking.
Total APY stands at 2.35%, with no additional reward component. Over the past week, the rate has increased by 0.42%, but there is no trend data available for the last 30 days. The current APY exceeds the 30-day mean of 2.26%.
TVL currently sits at $1.06M with no reported change over the previous seven days. Primary exposure here is smart-contract risk due to the on-chain capital allocation strategy employed by Ember Protocol. This pool benefits from a relatively deep liquidity base, enhancing its operational stability.
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 2.38%; 30-day mean is 1.86%. Yields can change as TVL and incentive emissions change.
-
DefiLlama yield prediction
DefiLlama's model classifies this pool's yield as "Stable/Up" with 72% 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 Ember Protocol TBTC on Sui?
The current total APY is 2.38%.
› What is the TVL of this pool?
Total value locked is $707.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.