Aave Weighs Native Bitcoin Loans With WBTC Liquidations

Native Bitcoin collateral gets an Aave record

The proposed arrangement uses Babylon’s Trustless Bitcoin Vaults, or TBV. A depositor locks BTC in a Taproot output, a Bitcoin transaction output with programmed spending conditions, while Ethereum contracts track the collateral and loan.

Aave V4 accepts Ethereum-standard ERC-20 tokens, so an adapter would create a transfer-restricted accounting token for each activated vault’s BTC. It could move only among specified integration contracts, rather than circulate as a freely tradable Bitcoin wrapper.

That differs from Ledger’s four wrapped-Bitcoin loan markets, where users pledge cbBTC or wBTC on Ethereum. Both approaches seek borrowing power from Bitcoin exposure, but they place the underlying coins under different custody and settlement arrangements.

Aave’s Hub and Spoke architecture separates shared liquidity from specialized lending rules. Hubs supply funds; Spokes manage positions, collateral and risk settings. A custom collateral process can therefore access lending liquidity without copying every rule of an ordinary token market.

The proposed Babylon Spoke would handle borrowing against native BTC. A second module, the BTC Vault Swap Spoke, would handle collateral after permissionless liquidation. These are separate jobs, even though both support the same loan.

Native custody does not mean pledged Bitcoin remains freely spendable. Under the design, release follows application rules and a proof-and-challenge process. The collateral remains committed to the loan until the conditions for withdrawal or liquidation are met.

Vault providers, application keepers and universal challengers participate in creating and protecting the vault. Babylon says a depositor can operate a vault provider themselves to challenge invalid claims. That makes the operating model relevant alongside custody: choosing who runs the infrastructure, and understanding the redemption conditions, remains part of using the arrangement.

WBTC handles liquidations before Bitcoin settles

The main timing problem is redemption. Babylon’s specification says native Bitcoin settlement takes multiple days because a claim must pass through a challenge window. Liquidators generally need a faster way to recover funds after repaying an unhealthy borrower’s debt.

The Swap Spoke would buy seized vaults from permissionless liquidators using WBTC drawn from an Aave Hub. Authorized arbitrageurs would later repay that WBTC debt, including accrued interest, buy the vaults and redeem the native Bitcoin.

This creates an important boundary around the no-wrapping claim. The borrower’s deposited collateral stays native BTC, while the liquidity used to clear a liquidation can still depend on a wrapped asset and participants authorized to redeem vaults.

Liquidation also moves whole vaults. If a vault exceeds the amount needed to clear the debt, the liquidator still takes the whole vault and pays the borrower for the remainder in WBTC at the same liquidation-bonus discount. The borrower could therefore finish with wrapped Bitcoin for that residual value.

By contrast, an application vault keeper already authorized to redeem a vault could liquidate through a separate permissioned path and claim the BTC directly. WBTC is consequently part of the proposed permissionless settlement route, rather than a requirement that every depositor wrap coins upfront.

Aave’s borrowing FAQ explains the underlying market risk: a falling collateral value or rising debt can reduce a position’s health factor, making it eligible for liquidation below one. Retaining Bitcoin keys does not remove that financial exposure.

The native-BTC proposal extends the same specialized-collateral approach seen in Aave’s tokenized-stock lending market. The central question is how an asset can be sold or redeemed under stress, alongside the borrowing power it offers in ordinary trading.

Aave vote must set Bitcoin loan limits

Full risk parameters would accompany a later on-chain proposal. The ARFC does not establish a final loan-to-value ratio, borrowing cap, live interest rate or mainnet date. Those omissions prevent a reliable calculation of borrowing capacity or total cost today.

The commercial terms are more explicit. Aave DAO would receive the first $500,000 in annual qualifying protocol revenue. Above that, revenue bands would divide proceeds among the DAO, Babylon and token purchases. Qualifying revenue covers specified protocol fees, rather than all borrower interest.

Operational controls also remain relevant. The proposal assigns market settings to Aave DAO and TBV configuration to Babylon governance representatives. It distinguishes a freeze that preserves exits from an emergency TBV pause that can stop them.

Babylon lists six firms across audit and formal-verification work, and says finalized changes are undergoing another review by Coinspect, ABDK and Zellic. Completed reviews and pending reports describe different stages. The proposal does not establish that the final deployment has already completed every security check.

Distribution agreements do not resolve those launch conditions. Babylon’s HashKey Cloud announcement describes planned institutional borrowing services and says further timing details will follow. It identifies native Bitcoin borrowing as live on testnet, which is separate from mainnet availability.

Bitcoin lending demand also cannot be inferred from technical readiness alone. The Botanix shutdown illustrated the difficulty of turning interest in productive BTC into sustained activity. Babylon’s proposed integration still needs approved limits, usable liquidity and actual borrowers.

Alternative.me showed a neutral reading of 53, compared with 62 the previous day, when checked at 12:01 UTC. The gauge measures broad crypto sentiment, rather than the proposed loan market’s safety.

The next steps are community feedback and risk analysis, followed by Snapshot and an on-chain Aave Improvement Proposal if supported. Babylon says follow-up audit reports will be shared when finalized. Approval, final parameters and deployment evidence remain the milestones needed to establish when these loans become available.