Bitcoin-focused developer Babylon Labs has formally submitted a groundbreaking governance proposal designed to allow decentralized finance users to borrow stablecoins on the Aave lending protocol using native Bitcoin as collateral. This development marks a significant step forward in bridging the world’s largest cryptocurrency by market capitalization with decentralized finance ecosystems, offering a novel structural approach that eliminates the need for traditional wrapped tokens or centralized custodians.
Under the mechanics outlined in the proposal, users would securely lock their native Bitcoin within specialized vaults directly on the Bitcoin network. Once the Bitcoin is locked in these vaults, users would be able to borrow stablecoins against that underlying collateral on Aave. To track and manage this position across different blockchain networks, a non-transferable token minted on Ethereum would represent the collateral position. Meanwhile, the actual Bitcoin remains securely anchored on its native blockchain, completely avoiding the traditional processes of bridging or wrapping assets that have historically introduced technical vulnerabilities to cross-chain transactions.
The submission of this formal proposal on a Wednesday follows a lengthy preliminary trajectory that began months earlier. Babylon Labs initially introduced the concept to the community with a temperature check proposal on May 25. This early governance step was met with favorable community sentiment, eventually leading to a preliminary community vote that officially passed on June 10, according to public disclosures from Babylon Labs during their quarterly founders call.
As part of the economic terms structured within the proposal, the Aave Decentralized Autonomous Organization would stand to benefit substantially from the integration. Specifically, the Aave DAO would receive the first $500,000 in qualifying annual revenue generated by the native Bitcoin integration, aligning the financial interests of both protocols and providing a direct economic incentive for the Aave ecosystem to adopt the new vault technology.
The introduction of native Bitcoin collateral represents a potentially major evolution for Aave, which already supports various forms of lending against tokenized Bitcoin through assets such as Wrapped Bitcoin and Coinbase Wrapped Bitcoin, commonly referred to as cbBTC. While these existing wrapped products have successfully unlocked billions of dollars in liquidity for Bitcoin holders within decentralized finance, they inherently rely on centralized or federated custodians to hold and secure the underlying physical Bitcoin. This reliance on third-party custodians introduces counterparty risks, potential regulatory vulnerabilities, and single points of failure that have long been a subject of discussion and concern among purists within the cryptocurrency community. By utilizing Babylon’s trustless vaults, the proposed integration aims to mitigate these counterparty concerns by keeping the core asset on the Bitcoin blockchain itself.
As of Thursday, the proposal remains actively situated at the Aave Request for Comment stage. During this critical phase of the governance lifecycle, the proposal is undergoing rigorous community feedback, technical scrutiny, and comprehensive risk analysis from risk management entities associated with the Aave protocol. This evaluation period is essential to ensure that the integration of a new collateral type—particularly one originating from outside the Ethereum and EVM-compatible ecosystems—does not introduce unforeseen systemic risks to Aave’s liquidity pools and lending markets.
Should the proposal successfully navigate the risk assessment and reach a broad community consensus, it will be eligible to proceed to the next phases of Aave’s established governance framework. This next step involves a three-day offchain Snapshot vote. According to Aave’s governance rules, this offchain voting procedure requires at least 320,000 AAVE-equivalent votes in favor before the initiative can advance to a formal onchain vote. Once it clears the offchain threshold, the proposal must then pass a formal onchain vote, which is subject to strict quorum requirements and approval thresholds to ensure that token holders have thoroughly endorsed the integration before any code changes or market deployments are finalized.
