Aave's Bitcoin Collateral Plan: Who Actually Holds It?

On October 14, 2026, Babylon Labs filed a formal governance request asking Aave's decentralized autonomous organization to let Bitcoin itself, not a wrapped token standing in for it, back loans on Aave V4. The filing proposes two new Aave V4 Spokes built around what Babylon calls Trustless Bitcoin Vaults, and the pitch behind this Aave Bitcoin collateral plan is specific: the BTC would stay on the Bitcoin blockchain the entire time it sits as collateral, never bridged to Ethereum, never wrapped into a token, never pooled into a company's own balance sheet. That is a specific claim for a lending protocol to make about someone else's coins, so here is a walkthrough of what the filing actually says, step by step, and what still separates a governance post from a live product people can use.

First: What Babylon's Aave Bitcoin Collateral Proposal Actually Says

Babylon's request follows an earlier temperature check it posted to Aave's forum back in May 2026, asking the community whether onboarding native BTC was worth pursuing at all. The October 14 filing is the formal next step, an ARFC, short for "Aave Request for Comment," and it names two concrete pieces of new infrastructure: a Babylon Spoke, where native BTC is the sole collateral asset and the first use is borrowing stablecoins against it, and a BTC Vault Swap Spoke, which handles settlement after a liquidation. You can read the proposal's own language in the ARFC Babylon filed with Aave's governance forum, which lays out both Spokes and the parameters the DAO would need to approve.

Then: How the Vault Is Built to Avoid Becoming Another Custodian

The mechanism is the part worth slowing down for. According to Babylon's description, a depositor's BTC is locked under spending conditions written directly into a Bitcoin Taproot script, not handed to a company, a signer committee, or a bridge contract. Redemption depends on those on-chain conditions being met, and the proposal states that the vault settles directly to a Bitcoin UTXO controlled by the person redeeming it, not to an intermediary who then forwards the funds. Babylon's own May 2026 temperature check went further, describing a design with no third-party custodian and no signer consortium or threshold-signature group holding discretionary control over the underlying BTC. That framing is Babylon's characterization of its own protocol. It has not been independently audited in public reporting found for this post, and it is worth reading that way: as what the design is supposed to do, not yet as a verified fact about what it does under adversarial conditions.

Next: What Still Has to Happen Before Any Real Loan Touches This

An ARFC is a comment stage, not an approval. Coverage of the filing notes that Aave's DAO still has to review and approve risk parameters and caps on both new Spokes, and that security audits are still pending before anything goes live. One detail reported alongside the filing is that a multisig involving Llama Risk, Babylon Labs, and Aave Labs would govern the BTC Vault Swap Spoke specifically, which is itself a form of shared control worth watching closely as the proposal moves through review, since "no custodian" and "no multisig anywhere in the system" are not quite the same claim. Nothing here is live yet. If you are reading this expecting an already-working product, the honest answer is that it is still a governance proposal working its way through Aave's own process, with audits and parameter votes still ahead of it.

Finally: The Same Question This Raises for Anything Holding Your Bitcoin

Strip away the DeFi vocabulary and this is the same question solo miners have been asking about pools for years: when something touches your Bitcoin, does it actually hold it, or does it only read and verify it? NexusPool's technology page answers that question for mining the same way Babylon's filing tries to answer it for lending. The block pays your address. There is no balance for us to hold. That is true because the coinbase transaction in a found block pays the miner's own address directly, with a 0% pool fee and nothing routed through a pool-held account first. NexusPool also publishes a tool called Payout Preflight that shows the exact coinbase that would pay your address on the current block, before any block is actually found, so the claim is checkable rather than just stated. And for the hourly accounting of the work a rig did, NexusPool signs a receipt it calls the Glass Ledger, built against a key it publishes, rather than asking anyone to just trust an internal dashboard.

None of this means Aave's proposal is safe, finished, or a substitute for doing your own reading. This post is not investment advice, it does not recommend using Aave, Babylon, or any lending protocol, and it is not a claim that NexusPool's own software is open source or publicly auditable today. It is simply a mechanism, described from the primary filing, placed next to a different mechanism NexusPool already runs for mining. Before you put Bitcoin into any vault, lending spoke, exchange, or mining pool, check this first: who, specifically, holds the key that can move it, and what, specifically, happens the moment you ask for it back. If a project can't answer that in one sentence, the rest of its pitch matters less than it sounds like it should.

Keep the whole block. See your payout before you win.

Trust nothing. Verify who actually holds the Bitcoin before it goes into any vault, lending spoke, or pool.