Have you ever wished you could unlock the value of your Bitcoin without selling a single satoshi or handing it over to some third-party custodian? That exact question has been floating around DeFi circles for years, and now a concrete plan is on the table that tries to answer it head-on. On October 14, Babylon Labs dropped a formal governance proposal aimed at letting Aave users borrow stablecoins against native Bitcoin that never leaves the Bitcoin blockchain. No wrapping, no bridges in the traditional sense, and no surrendering custody. It sounds almost too clean to be true, yet the details suggest the team has spent serious time thinking through the mechanics.
What Babylon Actually Proposed for Aave V4
The proposal centers on something called Trustless Bitcoin Vaults. In simple terms, Bitcoin holders would lock their coins into special vaults that live directly on the Bitcoin network. Those locked coins would then serve as collateral for loans issued through Aave’s newest version, V4. The coins stay on Bitcoin the entire time. Aave’s Ethereum-based system simply recognizes the collateral through a tightly restricted accounting token that never leaves the designated contracts.
I’ve followed a lot of Bitcoin-DeFi experiments over the years, and most of them eventually lean on some form of wrapped asset or trusted intermediary. This one tries to sidestep that pattern. The technology leans on Bitcoin’s Taproot features to enforce strict conditions on how the deposited coins can ever move. Only when predetermined rules are satisfied can the BTC be released. Babylon describes the whole setup as operating without transferring custody to any trusted third party. That phrasing is deliberate, and it deserves a closer look.
How the Trustless Vault System Works in Practice
Users deposit BTC into vaults that exist on the Bitcoin chain itself. Once locked, those coins back a borrowing position on Aave. The system creates a special ERC-20 accounting token that represents the locked Bitcoin on a one-to-one basis. This token is not meant for trading or free transfer. Its only job is to let Aave’s contracts track the collateral value. When a vault becomes active, the supply of the accounting token increases. When collateral is withdrawn or liquidated, the supply shrinks.
The difference from current Aave offerings is pretty clear. Today, Bitcoin exposure on Aave usually comes through assets like WBTC or cbBTC. Those are tokens issued on other chains that represent Bitcoin held somewhere else. Ownership and custody arrangements vary depending on the specific product. Babylon’s approach keeps the original coins on Bitcoin throughout the life of the loan. That distinction matters to people who view self-custody as non-negotiable.
Perhaps the most interesting technical detail is the way liquidations would be handled. Redeeming a Bitcoin vault can take several days because of a built-in challenge period. That creates a timing mismatch with Aave’s need for relatively fast liquidation processes. To bridge the gap, the proposal introduces a second specialized component called the BTC Vault Swap Spoke. Liquidators would receive wrapped Bitcoin quickly while designated participants finish the underlying Bitcoin settlement. WBTC is the initial wrapped asset suggested for that temporary role.
Two New Aave V4 Components on the Table
Babylon is not asking to bolt Bitcoin support onto existing Aave markets in a casual way. The proposal calls for two dedicated components, referred to as Spokes within the Aave V4 architecture.
- The Babylon Spoke would handle the core borrowing function, letting users take out loans against native Bitcoin collateral.
- The BTC Vault Swap Spoke would manage the more complex liquidation flow, ensuring the system can still protect lenders even when the underlying collateral lives on a different chain.
Aave DAO would retain full control over the lending parameters. That includes borrowing limits, collateral ratios, interest rate models, and liquidation thresholds. Risk service providers would put forward the concrete numbers for community review. In the early discussion, Aave founder Stani Kulechov offered supportive comments, noting that native Bitcoin represents an important potential source of lending collateral and that Aave V4’s modular design is well suited for this kind of integration.
The proposal is not starting from zero. A temperature check ran back in May and passed a community vote in June. That earlier step gave the green light for the more detailed October submission. Still, nothing is live yet. The current stage is an Aave Request for Comment. Community members and risk specialists can dig into the design, raise concerns, and push for adjustments.
Revenue Sharing Between Aave DAO and Babylon
Money talks, and the proposal includes a clear revenue-sharing framework. Under the suggested terms, Aave DAO would receive the entire first $500,000 of qualifying annual revenue generated by the integration. Qualifying revenue would come from specific protocol fees, including Aave’s liquidity fee on borrowing interest and fees collected during liquidations.
After that initial threshold, the split changes across several bands:
- Between $500,000 and $2 million, Aave DAO would take 78 percent, Babylon 18 percent, and 4 percent would go toward token purchases.
- Higher revenue levels shift the percentages further, with Aave still receiving the majority share even above $6 million annually.
The token purchase allocation would buy AAVE and BABY on the open market, with 85 percent directed to AAVE and 15 percent to BABY. Those purchased tokens would then be split equally between Aave DAO and the Babylon Foundation. These numbers describe a proposed formula, not a guaranteed outcome. Babylon has not projected how much activity the integration might generate. The figures simply set the rules if revenue materializes.
For context, Babylon reported that its existing Bitcoin staking protocol has activated more than 100,000 BTC cumulatively since August 2024. At the time the proposal was prepared, roughly 40,772 BTC remained staked, valued around $3.37 billion. Those numbers relate only to staking activity. They do not represent Bitcoin already sitting in the proposed lending vaults.
Why This Matters for Bitcoin Holders Right Now
Bitcoin has always been strong as a store of value, yet it has lagged behind in productive use cases compared with assets that natively support smart contracts. Many holders sit on large positions and feel reluctant to sell because of tax implications, long-term conviction, or simple preference for self-custody. Being able to borrow against that position without moving the coins off Bitcoin addresses a real friction point.
In my view, the appeal sits in the combination of three things: the coins stay on Bitcoin, no traditional custodian sits in the middle, and the borrowing happens inside one of the most established lending protocols in DeFi. That combination is rare. Whether it proves robust enough for large-scale use is another question, and one the community will need to pressure-test thoroughly.
The proposal also arrives at a moment when institutional and retail interest in Bitcoin-backed products continues to grow. Different approaches exist across centralized platforms and other DeFi protocols. What stands out here is the attempt to keep the collateral as close as possible to its native environment while still plugging into Aave’s liquidity and risk management framework.
Security Reviews and Remaining Hurdles
Security work has already covered five areas: the Bitcoin vaults themselves, proof generation, smart contracts, web services, and the cryptographic system that supports vault settlements. Six firms participated in the audits, including Coinspect, Sherlock, Zellic, ABDK, ZK Security, and Runtime Verification. Babylon states that each component received at least two independent reviews, with formal verification performed on the smart contracts by Runtime Verification.
Further review of finalized changes is underway with Coinspect, ABDK, and Zellic before any mainnet deployment. The team has committed to publishing those follow-up reports once complete. That level of transparency is necessary. Cross-chain systems that involve Bitcoin and Ethereum inevitably create new surfaces for potential issues, and the longer challenge periods on the Bitcoin side add operational complexity.
Governance still has several steps ahead. After the current discussion and risk analysis phase, the proposal can move to an off-chain Snapshot vote that requires at least 320,000 AAVE-equivalent votes in support. A successful Snapshot would then lead to a formal on-chain Aave Improvement Proposal containing the complete risk settings. Babylon has not announced exact timelines for those votes.
Comparing Native BTC to Wrapped Alternatives
It is worth pausing to contrast the proposed model with the status quo. Wrapped Bitcoin products have served the ecosystem for years and currently provide substantial liquidity on Aave and elsewhere. They work. Yet they introduce counterparty and operational risks that some users prefer to avoid. The custody arrangements behind each wrapped product differ, and users must trust that the underlying Bitcoin remains properly reserved and accessible.
Babylon’s design tries to remove that layer. The accounting token is purely internal. Users never hold a freely transferable representation that could trade independently of the locked Bitcoin. The vault rules, enforced by Taproot conditions, dictate when and how the coins can move. If the system functions as described, the risk profile shifts from custodial risk toward the correctness of the cryptographic and smart-contract implementation.
That shift is not automatically better or worse. It is different. Users will need to evaluate whether they prefer the known risks of established wrapped assets or the newer risks of a native-vault design that has not yet operated at scale inside a major lending market.
Potential Benefits and Open Questions
If approved and successfully deployed, the integration could expand the usable collateral base for Aave while giving Bitcoin holders a new option for capital efficiency. Lenders on Aave would gain exposure to a fresh source of demand for stablecoin borrowing. The revenue-sharing structure aligns incentives between the two protocols, at least on paper.
Several open questions remain. How will the multi-day challenge periods interact with rapid market moves? Will liquidators find the temporary WBTC mechanism attractive enough to participate reliably? What collateral factors and liquidation thresholds will risk teams ultimately recommend? How will the accounting token’s restricted nature interact with Aave’s existing risk engines?
These are the kinds of details that separate a promising concept from a production-ready feature. The current Request for Comment phase exists precisely so that specialists can pressure-test those points before any binding vote.
Native Bitcoin as collateral represents an important potential expansion of lending markets when the technical and risk frameworks are carefully designed.
That sentiment, reflected in early comments from Aave leadership, captures the cautious optimism surrounding the proposal. The architecture of Aave V4 appears deliberately flexible enough to accommodate specialized components like the ones Babylon has outlined.
How the Liquidation Flow Would Actually Unfold
Liquidations are the stress test of any lending protocol. When a borrower’s collateral value drops relative to the outstanding debt, the system needs a reliable way to close positions and protect lenders. In a standard Aave market, that process happens on a single chain with assets that are immediately available. Here the collateral sits on Bitcoin while the debt lives in Aave’s environment.
According to the proposal, the BTC Vault Swap Spoke would allow liquidators to receive wrapped Bitcoin promptly. Designated participants would then complete the slower Bitcoin-side settlement. The system would process individual vaults, and a borrower holding multiple vaults could specify the order in which they should be used if liquidation becomes necessary. That level of granularity is thoughtful. It gives users some control even in a distressed scenario.
Still, the multi-day window introduces a period during which market conditions can change significantly. The design will need robust incentives and clear fallback rules so that the temporary wrapped exposure does not create new systemic risks inside Aave.
Context from Babylon’s Existing Staking Activity
Babylon did not appear out of nowhere with this lending idea. The protocol has already built a Bitcoin staking system that has seen meaningful adoption. Cumulative activation of more than 100,000 BTC and a current staked balance in the tens of thousands of coins demonstrate that a non-trivial number of Bitcoin holders are willing to lock coins for yield under the right conditions. Expanding from staking into lending is a logical next step for a team focused on bringing Bitcoin deeper into decentralized finance.
Earlier funding, including a $15 million investment from a well-known crypto venture firm, supported plans to grow beyond staking into additional services. The current Aave proposal fits that trajectory. Staking and lending remain separate activities with different risk profiles and reward structures, yet both rest on the same core idea of using native Bitcoin productively without traditional custody models.
What Users Should Watch Next
Anyone interested in this development should monitor three parallel tracks. First, the quality and volume of feedback during the Request for Comment period. Serious technical or risk concerns raised now can still shape the final design. Second, the eventual Snapshot vote and the level of AAVE voting power that turns out in support. Third, the publication of the remaining security reports and the concrete risk parameters that risk service providers ultimately put forward.
Even if the proposal advances smoothly through governance, mainnet deployment will still require careful monitoring in the early weeks and months. New collateral types always carry learning curves for both the protocol and its users. Borrowers will need clear documentation on vault management, challenge periods, and liquidation ordering. Lenders will want transparency around the temporary wrapped Bitcoin exposure during liquidations.
I’ve found that the most durable DeFi integrations are the ones that survive their first real market stress test with minimal drama. This proposal has the potential to become one of those, but only if the remaining design and governance work stays rigorous.
Broader Implications for Bitcoin in DeFi
Beyond the specific Aave integration, the proposal highlights a larger trend. More teams are exploring ways to bring Bitcoin’s security and liquidity into decentralized applications without relying on the classic bridge-and-wrap pattern. Some approaches use sidechains or specialized layer-2 solutions. Others, like Babylon’s vault design, try to keep the coins on the base Bitcoin layer while still making their value usable elsewhere.
Each approach carries trade-offs. Keeping coins on Bitcoin maximizes the security assumptions many holders care about most. It also introduces latency and complexity when interacting with faster smart-contract environments. The success of this particular design will depend on whether the benefits of native custody outweigh the operational friction for a critical mass of users.
If the model works at scale, it could encourage similar experiments on other major lending protocols. Competitive pressure tends to accelerate innovation once a viable path is demonstrated. At the same time, any significant incident involving the vaults or the liquidation mechanism would likely cool enthusiasm across the board. The stakes for careful execution are therefore high.
Risk Considerations for Potential Borrowers
Borrowing against any volatile asset carries well-known risks. Bitcoin’s price can move sharply in short periods. A borrower who takes on too much debt relative to collateral value can face liquidation. In this design the liquidation process includes an additional multi-day component on the Bitcoin side, which means the final settlement of the collateral may lag the market action that triggered the liquidation.
Users should also understand that the accounting token is not a freely tradable asset. It exists only inside the integration contracts. That restriction is intentional and protective, yet it means borrowers cannot easily exit a position by transferring the token to someone else. Position management will rely on the vault and Aave interfaces provided by the integration.
Interest rates, collateral factors, and liquidation penalties will be set by Aave governance. Those parameters can change over time through further proposals. Borrowers need to stay informed about governance decisions that affect their positions.
The Path from Proposal to Potential Launch
The sequence ahead is relatively standard for major Aave integrations, yet each step matters. Community discussion and risk analysis come first. A successful Snapshot vote would signal broad support. The final on-chain vote would then lock in the specific risk settings and authorize deployment. Parallel to governance, the remaining security reviews must conclude with satisfactory results.
Babylon has indicated that it is already conducting follow-up audits on the finalized changes. Publishing those reports will be an important transparency milestone. Only after both governance approval and security sign-off would any mainnet launch make sense.
Even then, a cautious rollout with limited initial capacity is common practice for new collateral types. Gradual increases in borrowing limits allow the system to prove itself under real conditions before larger amounts of capital flow in.
Final Thoughts on a Notable Development
Babylon’s proposal represents one of the more carefully constructed attempts to bring native Bitcoin into a major DeFi lending market. The combination of on-Bitcoin vaults, restricted accounting tokens, specialized liquidation handling, and a clear revenue-sharing framework shows that the team has tried to address the practical obstacles rather than paper over them.
Whether the community ultimately approves the design, and whether the system performs as hoped under market stress, remains to be seen. The coming weeks of discussion and risk analysis will reveal how robust the current proposal really is. For Bitcoin holders who have long wanted productive use of their coins without selling or wrapping, the idea itself is worth watching closely.
In the end, the strongest argument for this integration is simple. It tries to let users keep their Bitcoin where they want it—on the Bitcoin blockchain—while still accessing the liquidity and capital efficiency that Aave has built over years of operation. That is a hard combination to achieve. If the remaining technical, risk, and governance work holds up, it could open a meaningful new chapter for both protocols.
The proposal is still early in the formal process. Nothing is guaranteed. Yet the fact that a detailed, audited design has reached the Aave governance forum already marks progress compared with many earlier concepts that never advanced beyond discussion. The next steps belong to the community, the risk teams, and the auditors. Their collective scrutiny will decide whether native Bitcoin collateral on Aave becomes reality or remains an interesting idea on paper.
