Babylon Labs Proposes Native Bitcoin Collateral for Aave V4
MissedBlock Desk · · 4 min read
Updated
Babylon Labs is advancing a proposal for Aave V4 that would enable users to borrow assets by using Bitcoin as collateral, without requiring the Bitcoin to leave the Bitcoin network. This approach aims to circumvent the need for wrapped Bitcoin (WBTC) and maintain self-custody for users.
Why This Matters
The materials describe a narrow update: Babylon Labs is developing a protocol (Trustless Bitcoin Vaults – TBV) that allows users to borrow assets on Aave V4 by using Bitcoin as collateral, with the Bitcoin remaining on the Bitcoin network in self-custodial Taproot UTXOs. Risk parameters still need to be set.
Broader Context
Source materials place the factual news in this context: Bitcoin has always had an awkward relationship with DeFi. It’s the largest crypto asset, yet using it in lending markets has usually meant wrapping it and trusting someone to hold the real coins.
Trustless Bitcoin Vaults Protocol
The proposal is built on Babylon’s Trustless Bitcoin Vaults (TBV) protocol. TBV locks Bitcoin in self-custodial Taproot UTXOs directly on the Bitcoin network. The system utilizes Taproot scripts and zero-knowledge proofs to enforce borrowing rules and manage collateral, with cryptography effectively replacing the role of a traditional custodian. This means no third party ever holds the private keys to the locked Bitcoin.
Aave V4 Integration
Aave V4’s modular architecture, which organizes markets into components called spokes, will accommodate this integration. Babylon’s plan introduces two new spokes: the Babylon Core Lending Spoke, where borrowers would deposit their vault-backed Bitcoin and take out assets like USDC, USDT, and WBTC, and the BTC Vault Swap Spoke, designed to manage liquidations.
Liquidations, a critical component of lending markets, are handled by the BTC Vault Swap Spoke. When a loan’s collateral value falls below a certain threshold, liquidators step in to repay the debt and claim the collateral at a discount. Babylon’s solution involves settling these liquidations in WBTC. This provides liquidators with an immediately usable asset on Ethereum, while the underlying Bitcoin collateral remains secured on its native network. This design aims to keep liquidations permissionless, allowing anyone to act as a liquidator.
Control over risk parameters, such as loan-to-value ratios and liquidation thresholds, remains with the Aave Decentralized Autonomous Organization (DAO). Babylon builds the technical infrastructure, but the Aave DAO tokenholders will ultimately decide on these crucial settings.
Development Timeline and Context
The partnership between Babylon Labs and Aave was first announced on December 3, 2025. A DAO temperature check, an initial gauge of community interest, began on May 25, 2026. A public testnet deployment for native BTC-backed borrowing was active by October 2026. Additionally, HashKey Cloud reported its integration of TBV for institutional clients on October 7, 2026.
This development addresses a long-standing challenge in Decentralized Finance (DeFi): integrating Bitcoin, the largest cryptocurrency, into lending markets without compromising user custody. Historically, this has often required wrapping Bitcoin into tokens on other blockchains, a process that many Bitcoin holders, particularly those adhering to the “not your keys, not your coins” principle, find unappealing. Babylon’s model seeks to eliminate this objection by allowing users to borrow against their Bitcoin while retaining full control over their private keys.
Furthermore, the integration could potentially increase the utilization of WBTC within Aave’s existing pools. Aave holds a significant supply of WBTC, but borrow demand for it has historically lagged. By facilitating WBTC payouts to liquidators and allowing borrowers to take out WBTC, the proposal might put more of this idle supply to work.
Next Steps and Uncertainties
However, the proposal is still navigating the Aave DAO governance process. Further votes, including the ARFC (Aave Request for Comment) and AIP (Aave Improvement Proposal) stages, are required before the integration can go live on the mainnet. The specific risk parameters set by the Aave DAO will be crucial in determining the adoption and success of this feature. Additionally, the robustness of the WBTC settlement mechanism under market stress and the competition from existing wrapped Bitcoin products will be key factors to monitor.
