LlamaRisk’s pre-listing assessment of Babylon Labs’ proposed native Bitcoin lending market on Aave V4 identifies persistent WBTC payment dependencies for liquidation fees, borrower surplus, and debt repayment, even when keepers bypass Hub funding routes.
The risk assessor published its review on October 23, examining Babylon’s integration architecture for a native Bitcoin collateral market. Babylon’s native BTC collateral remains secured in a Bitcoin vault, with Aave recognizing it through restricted internal ERC-20 accounting rather than as a tradeable wrapped token.
Two liquidation pathways exist within the proposed structure. The Liquidation Liquidity Provider (LLP) route allows external liquidators to repay debt and receive WBTC payouts from Aave’s shared pool. A direct route enables authorized keepers with Bitcoin redemption rights to fund repayment without Hub payouts. However, LlamaRisk’s assessment reveals that keepers must transfer WBTC for debt repayment, the application fee (0.5% of liquidation bonus profit), and borrower fairness payments even when the application fee is set to zero.
The direct route requires keepers to finance a multi-day Bitcoin proof-and-challenge redemption process. Partial-position liquidations seize whole indivisible vaults. If debt clears before the vault value is consumed, the liquidator must compensate the borrower for remaining WBTC value at a liquidation-bonus discount.
Initial rollout parameters
Babylon’s proposed launch configuration includes a 300 BTC collateral cap, 10 allowlisted borrowers, and 50 vaults in the initial rollout. The application liquidation fee stands at 0.5% of liquidation bonus profit. LlamaRisk’s assessment recommends an initial Core Hub credit line of 100 WBTC for BTCVaultSwap, the settlement component.
Bitcoin loans under the proposed structure face a 4.7% price dip vulnerability threshold. Integration contracts remain undeployed on Ethereum mainnet as of the assessment date, with only Sepolia testnet deployments identified in Babylon’s contract directory as of October 25.
Architectural conflict
LlamaRisk’s assessment identifies a structural discrepancy between risk requirements and integration documentation. The assessment requires no remaining debt to withdraw every vault, while Babylon’s integration documentation describes removing vaults subject only to remaining position staying healthy. This gap creates ambiguity around vault withdrawal conditions under different liquidation scenarios.
Babylon did not respond publicly to LlamaRisk’s findings within the timeframe of the assessment. The current status of any Aave governance vote on the proposal remains unspecified.
