Aave Proposes Onboarding BTC.b to Aave V4 Core Instance on Ethereum Mainnet
Aave Governance proposes onboarding BTC.b (Avalanche-bridged Bitcoin) to Aave V4 Core Instance on Ethereum Mainnet with 73% LTV and Chainlink oracle integration.

Aave Governance submitted a proposal on August 28, 2026, to onboard BTC.b — Bitcoin-backed collateral on the Avalanche network — to the Aave V4 Core Instance on Ethereum Mainnet. The proposal represents a significant expansion of Bitcoin representation within decentralized lending markets and highlights the growing demand for cross-chain Bitcoin liquidity in DeFi protocols.
BTC.b is a wrapped Bitcoin asset minted through Avalanche's bridge infrastructure, backed by native Bitcoin held in custody. Unlike synthetic Bitcoin derivatives, BTC.b maintains a 1:1 backing with actual Bitcoin reserves, making it functionally similar to other wrapped Bitcoin products like WBTC but operating across Avalanche's subnet architecture before bridging to Ethereum.
Key Metrics at a Glance

| Metric | Detail |
|---|---|
| Proposal Date | August 28, 2026 |
| Governance Forum | Aave Governance |
| Asset | BTC.b (Bitcoin-backed Avalanche bridge asset) |
| Target Market | Aave V4 Core Instance, Ethereum Mainnet |
| Proposed LTV | 73% |
| Liquidation Threshold | 78% |
| Liquidation Penalty | 7.5% |
| Oracle Provider | Chainlink |
| Bitcoin Backing | 1:1 with native Bitcoin reserves |
What the Proposal Actually Does

The governance proposal seeks to add BTC.b as a collateral asset within Aave V4's Core Instance, which is the protocol's primary lending market on Ethereum Mainnet. If approved, users would be able to deposit BTC.b as collateral and borrow against it, or supply BTC.b to earn yield from borrowing demand.
The proposed risk parameters reflect BTC.b's characteristics as a Bitcoin-backed asset. The 73% loan-to-value ratio is conservative relative to some other collateral assets, reflecting the additional bridge and custody risks associated with cross-chain Bitcoin representation. The 78% liquidation threshold provides a modest buffer above the LTV, while the 7.5% liquidation penalty is standard for volatile collateral types.
The proposal includes Chainlink oracle integration for price feeds, which is significant because accurate Bitcoin pricing is essential for safe liquidation mechanics. Chainlink's BTC/USD feed would provide the primary price reference, with additional safeguards through circuit breakers and deviation thresholds.
The Bitcoin Dimension

Bitcoin's role in this proposal is structural rather than direct. BTC.b is not native Bitcoin — it is a representation of Bitcoin on another chain. That distinction matters for risk assessment. The value of BTC.b depends on three factors: the price of native Bitcoin, the security of the Avalanche bridge holding the backing BTC, and the redemption mechanism that allows conversion back to native Bitcoin.
The proposal acknowledges these layers of risk through its conservative parameterization. Aave's risk stewards evaluated BTC.b's bridge history, liquidity profiles across Avalanche and Ethereum, and correlation with native Bitcoin price movements. Their recommendation for a 73% LTV suggests confidence in the asset's price stability but caution regarding bridge and custody risks.
For Bitcoin holders, the proposal creates additional utility for Bitcoin exposure within DeFi lending markets. Rather than selling Bitcoin to access liquidity, holders could deposit BTC.b as collateral and borrow stablecoins against it. That use case preserves Bitcoin price exposure while unlocking dollar-denominated liquidity — a familiar value proposition that has driven wrapped Bitcoin adoption across DeFi protocols.
Market Structure Implications
The BTC.b onboarding creates implications for three market segments: Aave's competitive positioning, Bitcoin bridge infrastructure, and DeFi collateral diversity.
On Aave's competitive positioning, adding BTC.b responds to demand from users who want Bitcoin collateral exposure within Aave's liquid markets. Competing protocols including Compound, Euler, and Morpho already support various forms of wrapped Bitcoin. Aave's inclusion of BTC.b closes a product gap and may attract users who prefer Aave's security model and liquidity depth.
On bridge infrastructure, the proposal validates Avalanche's Bitcoin bridge as sufficiently robust for integration into a top-tier DeFi protocol. That validation creates network effects: if Aave accepts BTC.b, other protocols may follow, increasing demand for Avalanche's bridge infrastructure and potentially strengthening its security through larger economic participation.
On collateral diversity, the proposal expands the range of Bitcoin representations available in DeFi. Bitcoin is already represented by WBTC, tBTC, renBTC (historically), and now BTC.b. Each representation carries different trust assumptions regarding custody, bridge security, and decentralization. The proliferation of options gives users choice but also fragments liquidity across multiple Bitcoin-backed assets.
What Remains Unresolved
The proposal leaves several questions open. First, the governance vote has not concluded at the time of writing. Aave's governance process typically requires a temperature check, formal proposal, and execution through the protocol's multisig. The timeline for activation depends on governance participation and any objections raised during the review period.
Second, the proposal does not address how BTC.b integration might affect Aave's existing wrapped Bitcoin positions, particularly if users migrate from other Bitcoin representations to BTC.b. That migration could affect liquidity and borrowing dynamics across different collateral markets.
Third, the proposal assumes continued reliability of Avalanche's bridge infrastructure. Bridge security remains an active area of risk in cross-chain protocols, and any compromise of the BTC.b backing would immediately affect Aave's collateral valuations and liquidation mechanics.
TL;DR
- What: Aave Governance proposes onboarding BTC.b (Avalanche-bridged Bitcoin) to Aave V4 Core Instance on Ethereum Mainnet
- Why: Expands Bitcoin collateral options in DeFi lending, closes competitive gap with other protocols
- Impact: Creates additional Bitcoin utility in DeFi, validates Avalanche bridge infrastructure, increases collateral diversity
- Bitcoin Connection: BTC.b maintains 1:1 backing with native Bitcoin; conservative 73% LTV reflects bridge and custody risks
- Watch: Governance vote outcome and potential liquidity migration from existing wrapped Bitcoin products
Sources
- Aave Governance Forum Proposal
- Aave V4 Risk Parameters Documentation
- Avalanche Bridge BTC.b Documentation
- Chainlink BTC/USD Price Feed
Filip Peshko is Senior Opinion Columnist & Blockchain Technology Analyst at TotesTek. He writes about Bitcoin, blockchain technology, crypto markets, Web3 infrastructure, digital asset custody, institutional adoption, and legislation affecting the crypto industry.



