Babylon’s proposed direct route can bypass pool funding, while fees, borrower surplus and WBTC-denominated debt retain separate payment requirements.
Babylon Labs’ proposed native Bitcoin lending market on Aave V4 would still need Wrapped Bitcoin (WBTC) for its direct-liquidation fallback whenever application fees or borrower compensation are due.
An operator with the vault’s Bitcoin redemption rights could bypass Aave’s shared lending pool yet still be unable to complete a liquidation if those WBTC payments cannot move.
The distinction comes from risk assessor LlamaRisk’s Oct. 23 pre-listing assessment. The direct route can avoid the funding constraint of running out of WBTC lending capacity by having an authorized keeper finance the liquidation itself. Required payment failures can affect both routes.
If the borrower owes WBTC, the keeper must transfer WBTC to repay the loan even when the application fee and borrower-surplus payment are zero.
The assessment said the integration contracts had not been deployed on Ethereum mainnet. Babylon’s contract directory, checked Oct. 25, identifies its published addresses as Sepolia testnet deployments.
A borrower’s native BTC would remain in a Bitcoin vault, and Aave would recognize that collateral through a restricted internal ERC-20 accounting record, which users cannot trade as a wrapped Bitcoin token.
Through the proposed Liquidation Liquidity Provider (LLP) route, an outside liquidator would repay the borrower’s debt and receive an immediate WBTC payout.
The settlement component, BTCVaultSwap (the Swap Spoke), would place the seized vault in escrow and draw the payout from Aave’s shared liquidity pool (the Hub).
Source link







