Babylon advances native Bitcoin collateral plan for Aave V4

Babylon advances native Bitcoin collateral plan for Aave V4

The proposal keeps BTC on the Bitcoin network while paying liquidators in WBTC, but risk settings and further governance votes are still pending

Babylon Labs is pushing forward a plan to let people borrow on Aave V4 using Bitcoin that never leaves the Bitcoin network.

The pitch is simple. Your BTC stays put, you borrow against it, and nobody has to hold your coins for you.

The catch, as with most things in DeFi governance, is that the paperwork isn’t finished. Risk parameters still need to be set, and more Aave DAO votes are required before anything goes live on mainnet.

How the setup actually works

The proposal is built on Babylon’s Trustless Bitcoin Vaults protocol, or TBV. Instead of wrapping BTC into a token on another chain, TBV locks the coins in self-custodial Taproot UTXOs on Bitcoin itself.

Think of it as a safe deposit box with programmable rules. The box sits on Bitcoin, and the rules decide when the contents can move.

Those rules are enforced through Taproot scripts and zero-knowledge proofs. Put plainly, cryptography plays the role a custodian normally would, and no third party ever holds the keys.

On the Aave side, deposits show up through an internal accounting unit called vaultBTC. It acts as a verifiable record of the BTC sitting in vaults, which Aave can then treat as collateral.

The integration leans on Aave V4’s modular design, which organizes markets into components called spokes. Babylon’s plan adds two of them.

The first is the Babylon Core Lending Spoke. This is where borrowers would post vault-backed BTC and take out assets such as USDC, USDT and WBTC.

The second is the BTC Vault Swap Spoke. Its job is to handle the messy part of lending: liquidations.

Advertisement

The WBTC twist in liquidations

Every lending market lives or dies by its liquidations. When a loan’s collateral falls below a safe threshold, outside parties called liquidators step in, repay the debt and collect the collateral at a discount.

That works smoothly when the collateral is a token sitting on the same chain. It gets awkward when the collateral is locked BTC on an entirely different network.

Babylon’s answer is to keep the collateral on Bitcoin while settling liquidations in WBTC. Through the BTC Vault Swap Spoke, liquidators would receive WBTC immediately rather than waiting on native BTC to move.

So liquidators get a familiar asset they can use right away on Ethereum. Borrowers, meanwhile, never had to wrap anything going in.

The design keeps liquidations permissionless, meaning anyone can act as a liquidator. Babylon has published documentation on the liquidation model in its developer docs.

Importantly, control over risk settings stays with the Aave DAO. Babylon builds the plumbing, but tokenholders decide how much can be borrowed and when positions get closed out.

A timeline measured in governance phases

Babylon and Aave first announced their partnership on December 3, 2025. The idea moved into Aave’s formal process with a DAO temperature check that began on May 25, 2026.

A temperature check is Aave’s version of a show of hands. It gauges interest before a proposal moves into the heavier ARFC and AIP stages, which are the detailed request-for-comment and final on-chain vote phases.

Public testnet deployment for native BTC-backed borrowing was active by October 2026. Around the same time, HashKey Cloud’s integration of TBV for institutional clients was confirmed on October 7, 2026.

That institutional piece matters. Custody-wary funds have often been the loudest critics of wrapped Bitcoin, so a trust-minimized route may appeal to exactly that crowd.

Still, testnet is testnet. Real money hasn’t touched this design yet, and the remaining ARFC and AIP phases are where proposals tend to get picked apart line by line.

Why this matters for Bitcoin in DeFi

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.

That tradeoff has kept plenty of long-term holders on the sidelines. For a group whose motto is roughly “not your keys, not your coins,” handing BTC to a custodian is a tough sell.

Babylon’s model tries to remove that objection entirely. If it works as described, holders could tap lending markets without ever giving up custody.

There’s also an interesting second-order effect on Aave itself. The protocol holds one of its largest token supplies in WBTC, but borrow demand for that WBTC has historically lagged.

In other words, a lot of WBTC sits in Aave’s pools doing very little. Since liquidators in Babylon’s design get paid in WBTC and borrowers can take out WBTC, the integration could potentially put more of that idle supply to work.

What to watch

The first thing to track is the risk parameters. Loan-to-value ratios, liquidation thresholds and supply caps will determine whether this is a niche experiment or a serious Bitcoin borrowing venue.

Conservative settings would limit early risk but also limit appeal. Aggressive ones would attract borrowers while putting more weight on the untested liquidation path.

The second is how the WBTC settlement holds up under stress. A design that pays liquidators instantly needs enough liquidity behind it during a sharp BTC drawdown, which is precisely when everyone wants out at once.

The third is competition. Wrapped Bitcoin products have long dominated BTC collateral in DeFi, and a credible native alternative on the largest lending protocol would put pressure on custodial models to justify their trust assumptions.

For BTC holders, the appeal is clear: borrowing power without surrendering custody. For Aave, it’s a shot at drawing in a huge pool of capital that has mostly stayed on the sidelines. Whether both sides get what they want now depends on a few more rounds of DAO voting.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.
Babylon advances native Bitcoin collateral plan for Aave V4
Babylon advances native Bitcoin collateral plan for Aave V4

The proposal keeps BTC on the Bitcoin network while paying liquidators in WBTC, but risk settings and further governance votes are still pending

Babylon Labs is pushing forward a plan to let people borrow on Aave V4 using Bitcoin that never leaves the Bitcoin network.

The pitch is simple. Your BTC stays put, you borrow against it, and nobody has to hold your coins for you.

The catch, as with most things in DeFi governance, is that the paperwork isn’t finished. Risk parameters still need to be set, and more Aave DAO votes are required before anything goes live on mainnet.

How the setup actually works

The proposal is built on Babylon’s Trustless Bitcoin Vaults protocol, or TBV. Instead of wrapping BTC into a token on another chain, TBV locks the coins in self-custodial Taproot UTXOs on Bitcoin itself.

Think of it as a safe deposit box with programmable rules. The box sits on Bitcoin, and the rules decide when the contents can move.

Those rules are enforced through Taproot scripts and zero-knowledge proofs. Put plainly, cryptography plays the role a custodian normally would, and no third party ever holds the keys.

On the Aave side, deposits show up through an internal accounting unit called vaultBTC. It acts as a verifiable record of the BTC sitting in vaults, which Aave can then treat as collateral.

The integration leans on Aave V4’s modular design, which organizes markets into components called spokes. Babylon’s plan adds two of them.

The first is the Babylon Core Lending Spoke. This is where borrowers would post vault-backed BTC and take out assets such as USDC, USDT and WBTC.

The second is the BTC Vault Swap Spoke. Its job is to handle the messy part of lending: liquidations.

Advertisement

The WBTC twist in liquidations

Every lending market lives or dies by its liquidations. When a loan’s collateral falls below a safe threshold, outside parties called liquidators step in, repay the debt and collect the collateral at a discount.

That works smoothly when the collateral is a token sitting on the same chain. It gets awkward when the collateral is locked BTC on an entirely different network.

Babylon’s answer is to keep the collateral on Bitcoin while settling liquidations in WBTC. Through the BTC Vault Swap Spoke, liquidators would receive WBTC immediately rather than waiting on native BTC to move.

So liquidators get a familiar asset they can use right away on Ethereum. Borrowers, meanwhile, never had to wrap anything going in.

The design keeps liquidations permissionless, meaning anyone can act as a liquidator. Babylon has published documentation on the liquidation model in its developer docs.

Importantly, control over risk settings stays with the Aave DAO. Babylon builds the plumbing, but tokenholders decide how much can be borrowed and when positions get closed out.

A timeline measured in governance phases

Babylon and Aave first announced their partnership on December 3, 2025. The idea moved into Aave’s formal process with a DAO temperature check that began on May 25, 2026.

A temperature check is Aave’s version of a show of hands. It gauges interest before a proposal moves into the heavier ARFC and AIP stages, which are the detailed request-for-comment and final on-chain vote phases.

Public testnet deployment for native BTC-backed borrowing was active by October 2026. Around the same time, HashKey Cloud’s integration of TBV for institutional clients was confirmed on October 7, 2026.

That institutional piece matters. Custody-wary funds have often been the loudest critics of wrapped Bitcoin, so a trust-minimized route may appeal to exactly that crowd.

Still, testnet is testnet. Real money hasn’t touched this design yet, and the remaining ARFC and AIP phases are where proposals tend to get picked apart line by line.

Why this matters for Bitcoin in DeFi

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.

That tradeoff has kept plenty of long-term holders on the sidelines. For a group whose motto is roughly “not your keys, not your coins,” handing BTC to a custodian is a tough sell.

Babylon’s model tries to remove that objection entirely. If it works as described, holders could tap lending markets without ever giving up custody.

There’s also an interesting second-order effect on Aave itself. The protocol holds one of its largest token supplies in WBTC, but borrow demand for that WBTC has historically lagged.

In other words, a lot of WBTC sits in Aave’s pools doing very little. Since liquidators in Babylon’s design get paid in WBTC and borrowers can take out WBTC, the integration could potentially put more of that idle supply to work.

What to watch

The first thing to track is the risk parameters. Loan-to-value ratios, liquidation thresholds and supply caps will determine whether this is a niche experiment or a serious Bitcoin borrowing venue.

Conservative settings would limit early risk but also limit appeal. Aggressive ones would attract borrowers while putting more weight on the untested liquidation path.

The second is how the WBTC settlement holds up under stress. A design that pays liquidators instantly needs enough liquidity behind it during a sharp BTC drawdown, which is precisely when everyone wants out at once.

The third is competition. Wrapped Bitcoin products have long dominated BTC collateral in DeFi, and a credible native alternative on the largest lending protocol would put pressure on custodial models to justify their trust assumptions.

For BTC holders, the appeal is clear: borrowing power without surrendering custody. For Aave, it’s a shot at drawing in a huge pool of capital that has mostly stayed on the sidelines. Whether both sides get what they want now depends on a few more rounds of DAO voting.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.