Babylon Proposes Native Bitcoin Collateral for Aave V4, Sidestepping Full Custody Transfer

Babylon is advancing a governance proposal to bring native Bitcoin into Aave V4 as collateral, a design that would let holders borrow against their BTC without moving it off the Bitcoin network. Risk parameters and final governance votes remain pending, but the proposal has cleared early discussion stages and is moving toward formal review.

The structure works by keeping the collateral on the Bitcoin blockchain while using Wrapped Bitcoin (WBTC) to settle permissionless liquidations on Aave's side. In practice, a borrower's Bitcoin stays on-chain under a staking arrangement managed through Babylon's infrastructure, while the liquidation mechanism draws on WBTC liquidity to close undercollateralized positions without requiring a custodian to move the underlying asset.

"The proposal would keep collateral on Bitcoin but use WBTC to settle permissionless liquidations."

Babylon's proposal documentation

That design is the core distinction from existing approaches. Every major attempt to bring Bitcoin into DeFi lending, from WBTC to the now-defunct renBTC, has required locking native BTC with a centralized or federated custodian before issuing a token that DeFi protocols can actually read. Babylon's model flips the dependency: the native asset stays put, and a liquid wrapped token handles the settlement layer. The custody problem does not disappear entirely, since WBTC itself carries BitGo custodial risk, but the primary collateral position never transfers off-chain.

Aave V4 is a fitting venue for the experiment. The upgrade, which has been in development as Aave's most significant architectural overhaul in years, introduces a unified liquidity layer and more modular risk configurations. That modularity matters here because native Bitcoin collateral requires custom risk parameters, separate from Aave's standard onboarding framework. Those parameters, including loan-to-value ratios, liquidation thresholds, and liquidation bonuses, have not been finalized. Aave's risk committees and the broader governance token holders will need to approve them before any integration goes live. Governance rejection or significant modification remains a real possibility.

The counter-arguments are substantive. Undefined risk settings create a gap in the safety model: without published liquidation thresholds, it is difficult to assess whether the protocol can handle a sharp BTC drawdown without cascading bad debt. The reliance on WBTC for liquidation settlement also reintroduces the wrapped token dependency that the proposal nominally avoids. Managing native Bitcoin collateral across two chains within a permissionless liquidation framework introduces coordination complexity that could become an attack surface. Regulatory treatment of Bitcoin-backed lending products is an additional open question, particularly in jurisdictions that have scrutinized collateralized crypto lending since the 2022 lending platform collapses.

Still, the market appetite for non-custodial Bitcoin yield and borrowing is real. Bitcoin's market cap routinely exceeds $1 trillion, yet its participation in DeFi lending protocols remains negligible compared to ETH and stablecoins, largely because of the custody barrier. Babylon has been building staking infrastructure specifically designed to put Bitcoin's economic weight to work without bridging it to another chain. If the Aave V4 proposal clears governance and the risk parameters land conservatively, it would mark the most significant structural integration of native Bitcoin into a major lending protocol to date. The Zest Protocol's recent V2 migration is restructuring its own Bitcoin-backed lending mechanics on Stacks, signaling that the broader sector is actively reworking how Bitcoin collateral functions inside lending systems.

The next milestone is governance. Aave delegates and AAVE token holders will need to weigh the protocol safety tradeoffs against the potential TVL (total value locked) upside of capturing even a fraction of Bitcoin's idle capital. A formal snapshot vote has not been scheduled as of October 14, 2026.