Babylon advances native Bitcoin lending proposal on Aave V4
Reported by Cointelegraph · AI-assisted summary by ChikoCorp AI News Desk

AI-generated summary based on the linked source; not independently verified. This is not investment advice. Verify market-moving details at the original publisher before acting. See our editorial policy, AI content policy, and financial disclaimer.
Summary
Babylon Labs, a Bitcoin-focused developer, has submitted a proposal to Aave to enable users to borrow stablecoins on Aave by locking native Bitcoin (BTC) in vaults on the Bitcoin network. Instead of bridging or wrapping BTC, collateral would be represented by a non-transferable token on Ethereum while the BTC remains on its native blockchain. The proposal is currently at the Request for Comment stage and has undergone preliminary voting within the community.
Why it matters
The proposal aims to allow borrowing against native BTC without relying on wrapped tokens, which currently introduce counterparty risks due to custodians holding the underlying Bitcoin. This could represent a new, potentially safer method for Bitcoin-backed lending on Aave. The source does not explicitly state the broader market or policy impact.
Key context
Aave traditionally supports loans against tokenized Bitcoin like Wrapped Bitcoin (WBTC) and Coinbase Wrapped Bitcoin (cbBTC), which involve custodians holding BTC and thus entail counterparty risks. Babylon Labs’ proposal, by keeping BTC on its native blockchain and using a non-transferable Ethereum token to represent collateral, seeks to avoid these risks. The proposal follows an initial submission on May 25 and a community vote that passed on June 10.
Key numbers and entities
The Aave DAO would receive the first $500,000 in qualifying annual revenue from this integration. The proposal requires at least 320,000 AAVE-equivalent votes to advance from the offchain Snapshot vote to a formal onchain vote. Babylon Labs and Aave are the key organizations mentioned.
What remains unclear
Details on the technical implementation, how risks would be managed, the timeline for the proposal’s full approval, and the specific mechanisms of the non-transferable token are not provided. The eventual economic or user impact remains unspecified in the source.