Overview
Risks
How much debt can be issued against LBTC as collateral across lending protocols.
Maximum possible exposure to LBTC
$167.43m
$6.63m (max additional borrows against LBTC) + $160.79m (bad debt if LBTC was hacked now)
Fluid
$3.21m at-risk exposure = $8,141.13 bad debt if hacked + $3.2m additional borrowable against LBTC
Aave V3
$77.34m at-risk exposure = $75.57m bad debt if hacked + $1.77m additional borrowable against LBTC
Euler V2
$889,293.35 at-risk exposure = $55,188.12 bad debt if hacked + $834,105.23 additional borrowable against LBTC
Morpho V1
$3.94m at-risk exposure = $3.11m bad debt if hacked + $831,893.09 additional borrowable against LBTC
SparkLend
$82.05m at-risk exposure = $82.05m bad debt if hacked + $0 additional borrowable against LBTC
Methodology and limitations
Showing collateral exposure for LBTC on onchain. Max Borrowable uses the backend's liquidity-bounded borrow-capacity metric (`collateralMaxBorrowUsdLiquidity`) for the maximum additional USD debt that can be issued against the asset right now. Bad Debt at $0 is the minimum known bad debt if the collateral asset price goes to zero; null rows are excluded from this total rather than treated as zero, so totals may remain lower bounds.
- These metrics describe lending exposure only and are not a full protocol risk rating.
- This view does not include multisigs, timelocks, audits, oracle incidents, listing discussions, curator reports, or protocol backstops.
- Chain-specific drilldown is exact only when the token resolves to a concrete chain:address.
- Bad debt at $0 is a lower bound when some contributing markets return null for zero-price bad debt; null rows are excluded instead of being treated as zero.
Show exposure details
Each row is one protocol-chain exposure for LBTC as collateral. Bad debt at $0 totals remain lower bounds when a row is marked partial.
Token Usage
An is required to view token usage.
Liquidations
An is required to view token liquidations.
Yields
Showing 10 of 33 pools
Borrow
Showing 10 of 53 routes