Aave DAO Passes Proposal to Enable Native Bitcoin (BTC) Collateral on Aave V4 Through Babylon

Aave DAO Passes Proposal to Enable Native Bitcoin (BTC) Collateral on Aave V4 Through Babylon

Custom Image
Aave DAO approved a proposal on November 9, 2026, to enable native Bitcoin (BTC) collateral on Aave V4 through Babylon's Trustless Bitcoin Vaults. The Aave Request for Comment (ARFC) passed with 100% support, advancing plans to let Bitcoin holders borrow stablecoins while keeping their underlying BTC on the Bitcoin network. The proposed integration includes a 78% collateral factor and $21 million in initial stablecoin credit lines, potentially expanding Bitcoin's role in decentralized finance (DeFi) lending. However, the approval represents a preliminary governance milestone rather than a live product launch, with final on-chain authorization and technical deployment still pending.
 

Key Takeaways

  • Aave DAO approved Babylon's native Bitcoin collateral proposal on November 9, 2026, with 100% of votes supporting the ARFC.
  • Babylon's Trustless Bitcoin Vaults would allow BTC-backed borrowing on Aave V4 without transferring the underlying Bitcoin to Ethereum.
  • The proposed lending configuration includes a 78% collateral factor, $21 million in stablecoin credit lines, and an initial 300 BTC collateral cap.
  • Aave DAO and Babylon Foundation would share qualifying revenue, with allocations for AAVE and BABY token buybacks.
  • Security assessments identified and addressed serious vulnerabilities, although liquidation settlement, redemption delays, and cross-chain operations introduce continuing risks.
  • Final Aave Improvement Proposal approval and technical readiness remain necessary before the targeted late-2026 mainnet deployment.
 

Aave DAO Approves Babylon Proposal to Enable Native Bitcoin Collateral on Aave V4

Aave DAO approved a governance proposal on November 9, 2026, to introduce native Bitcoin as collateral on Aave V4 through Babylon's Trustless Bitcoin Vaults (TBV). The proposal would enable Bitcoin holders to secure decentralized loans without transferring BTC to a centralized custodian or converting it into a wrapped asset. The integration would connect Bitcoin-native collateral with Aave's Ethereum-based lending infrastructure, allowing BTC to support borrowing while remaining secured on its original blockchain.
 

Aave DAO Vote Passes With 100% Support on November 9, 2026

The unanimous result followed several months of technical development and community review involving Aave Labs, Babylon Labs, and independent risk specialists. The initiative entered Aave's governance process in May 2026, with an initial Temperature Check advancing in June. Babylon subsequently published the detailed ARFC on October 14, outlining the proposed integration, governance responsibilities, and operational safeguards. The November vote confirmed support among participating voting power for moving forward with the implementation.
 
The approval is particularly relevant because native Bitcoin has historically faced additional technical requirements when used in Ethereum-based decentralized finance. Existing arrangements through Aave's decentralized lending protocol commonly rely on wrapped representations such as WBTC or cbBTC, which introduce different custody and trust assumptions. Babylon's proposal seeks to support BTC-backed borrowing while keeping the underlying Bitcoin on its original blockchain. For Aave, the integration would extend its lending model to a new form of collateral without requiring Bitcoin itself to operate as an Ethereum-native token.
 

Why Final AIP Approval Is Still Required Before Launch

Despite the successful Snapshot vote, the Babylon integration has not received final approval for mainnet activation. The ARFC establishes community support for the proposed design, but implementation must still proceed through an Aave Improvement Proposal (AIP), the formal on-chain governance stage. According to Babylon Labs, deployment on Ethereum mainnet is targeted for late 2026, subject to technical readiness, security reviews, and the remaining governance requirements.
 
The next stages include:
  • Final governance approval: The AIP must complete Aave's on-chain voting and execution process before the integration can be activated.
  • Security and deployment readiness: The implementation must complete its remaining reviews and operational preparations before production use.
  • Controlled mainnet rollout: Babylon plans an initial restricted deployment with limits on participation and collateral volume, followed by potential expansion based on operational readiness.
 
The November 9 decision therefore establishes an important governance milestone for native Bitcoin lending on Aave V4, while the availability of BTC-backed borrowing remains dependent on the completion of these implementation steps.
 

How Babylon Enables Native BTC Collateral and Stablecoin Borrowing on Aave V4

Babylon's integration with Aave V4 uses Trustless Bitcoin Vaults (TBV) to connect Bitcoin collateral with lending markets on Ethereum. Rather than moving BTC between blockchains, the system locks Bitcoin in programmable vaults and creates a corresponding collateral record that Aave can recognize. This structure would allow borrowers to access supported stablecoin liquidity while their underlying BTC remains secured on the Bitcoin network. The proposed architecture combines Bitcoin's native transaction rules with Aave V4's lending, collateral valuation, and risk-management mechanisms.
 

How Babylon Trustless Bitcoin Vaults Support Native BTC Lending

Babylon's Trustless Bitcoin Vaults lock BTC in Taproot-based unspent transaction outputs (UTXOs), with spending conditions established before the vault becomes active. Aave V4 recognizes this collateral through a transfer-restricted ERC-20 accounting representation that tracks the locked Bitcoin at a 1:1 ratio. Unlike conventional wrapped Bitcoin and other wrapped tokens, this representation cannot be freely transferred, traded, or held outside the integration. Babylon uses cryptographic proofs and a challenge mechanism to verify authorized redemption events, connecting Ethereum-based lending activity with Bitcoin's native settlement rules.
 
The integration operates through Aave V4's Hub-and-Spoke architecture. A dedicated Babylon lending Spoke manages BTC-backed borrowing positions, while Aave's liquidity Hubs supply supported loan assets. An adapter coordinates vault activation, borrowing, repayments, and collateral withdrawals, with individual position contracts tracking each depositor's obligations. Chainlink's BTC/USD price feed supports collateral valuation and health-factor calculations. Multiple Bitcoin vaults can support one borrowing position, although each vault remains subject to its predefined spending conditions and redemption procedures.
 

Aave V4 Collateral Factor, Stablecoin Credit Lines, and Borrowing Limits

The proposed integration includes a 78% collateral factor, establishing a risk parameter used to determine borrowing capacity against eligible BTC collateral. Actual borrowing limits also depend on available liquidity, interest accrual, position health, and other market restrictions. According to the Aave governance proposal and LlamaRisk's assessment, the initial Core Hub configuration includes $21 million in stablecoin credit lines. Borrowers would pay variable interest based on the selected asset's lending-market conditions, while additional integration-related fees may apply.
 
The initial risk configuration also specifies several operational limits:
  • Stablecoin liquidity: Proposed credit lines include $8 million each for USDT and USDC, $2 million each for USDG and RLUSD, and $1 million for GHO.
  • Collateral capacity: LlamaRisk recommends an initial 300 BTC collateral cap, with potential adjustments subject to governance and risk assessments.
  • Separate settlement liquidity: A 100 WBTC credit line is proposed for the BTCVault Swap Spoke, distinct from the $21 million allocated to stablecoin borrowing.
 
These amounts represent planned credit limits rather than outstanding loans or guaranteed liquidity available to individual borrowers. The architecture also supports a dedicated Babylon Hub with separately configured asset limits.
 

How Native Bitcoin Liquidations Work on Aave V4

Bitcoin-backed positions become eligible for liquidation when their health factor falls below 1, indicating that collateral no longer provides sufficient coverage for the outstanding debt under the protocol's risk rules. Unlike conventional ERC-20 collateral, individual Bitcoin vaults cannot be fractionally seized because their underlying UTXOs are indivisible. The system therefore liquidates whole vaults while allowing positions containing multiple vaults to retain unaffected collateral where possible. A fairness mechanism can reduce remaining debt or compensate borrowers in WBTC when seized collateral exceeds the amount required under the liquidation rules.
 
The BTCVault Swap Spoke addresses the timing difference between Ethereum liquidations and Bitcoin redemption. Unlike conventional DeFi liquidation mechanisms, which can settle directly using transferable collateral tokens, this system must account for Bitcoin vault redemption restrictions. Eligible liquidators can receive WBTC settlement through the lending infrastructure, while registered arbitrageurs subsequently acquire escrowed Bitcoin vaults, repay the associated WBTC debt, and complete redemption on Bitcoin. This process separates immediate liquidation settlement from the multiday Bitcoin redemption and challenge period. However, its effectiveness depends on available WBTC liquidity, functioning settlement contracts, and arbitrageur participation, creating operational risks that differ from conventional Ethereum-based collateral markets.
 

Aave–Babylon Revenue Sharing, Security Risks, and Native BTC Launch Timeline

The proposed Aave–Babylon integration includes a revenue-sharing agreement, independent security assessments, and a phased deployment strategy intended to manage the risks of Bitcoin-backed decentralized lending. Beyond introducing native BTC as collateral, the arrangement establishes how protocol revenue would be distributed, which organizations would oversee critical infrastructure, and what safeguards must be in place before broader participation. These commercial and operational details will help determine the integration's long-term viability.
 

How Aave and Babylon Will Share Revenue and Fund AAVE and BABY Buybacks

Under the governance proposal, Aave DAO would receive the first $500,000 in annual qualifying revenue generated by the integration. Revenue above that threshold would be divided among Aave DAO, Babylon Foundation, and a dedicated token purchase allocation. Qualifying revenue includes Aave Hub liquidity fees associated with Babylon borrowing activity and liquidation fees collected through the integration. It does not represent all interest paid by borrowers. The agreement uses progressive revenue bands, meaning each percentage applies only to the revenue earned within its specified range, with distributions scheduled monthly.
 
Under the proposed revenue-sharing agreement, Aave DAO would receive 100% of the first $500,000 in annual qualifying revenue. Revenue above that amount would be distributed progressively among Aave DAO, Babylon Foundation, and a dedicated token purchase allocation, according to the following thresholds:
 
  • $500,000–$2 million: Aave DAO receives 78%, Babylon Foundation receives 18%, and 4% goes toward token purchases.
  • $2 million–$4 million: Aave DAO receives 72.5%, Babylon Foundation receives 22.5%, and 5% is allocated to token purchases.
  • $4 million–$6 million: Aave DAO receives 67%, Babylon Foundation receives 27%, and 6% supports token purchases.
  • Above $6 million: Aave DAO receives 61.5%, Babylon Foundation receives 31.5%, and 7% is allocated to token purchases.
 
These percentages apply only to qualifying revenue within each respective band, rather than the entire annual revenue amount. The token purchase allocation would be divided between AAVE (85%) and BABY (15%), subject to actual revenue generation after the integration launches.
 
The token purchase allocation would direct 85% toward AAVE and 15% toward BABY, with purchased tokens divided equally between Aave DAO and Babylon Foundation. Babylon Foundation would also be responsible for incentive arrangements supporting the integration, including borrower incentives and strategic partnerships. However, these allocations depend on actual qualifying revenue after launch. They do not establish guaranteed earnings, token purchase volumes, or future AAVE token price performance.
 

Security Audits, Protocol Governance, and Remaining Bitcoin Collateral Risks

Babylon's security review covers five major components, including Bitcoin vault contracts, cryptographic provers, Ethereum smart contracts, web services, and the BaBe verification protocol. The governance documentation identifies Coinspect, Sherlock, Zellic, ABDK, ZK Security, and Runtime Verification among the security firms involved, with overlapping review responsibilities. Aave Labs has also conducted internal assessments and arranged additional independent verification, including work involving Certora. According to LlamaRisk's October 23 assessment, earlier reviews identified high- and critical-severity vulnerabilities that were subsequently addressed. Further reviews found no new critical issues, while remaining lower-severity findings were either resolved or acknowledged.
 
Nevertheless, completed security audits do not eliminate smart-contract or operational risk. The system depends on correct cryptographic verification, reliable cross-chain state information, and functioning emergency controls. LlamaRisk recommended independent proof-of-reserves monitoring to verify the Bitcoin backing associated with active vaults. The governance framework also separates oversight responsibilities: Aave DAO controls lending-market parameters, while Babylon governance representatives oversee the underlying vault infrastructure. Contract upgrades and parameter changes are subject to timelocks, although emergency pause and freeze functions can restrict activity when necessary. Babylon also maintains a $500,000 bug bounty program through Sherlock, with the integration contracts intended to fall within its scope.
 

Aave V4 Native Bitcoin Collateral Launch Timeline and Next Development Stages

Babylon Labs has identified late 2026 as the target for Ethereum mainnet deployment, although the schedule remains conditional on final governance authorization and technical readiness. The initial launch is intended to operate with restricted participation rather than immediately opening deposits to all Bitcoin holders. LlamaRisk's assessment describes a default-deny allowlist beginning with selected institutional and partner participants, followed by a potential expansion of borrower access and protocol capacity over approximately six months. The timing and scale of that expansion would depend on operational performance, risk assessments, and governance decisions.
 
The initial user experience would also differ from ordinary Aave lending markets. Aave Labs has indicated that users would be able to view Babylon-related positions through Aave Pro, while transactional actions would be handled through Babylon's interface. The standard Aave SDK is not expected to support these market transactions at launch, with specialized integration documentation and tooling provided separately. As of November 11, 2026, the publicly identified next milestone remains the final Aave Improvement Proposal and confirmation of the deployment schedule. Neither the targeted launch window nor the proposed financial arrangements establish that the integration is already generating revenue or supporting live native-BTC loans.
 

Conclusion

Aave DAO's approval of the Babylon proposal advances a lending model that could connect native Bitcoin collateral with Ethereum-based DeFi without requiring borrowers to convert their BTC into freely transferable wrapped tokens. The proposed architecture, lending parameters, and revenue-sharing framework establish a foundation for the integration, although its commercial impact will depend on actual borrowing activity and protocol revenue after deployment. The arrangement also introduces distinct technical considerations, particularly around collateral verification, liquidation settlement, and cross-chain operations.
 
The next important milestone is the final Aave Improvement Proposal (AIP), followed by confirmation of security readiness and mainnet activation. Babylon's late-2026 deployment target remains conditional, while initial participation restrictions and collateral limits could constrain early activity. For Aave and Babylon, the meaningful test will be whether the integration can support reliable BTC-backed lending while maintaining adequate liquidity, transparent risk controls, and secure collateral redemption.
 

FAQs

Does Babylon's Aave V4 integration require a Bitcoin network upgrade?

No. The proposed integration uses existing Bitcoin capabilities, including Taproot-based transaction conditions. It does not require a Bitcoin hard fork or changes to the network's consensus rules.

Is using native BTC as collateral the same as Bitcoin staking?

No. BTC-backed lending allows Bitcoin to secure a loan, while Bitcoin staking arrangements generally involve committing BTC to support another network or protocol. These activities have different mechanisms, financial obligations, and risks.

Can borrowers withdraw their Bitcoin while an Aave V4 loan remains active?

Withdrawals depend on the borrower's outstanding debt and collateral requirements. Borrowers generally cannot freely withdraw locked BTC if doing so would leave their loans insufficiently collateralized. Bitcoin vault redemption also follows the protocol's withdrawal conditions.

Does a 78% collateral factor mean Bitcoin loans are liquidated at 78%?

Not necessarily. The collateral factor helps determine borrowing capacity, while liquidation depends on the applicable liquidation threshold and the position's health factor. Borrowing interest and changes in collateral value can also affect liquidation eligibility.
 

Disclaimer

This general market information, possibly from third-party, commercial, or sponsored sources, is provided for reference and educational purposes only and does not constitute financial or investment advice, an offer, solicitation, or guarantee. We disclaim liability for its accuracy, completeness, reliability, and any resulting losses. Investments/trading are risky; past performance doesn’t guarantee future results. Users should research, judge prudently, and take full responsibility. For further details, please consult KuCoin’s Terms of Use and Risk Disclosure.