Welcome to the next crypto level
← Nexorena

DeFi & stablecoins

Aave DAO backs adding native Bitcoin as collateral in Aave V4

The advisory vote on integrating Babylon’s Bitcoin vaults into Aave V4 closed on November 9 at 14:03 UTC. Snapshot lists 76 votes and a final score entirely in favor. The proposal would allow users to borrow stablecoins against Bitcoin locked on its original network. The vote does not activate the system.

Nexorena Editorial Team

Aave DAO backs adding native Bitcoin as collateral in Aave V4

A vote in favor of Babylon’s proposal

On Snapshot, the affirmative choice received roughly 356,881 units of voting power. Both the opposition and abstention choices recorded zero. The 76 votes shown by the platform are the ballots recorded. The score is a weighted measure of voting power and does not equal the number of people. The consultation concerned an advanced request for comments, known as an ARFC in Aave governance. It followed an earlier vote in principle in favor of the same project.

Babylon Labs proposes using its Bitcoin vaults with Aave V4 on Ethereum. A borrower would lock BTC on Bitcoin in an output protected by a Taproot script. A record of that collateral would appear on Ethereum so Aave could account for the position. The Bitcoin posted as collateral would remain on its own network. The unit created for Aave accounting would be a transfer-restricted token that could not be used outside the contracts designated for the integration.

Liquidation settlement spans two networks

The proposal calls for two modules, or Spokes. The first would host positions backed by the vaults and allow borrowed assets to be drawn from an Aave liquidity pool. BTC would be its only eligible collateral. The second would facilitate liquidation settlement. A liquidator could receive tokenized Bitcoin, initially WBTC, without waiting for the position to settle on Bitcoin. WBTC would serve as an intermediate settlement asset in the liquidation.

Arbitrageurs with the required rights could then take over the relevant vaults by repaying the associated debt and reclaim the BTC on Bitcoin under the script’s terms. The proposal includes a challenge period for withdrawal claims, which can delay settlement on Bitcoin by several days. The delay explains why the two steps are separate. It also highlights the role of available WBTC liquidity and participants authorized to take over vaults.

Deployment and risk parameters still need confirmation

LlamaRisk recommended a collateral supply cap of 300 BTC and caps of 5 million each for USDT and USDC and 1 million for GHO in the proposed dedicated liquidity pool. Those figures are recommendations from the risk service provider. The Snapshot vote does not establish that the limits have been entered into active contracts or that deposits are already possible.

Aave Labs says in the governance thread that it is reviewing the security of contracts specific to the integration. The next key evidence will be the publication of parameters actually adopted and proof that the system is live. The November 9 vote sets a direction for governance. Final borrowing terms, market opening, and the system’s behavior during liquidation remain to be established.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena