SparkLend · Ethereum
WBTC
Current APY
0.00%
base 0.00% · reward —
TVL
$194.63M
APY +0.00% 7d
Risk signals
Overview
SparkLend WBTC on Ethereum is a lending pool featuring wrapped Bitcoin as the primary asset on the Ethereum blockchain. The pool currently displays a 0.0% total APY with no base or reward components; the 30-day average APY stands at 0.01%, declining 0.23% over the past month, while the 7-day change shows no movement. Total value locked in the pool reaches $194.6 million. The primary risk exposure is smart-contract risk inherent to the lending protocol.
Generated 2026-05-18 from the structured pool data on this page. No external claims, no hand-edited text. See methodology.
No history data yet.
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.
-
Yield variability
Current APY is 0.00%; 30-day mean is 0.00%. 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
same protocol
SparkLendWSTETH
Ethereum
same protocol
SparkLendUSDS
Ethereum
same protocol
SparkLendWETH
Ethereum
same chain + symbol
Aave V3WBTC
Ethereum
same chain + symbol
Compound V3WBTC
Ethereum
same chain + symbol
Morpho BlueWBTC
Ethereum
FAQ
› What is the current APY for SparkLend WBTC on Ethereum?
The current total APY is 0.00%.
› What is the TVL of this pool?
Total value locked is $194.63M 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-05-18. See methodology for how we collect and refresh this data.