Institutions have wanted a way to borrow against their Bitcoin without ever letting go of it, and Aave Labs just proposed a mechanism that gets closer to doing exactly that. On September 14, Aave Labs published an ARFC proposal calling for a new, isolated Aave V4 Hub and Spoke deployment purpose-built to let institutionally custodied assets serve as collateral for stablecoin borrowing directly on the protocol.
The first instance targets Bitcoin held in custody at Anchorage Digital, a federally chartered digital-asset bank. Under the design, the custodian keeps physical possession of the underlying BTC for the entire life of the loan — it never touches Aave's smart contracts directly. What does move on-chain is a representation of that custodied position, giving Aave's lending markets a claim they can price and liquidate against without the protocol itself ever taking custody of the coins.
Isolated by design
The word 'isolated' in the proposal's architecture is doing real work. Rather than folding institutional custody assets into Aave's existing general-purpose lending pools, the new Hub and Spoke sits in its own walled-off risk compartment. If something goes wrong with the custody arrangement, an oracle feed, or the wrapped-asset mechanics, the damage is contained to that isolated market rather than bleeding into the broader protocol where retail depositors' funds sit. That separation has become standard practice across DeFi's institutional-facing products since a string of earlier incidents made clear that mixing novel collateral types with deep, general liquidity pools concentrates risk in the wrong place — a lesson underscored by how quickly a leveraged Aave position can unwind when collateral value moves fast.
The parameters are still blank
What the ARFC does not yet specify is arguably the more consequential half of the design: the collateral ratio, liquidation penalty, supply and borrowing caps, interest-rate model, and oracle configuration are all left for DAO risk service providers to propose in a follow-up AIP. That is a deliberate sequencing choice. Aave's governance process typically separates the conceptual question — should this integration exist at all — from the technical risk parameters, which get scrutinized separately once the community has signaled support for the underlying idea. The proposal now needs to clear three stages in order: an ARFC comment period to gather feedback, a Snapshot vote to gauge community sentiment, and finally a binding AIP vote that would actually authorize deployment.
Part of a bigger institutional push
The timing lines up with a broader shift already underway inside Aave. The protocol has spent much of 2026 courting exactly this kind of institutional deposit flow, part of a stated push to bring roughly a billion dollars in real-world-asset deposits onto its rails through partnerships with traditional asset managers. Anchorage's involvement fits that pattern: rather than asking institutions to bridge assets into unfamiliar custody arrangements, Aave is instead building the rails to meet institutional custody where it already sits, part of the same wave that has pushed on-chain tokenized assets past $346 billion industry-wide.
Related: Aave's Kulechov: CLARITY Act Is DeFi's Version of the GENIUS Act
Whether the arrangement gains real traction will come down to the numbers the risk providers eventually propose. A collateral ratio and borrowing cap set too conservatively will leave the product unused by institutions who can already borrow against Bitcoin more cheaply through traditional prime brokers; set too aggressively, and the isolation that makes the design safe on paper won't matter much if the Hub itself is undercollateralized. That tension is exactly what the next stage of governance now has to resolve.
FAQ
What is an Aave V4 isolated Hub and Spoke?
It is a self-contained lending market within Aave V4 that keeps a specific collateral type and its associated risk separate from the protocol's main, general-purpose lending pools.
Does Aave take custody of the Bitcoin used as collateral?
No. Under the proposal, Anchorage Digital retains custody of the underlying BTC for the full duration of the loan; only a representation of that position interacts with Aave's contracts.
What happens next in the approval process?
The proposal needs to pass an ARFC comment period, then a Snapshot vote, then a final AIP vote before deployment, with risk parameters like collateral ratio and borrowing caps set in a separate follow-up proposal.
