The whole pitch was no wrapped Bitcoin. Then I read the liquidation design in Babylon's own Aave proposal and found WBTC sitting right in the middle of it.
Babylon's Trustless Bitcoin Vaults lock BTC in a Taproot UTXO on Bitcoin itself, no bridges, no custodians. That part of the pitch holds up fine.
Liquidations are routine events in any lending market, not emergencies, and Bitcoin's settlement speed cannot keep pace with routine. So permissionless liquidators swap the seized vault for WBTC at a small premium to settle debt right away.
A separate group of permissioned arbitrageurs redeems the actual Bitcoin afterward, on Bitcoin's own timing. Two assets, two speeds, working in sequence rather than at odds with each other.
I checked why they built it this way instead of avoiding WBTC entirely. The proposal says it plainly, this is meant to boost borrowing demand for the five billion dollars in WBTC already supplied to Aave but underused on the borrow side.
I wanted to see if anyone inside Aave pushed back on that dependency before I judged it myself. A technical service provider at Aave Labs called the design consistent with the V4 Hub and Spoke architecture, and Aave's own founder publicly backed the proposal without flagging the WBTC step as a concern.
That told me something. People closer to the mechanics than I am read this as a reasonable tradeoff, not a hidden flaw.
I still think the framing deserves a second look though. No wrapped Bitcoin is the headline, and no wrapped Bitcoin except during settlement is the actual mechanism, and those are two different claims even if the second one is defensible.
@BabylonLabs_io #baby $BABY
Babylon's Trustless Bitcoin Vaults lock BTC in a Taproot UTXO on Bitcoin itself, no bridges, no custodians. That part of the pitch holds up fine.
Liquidations are routine events in any lending market, not emergencies, and Bitcoin's settlement speed cannot keep pace with routine. So permissionless liquidators swap the seized vault for WBTC at a small premium to settle debt right away.
A separate group of permissioned arbitrageurs redeems the actual Bitcoin afterward, on Bitcoin's own timing. Two assets, two speeds, working in sequence rather than at odds with each other.
I checked why they built it this way instead of avoiding WBTC entirely. The proposal says it plainly, this is meant to boost borrowing demand for the five billion dollars in WBTC already supplied to Aave but underused on the borrow side.
I wanted to see if anyone inside Aave pushed back on that dependency before I judged it myself. A technical service provider at Aave Labs called the design consistent with the V4 Hub and Spoke architecture, and Aave's own founder publicly backed the proposal without flagging the WBTC step as a concern.
That told me something. People closer to the mechanics than I am read this as a reasonable tradeoff, not a hidden flaw.
I still think the framing deserves a second look though. No wrapped Bitcoin is the headline, and no wrapped Bitcoin except during settlement is the actual mechanism, and those are two different claims even if the second one is defensible.
@BabylonLabs_io #baby $BABY