Babylon Labs has proposed bringing native Bitcoin collateral to Aave V4 through a vault integration designed to let holders borrow without first converting their BTC into a wrapped token. The October 14 governance proposal remains under discussion and does not establish that the lending service is approved or live.
The plan would add two components to Aave V4: a Babylon borrowing spoke and a BTC Vault Swap spoke. Its first intended use is borrowing stablecoins against Bitcoin held in a vault on the Bitcoin network. Risk parameters would need to be supplied by Aave’s risk service providers and included in a later approval process.
The proposal follows an earlier temperature check, but that preliminary expression of support is different from final authorization to activate the integration.
The collateral stays on Bitcoin
Under the design described by Babylon, a depositor locks BTC in a Taproot transaction output on Bitcoin. Redemption would follow conditions connected to the borrowing position, such as repayment of the loan, and settle to a Bitcoin output controlled by the redeeming party.
That differs from a user depositing Bitcoin with a custodian and receiving a transferable wrapped representation to use as collateral elsewhere. It does not mean every part of the proposed lending system is independent of other assets, contracts or governance decisions.
The proposal says each escrowed vault would be backed by wrapped BTC borrowed from an Aave hub, initially WBTC. Native Bitcoin remaining on its own chain and wrapped Bitcoin participating in the financing mechanism are therefore separate features of the same design.
Control of the coins is only part of the risk
Babylon describes the vaults as trustless and says a third-party custodian or signer group would not hold the deposited BTC. That is the proponent’s description of the architecture, rather than a guarantee that the arrangement eliminates every dependency.
Governance, contract pauses, exit paths, liquidation and the interaction between the networks still need assessment. Discussion in the forum specifically raises the effect of pausing vault contracts on exits and the role of Babylon governance representatives in those controls.
Our guide to keys and self-custody explains why retaining signing authority matters. For a borrowing position, however, readers must also understand the rules that determine when collateral can be released or liquidated.
In an October 16 reply, a Babylon engineer said emergency pauses could take effect immediately, while contract upgrades and configuration changes would face a five-day timelock. The response also describes an emergency guardian with an independent unpause right. Final membership and contract addresses are to be included in the formal improvement proposal.
Approval and implementation are still ahead
The published next steps begin with community feedback and risk analysis. If consensus is reached, the proposal would move to a Snapshot vote. A positive outcome would then be followed by a formal Aave improvement proposal with full risk parameters for onchain approval.
Those stages leave material decisions unresolved. Borrowing limits, liquidation incentives and operational safeguards can determine how useful and how risky a collateral market becomes, even when its broad technical concept is agreed.
The proposal opens a potential route for Bitcoin holders seeking liquidity without a conventional wrapped-token deposit. The present development is the detailed governance request and its design, with activation dependent on further scrutiny and approval.