Aave, the decentralized lending protocol, has introduced a groundbreaking governance proposal to allow users to borrow against native Bitcoin (BTC) without relying on wrapped tokens or centralized custody. This initiative, powered by Babylon, would be integrated into Aave V4’s spoke architecture. Here are the essential questions and answers to understand this development.
1. What exactly is Aave proposing with the Babylon-powered Bitcoin spoke?
Aave has launched a temperature check on its governance forum to create a dedicated Bitcoin lending spoke within its upcoming V4 upgrade. This spoke would be fueled by Babylon, a protocol designed to bridge Bitcoin with proof-of-stake networks. The core idea is to let users deposit native BTC directly into Aave and borrow other assets against it—without needing to first convert BTC into a wrapped token like wBTC or rely on a centralized custodian. The proposal seeks initial feedback from the Aave DAO before moving to a formal vote. If approved, this would mark a major step in bringing Bitcoin’s massive liquidity into DeFi while preserving its trustless nature.
2. How does native BTC borrowing differ from using wrapped tokens like WBTC?
Currently, borrowing against Bitcoin on Aave requires depositing a wrapped version—WBTC, renBTC, or tBTC. Wrapped tokens are ERC-20 representations of BTC on Ethereum, typically backed by a centralized custodian (e.g., BitGo for WBTC) that holds the actual Bitcoin. This introduces counterparty risk and trust assumptions. Native BTC borrowing eliminates that layer entirely: users keep full control of their Bitcoin in a non-custodial setup, using Babylon's cross-chain messaging to verify collateral without moving the BTC itself. The result is a more secure and decentralized experience, aligning with the original ethos of both Bitcoin and DeFi. Moreover, it avoids the gas fees and complexity of wrapping or unwrapping tokens for each transaction.
3. Why is Babylon technology critical for this proposed integration?
Babylon acts as a bridge between Bitcoin and proof-of-stake ecosystems, enabling Bitcoin to be used as collateral without a trust intermediary. Its key innovation is a Bitcoin timestamping protocol that allows Aave’s smart contracts to verify the existence, amount, and ownership of native BTC on the Bitcoin blockchain. When a user wants to borrow, they lock their BTC in a Babylon-controlled covenant on the Bitcoin network. Aave’s spoke receives a cryptographic proof of that lock, minting a corresponding debt position on the Ethereum side. No BTC ever leaves the Bitcoin chain until the loan is repaid or liquidated. This preserves Bitcoin’s security while granting it programmability in DeFi—something previously only possible via wrapped tokens or centralized bridges.
4. What is a "temperature check" governance proposal, and what happens next?
In Aave’s decentralized governance framework, a temperature check is the first informal step to gauge community sentiment before a formal vote. Anyone can post an idea on the Aave Governance Forum; if it gains enough support (usually signaled by a poll or forum reactions), it progresses to a Snapshot proposal (a gas‐less off‐chain vote) and finally to an on-chain AIP (Aave Improvement Proposal) for a binding, staked‐token vote. For this native BTC borrowing spoke, the temp check is open for discussion and feedback. The next milestone would be a formal Snapshot vote if the community shows interest. The entire process can take weeks to months, depending on deliberation and technical audits. Users holding AAVE or stkAAVE can participate in each stage.
5. How would this affect Aave users and the broader DeFi ecosystem?
For Aave users, the proposal would unlock a new collateral asset—native Bitcoin—that is far more liquid and widely held than any wrapped variant. This could attract a wave of Bitcoin holders who previously avoided DeFi due to wrapping complexity or custodial risks. Lenders would benefit from increased demand for borrowing, potentially boosting deposit yields. Broadly, integrating native BTC into Aave V4 positions the protocol as a multi-chain liquidity hub and could catalyze similar moves across other lending platforms. However, it also adds technical complexity: the Babylon relay and Bitcoin finality checks introduce latency and potential points of failure. The success of this spoke could set a precedent for how Bitcoin interacts with Ethereum‐based DeFi without synthetic tokens.
6. What risks are associated with borrowing against native BTC?
While eliminating custodial risk, native BTC borrowing introduces new vulnerabilities tied to cross-chain operations. The primary risk is bridge or relay failure—if Babylon’s timestamping or the communication layer breaks, Aave might not detect collateral updates correctly, leading to stale price feeds or liquidation errors. There’s also Bitcoin network congestion: slow block times (10 minutes on average) compared to Ethereum (~12 seconds) mean that liquidations or adjustments can’t be as fast. Smart contract bugs in the Babylon code or Aave’s spoke logic are another concern. Additionally, users must trust that Babylon remains secure and decentralized; a compromise of its validators could allow fraudulent proofs. Finally, regulatory ambiguity around non-custodial BTC lending could pose legal risks in certain jurisdictions.
7. When might we see this feature go live on Aave V4?
Aave V4 itself is still under development, with its launch expected sometime in 2025 or later, according to project roadmaps. The native BTC borrowing spoke would be one of several spoke chains within V4’s modular architecture. The governance process alone—from temperature check to on-chain vote—typically takes 2–3 months. After approval, technical implementation, auditing, and testing would follow, likely adding another 6–12 months. Therefore, the earliest realistic timeframe for this feature to go live is late 2025 or early 2026. However, community enthusiasm could accelerate milestones, or delays could push it further. The proposal is designed to be rolled out as part of V4’s initial deployment, not as a separate upgrade, so its timeline is tied to the broader V4 release schedule.