# Aave approves the use of native Bitcoin as collateral in its V4

> Aave unanimously approves using native BTC as collateral in V4 with Babylon. 78% factor, no wrappers, and the on-chain vote is still pending.
> By José Maldonado · DeFi · 2026-11-11

The Aave DAO closed on November 9 a vote that had been in the works for months: using native bitcoin as collateral to borrow on Aave V4. The count published by Babylon Labs shows 100% of votes in favor, and it comes with two conditions worth reading before getting excited. The first is that the on-chain vote that activates the market is still pending. The second is that the bitcoin is not wrapped or bridged: it is locked in a self-custody vault and the borrower retains title to the asset.

The mechanism relies on Babylon's Trustless Bitcoin Vaults, an infrastructure that locks BTC in a Taproot output on the Bitcoin network and releases redemption through onchain rules. It is not an invention of this market: [Babylon has spent two years building staking on Bitcoin](https://observatorioblockchain.com/criptomonedas/bitcoin/asi-funciona-babylon-la-nueva-plataforma-de-staking-sobre-bitcoin/) and this integration is the first time that work becomes collateral for credit. Aave recognizes that deposit as collateral through an adapter and allows borrowing in stablecoins. No custodian, no consortium of signers, no threshold signing group. The bitcoin stays on Bitcoin while the credit is issued on Ethereum.

The approved numbers are competitive and explain the interest. The collateral factor is 78% and the risk premium is 0%, which in practice means native BTC does not pay extra interest compared with wrapped versions. Liquidity starts with a $21 million line split across USDT, USDC, GHO, USDG, RLUSD and WBTC. Deployment is planned for late 2026, in phases and with participation limits at first.

## Two vaults and an adapter

Aave V4's modular design faces its toughest test here, because the collateral cannot be moved from its source chain and the entire liquidation mechanics must be resolved on Ethereum.

The integration adds two components to that design. The first is the Babylon Spoke, a market where the only accepted collateral is native bitcoin and loans are repaid against the Core Hub's liquidity. The second is the BTC Vault Swap Spoke, the piece that solves the hardest problem: how to liquidate a position when the collateral lives on another chain and cannot be moved.

The solution is an adapter that works as a liquidation manager. When a position approaches the threshold, any liquidator can execute the operation and receive WBTC with a small premium, while an arbitrageur buys the vault as guarantee and handles the redemption on the Bitcoin side. Each vault corresponds to a WBTC loan taken from the Hub, which generates loan demand for an asset that is currently underused in Aave.

The [technical detail of the proposal](https://governance.aave.com/t/arfc-onboard-native-btc-as-collateral-to-aave-v4-via-babylon-trustless-bitcoin-vaults/25845) clarifies an important limitation: the collateral is not transferable. Aave only accepts ERC-20 tokens as collateral, so native BTC is represented by an internal eight-decimal token that cannot be moved between users, sold, or taken out of the system. It is not a wrapper, it is a unit of account with transfer restrictions fixed at deployment.

That design closes the door to anyone using the token as if it were WBTC, and also to redeeming it through alternative routes. Redemption happens on Bitcoin, against the vault's rules, and the contract that manages it is neither upgradeable nor has an administrator.

The consequence is that the Aave market cannot treat native bitcoin like just another asset: it is held by logic that lives outside Ethereum and responds to its own block times.

Each vault held as collateral corresponds to a WBTC loan taken from the Hub, a detail that changes the protocol's balance. WBTC is today Aave's largest bitcoin reserve and is underused on the lending side, so the integration gives it a new function: serving as a bridge between native settlement and the Ethereum market.

## Revenue sharing and audits

The economic side was voted on with the same level of detail as the technical side, and that is where each partner's contribution becomes clear: Aave brings the market and liquidity, Babylon the vault infrastructure and years of work on Bitcoin.

Aave keeps the first $500,000 of annual revenue from the integration and shares the surplus with Babylon in tiers. Between $500,000 and $2 million, the split is 78% for Aave, 18% for Babylon and 4% for a buyback fund; above $6 million, it drops to 61.5%, 31.5% and 7%. Of that fund, 85% goes to buying back AAVE and 15% to BABY.

The security work behind it is unusually long for a governance proposal. The summary of [Babylon on ARFC approval](https://babylonlabs.io/blog/arfc-passed-to-enable-native-bitcoin-btc-collateral-on-aave-v4-through-babylon) it lists six specialized firms that reviewed the vaults' code, joined by four Aave technical teams, formal verification and automated analysis tools. The project originated in the academic circle of David Tse, a Stanford professor, and its network raised 15 million dollars in January this year.

None of that guarantees that the market will work. An audit says that the code does what it promises, not that the economic model can withstand a 30% drop in the price of the collateral, nor that there will be liquidators willing to step in when needed. The restricted launch phase exists precisely because those questions are not answered in a document.

## What has not yet been approved

Aave's governance calendar has three stages and this vote only covers the first, so the market does not yet exist and no one can deposit bitcoin into it until the final vote passes.

The November 9 vote was the temperature check and the request for comments, not the activation. The next step is an on-chain improvement proposal (AIP) with the full parameters, and until that vote passes, native BTC cannot be used as collateral in production. Several reports on the announcement have presented the result as a launch, and it is not.

There is also a risk limit on the table. Aave's risk provider, LlamaRisk, proposed a cap of 300 BTC of collateral for the first phase, a figure that sets the tone with which governance itself views the experiment. If the market starts with that ceiling, initial volume will be modest and will grow by governance decision, not by demand.

It remains to be seen how liquidity behaves in practice. The incentive for a bitcoin holder is clear if rates are 3% to 5% versus the 9% to 16% that centralized platforms usually charge, but that spread only exists if there are lenders willing to supply stablecoins against collateral they cannot seize on their own chain.

A rational lender will look at three things before entering: the quality of the price oracle, the depth of liquidators and the time it takes for a redemption in Bitcoin when the market moves fast. Institutional interest in this class of assets is already visible: [Citi sees Aave as a way to lend without selling tokenized investments](https://observatorioblockchain.com/en/defi/citi-aave-prestamos-activos-tokenizados/), and that demand is what justifies a native collateral market.

## Bitcoin stops being a passive asset

The integration resolves a long-flagged anomaly: the sector's largest asset by market capitalization could not be used as collateral without trusting an intermediary or accepting a wrapper. There is now a path that requires neither, with the trade-off of a more complex liquidation mechanism and a new risk surface that governance will have to monitor.

The final vote is still missing, and so are the first real positions, which will arrive at the end of the year at the earliest. If the experiment works with the 300 BTC cap, the next debate will be how far to expand it, and that debate will say more about the state of decentralized finance than any partnership announcement.
