# [ARFC] Onboard Native BTC as Collateral to Aave V4 via Babylon Trustless Bitcoin Vaults

- Space: [Aave DAO](https://snapshot.box/s:aavedao.eth.md)
- Author: 0x66a28531E6f390A8CD44aB0C57a0F1aeb7E673FF
- State: Passed
- Voting type: Basic
- Start: 2026-11-06 14:03 UTC
- End: 2026-11-09 14:03 UTC
- Votes: 76
- Discussion: https://governance.aave.com/t/arfc-onboard-native-btc-as-collateral-to-aave-v4-via-babylon-trustless-bitcoin-vaults/25845
- Open in Snapshot: https://snapshot.box/#/s:aavedao.eth/proposal/0x83f578d707966014cd4ef7c7972f4af89c14964970f3f7088c688c07a6d915c0

## Results

- For: 356,881.41 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

**Title:** [ARFC] Onboard Native BTC as Collateral to Aave V4 via Babylon Trustless Bitcoin Vaults  
**Author:** Babylon Labs  
**Date:** 2026-11-5

---

## Simple Summary

This proposal requests the activation of native BTC as collateral on Aave V4 via the Trustless Bitcoin Vaults (TBV) protocol. The integration deploys two new Aave V4 Spokes, the Babylon Spoke and the BTC Vault Swap Spoke, and lists native BTC as the sole collateral asset of the Babylon Spoke. The first use case is borrowing stablecoins against native BTC. Risk parameters for both Spokes will be provided by Aave's risk service providers.

In TBV, a depositor locks BTC in a Taproot UTXO on Bitcoin Network. Redemption is governed by on-chain rules (e.g., the depositor repaid their loan) and settles directly to a Bitcoin UTXO controlled by the redeeming party. The deposited BTC is not wrapped, bridged or held by a custodian.

Following the passed [Temperature Check](https://governance.aave.com/t/temp-check-babylon-trustless-btc-vault-integration-on-aave-v4/24964) on this integration, the ARFC extends  
that scope to the integration with the Aave V4 Hub and Spoke architecture, the  
BTC vault lifecycle and its trust assumptions, liquidation and arbitrage  
mechanics, value accrual, and governance.

## Context

## Babylon

Babylon was started in 2022 by Stanford University Professor David Tse and Dr. Fisher Yu, with a vision of a Bitcoin-backed crypto economy built on trustless protocols that unlock Bitcoin's productivity without bridges, wrappers, or custodians.

The project is best known for the Bitcoin staking protocol, which lets BTC holders stake their BTC to secure other chains and rollups to provide economic security and earn staking rewards. The protocol is fully self-custodial: BTC never leaves Bitcoin and is not held by a bridge, wrapper, or signer set. Since the protocol's launch in August 2024, the protocol has activated over 100,000 BTC cumulatively, reached a peak TVL of 72,000 BTC, and currently holds ~40,772 BTC ([approximately $3.37B](https://staking.babylonlabs.io/btc)) staked.

The success of Bitcoin staking demonstrated that BTC holders seek trustless and native ways to put their Bitcoin to work. This motivated the development of Trustless Bitcoin Vaults (TBV), which extends the same trustless and self-custodial principles to general DeFi participation, and is the subject of this proposal.

The Babylon project is backed by approximately $110M+ to date from a16z, Paradigm, Polychain, Hack VC and others.

## Trustless Bitcoin Vaults (TBV)

Trustless Bitcoin Vaults (TBV) allows anyone to use their native bitcoins as collateral in supported on-chain applications, without transferring custody to any trusted third party.

TBV achieves this by locking BTC on Bitcoin inside a Taproot script. The conditions under which it can be moved are enforced cryptographically: redemption requires a valid zero-knowledge proof of an event on the host chain (e.g. Ethereum Mainnet), and any attempt to claim BTC without a valid proof can be challenged and stopped by an eligible challenger during a fraud-proof window. The depositor can act as a challenger themselves by operating their own vault provider, so they need not trust any third party to secure their BTC.

Spending conditions are encoded in the Taproot script and pre-authorized by all vault participants, including the depositor. The protocol itself is governed by zero-knowledge proofs through a challenge-based procedure, efficiently enabled by the BaBe protocol, and redemption is native to Bitcoin. The locked BTC moves to a recipient designated by the vault's spending conditions, which reference events on the host chain.

TBV can be integrated with any application on any supported host chain. Ethereum is the first supported host chain and the one this integration is built on. When BTC is locked in a Taproot script, a corresponding collateral record is created on Ethereum. Each application integration builds on it, optionally via an adapter layer that exposes it through the application's interface. For the Aave V4 integration, since Aave V4 only accepts ERC-20 tokens as collateral, the adapter contracts represent BTCVaults 1:1 as a transfer-restricted ERC-20 representation token. The full component set is detailed in Architecture Overview.

TBV is built on BaBe ([eprint 2026/065](https://eprint.iacr.org/2026/065.pdf)), peer-reviewed cryptographic research (to appear in CCS 2026, a top security conference) developed jointly by Babylon Labs and UC Berkeley. BaBe makes SNARK proof verification on Bitcoin approximately 1000x cheaper than prior approaches, making trustless Bitcoin DeFi practical at scale.

## **Motivation**

The Aave V4 integration with Babylon Trustless Bitcoin Vaults protocol enables onboarding of non-custodial native BTC collateral on Aave. Depositors can borrow allowed loan assets against this collateral, with no third-party custodian, signer consortium, or threshold-signature group holding the underlying BTC.

The BTC Vault Swap Spoke enables permissionless liquidation on Aave despite the underlying collateral settling natively on Bitcoin. Any liquidator can settle the position by receiving wrapped BTC for a small premium, while arbitrageurs purchase the escrowed vaults and handle the BTC-side redemption. Mechanism described in Specification.

Every escrowed BTCVault is backed by wrapped BTC borrowed from the Hub, creating new borrow demand for that asset. At launch this is WBTC, Aave's largest BTC reserve and presently underutilized on the borrow side; the integration can use any other wrapped BTC.

Native BTC as collateral on Aave V4 also serves as a composable primitive for the broader BTC DeFi ecosystem. Other projects can build new BTC-collateralized products on top, extending Aave’s reach into BTC-native DeFi.

## Specification

### Architecture Overview

The TBV deployment on Ethereum consists of protocol contracts and application contracts. A BTCVault is the protocol's core primitive, BTC locked in a UTXO on Bitcoin, secured by its pre-signed transaction graph. On Ethereum, each BTCVault is represented by a collateral record carrying its amount, its depositor, its participant set, and its lifecycle state. The protocol contracts track collateral records and enforce the vault lifecycle, from creation through activation to redemption.

The application contracts define how BTCVaults are used inside the integrated application, in this case as collateral for Aave V4 Babylon Spoke. The Aave application layer consists of the adapter contracts, the two new Spokes, and the collateral representation token. Depositors supply their BTCVaults and manage their positions through the adapter, and liquidators call it to liquidate unhealthy positions. The Babylon Spoke is a variant of the standard Aave V4 Spoke, written by Aave Labs and maintained in the Aave V4 repository ([Babylon Spoke](https://github.com/aave/aave-v4/pull/1345)), while the BTC Vault Swap Spoke introduces custom Spoke code.

## Babylon Spoke

On the Babylon Spoke, depositors borrow against native BTC, the Spoke's only collateral asset, drawing the borrowed assets from an Aave V4 Hub.

The Spoke differs from the standard Spoke in liquidation and collateral registration only. Only the Babylon Aave V4 adapter, configured as the Spoke's liquidation manager, can liquidate on the Spoke. The standard liquidation entry point is disabled. Each liquidation call targets one BTCVault. The adapter passes the BTCVault's amount to the Spoke as the maximum collateral to remove, and the Spoke repays only as much debt as that amount covers at the liquidation bonus, instead of repaying toward a target health factor. The Spoke charges no liquidation fee and applies no dust threshold, so the liquidator receives all the collateral removed. A position can use only the native BTC reserve as collateral.

The Spoke exposes the same set of risk parameters as a standard Aave V4 Spoke, with values configured for this Spoke. Because the collateral token cannot be transferred, some parameters are fixed: native BTC is collateral only and non-borrowable, the liquidation fee is zero, and receiving shares on liquidation is disabled. The target health factor has been removed, as each liquidation call seizes a single BTCVault and the liquidator repeats the call until the position is healthy.

A depositor locks BTC on Bitcoin, creating a BTCVault, and supplies it through the adapter. The adapter exposes the standard position-management actions, and the liquidation (both permissionless and permissioned) entry points.

## Native BTC Collateral Representation

Aave V4 accepts only ERC-20 tokens as collateral. Native BTC collateral is therefore represented by an ERC-20 token with transfer restrictions. The token is an internal accounting unit, not a BTC wrapper, it cannot be transferred between users, traded, or held anywhere outside the integration.

The token has 8 decimals, matching Bitcoin's satoshi denomination. Transfers are allowed only between the integration's Aave contracts, a fixed allowlist made up of the Aave V4 Hub, the adapter contract, and the per-user position proxy contracts that hold each depositor's position.

There are no risk parameters to configure for this token. The token contract is not upgradeable and has no admin. Its decimals, transfer restrictions, and the Hub and adapter addresses are set at deployment and cannot be changed.

Mint and burn are restricted to the adapter contract. The token is minted at BTCVault activation, directly into the depositor's position, and burned when a vault leaves a position, whether withdrawn by the depositor or seized in liquidation.....

Note: Due to the character count limitations of Snapshot, the remainder of the forum post cannot be shown, and can be found on the governance forum linked below.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

