Babylon's Trustless Bitcoin Vaults (TBV) stopped being a slide deck this week. The first use case, native BTC-backed borrowing on Aave v4, is live on a public testnet. No allowlist. You can run the whole loop yourself with test coins.

Here's the path, start to finish. Grab test BTC from the faucet (it's Signet, not real money). Connect a wallet. Create a vault and deposit your native BTC. That deposit locks into a Taproot script on Bitcoin itself. It doesn't get wrapped, it doesn't get shipped to Ethereum. Then you wait. The peg-in isn't instant. Babylon says it's trimmed that wait to around three hours and cut on-chain fees more than threefold, but it's still Bitcoin block time, not a loading spinner.

Once the vault is active, its collateral state shows up as a verifiable record on Ethereum. That's what Aave v4 reads through the new Babylon lending spoke. You borrow USDC or USDT against BTC that never left the Bitcoin network. Repay, and the vault releases your coins.

I didn't want to just say "go try the testnet," so I sat down today and traced the full path, faucet to borrow, before writing any of this. The part that stuck with me wasn't the borrow. It was the peg-in wait. On testnet nobody minds a three-hour lock. On mainnet, with real BTC, that window is exactly where you'd want to understand what's happening under the hood, and testnet timing won't tell you how it behaves when the network is busy.

So treat this as a dry run, not a verdict. Test coins, your own hands, nothing at risk. The feedback form at the end actually reaches the team. If "native BTC collateral" has sounded like a buzzword to you, twenty minutes on the TBV testnet is the cheapest way to decide for yourself.

@BabylonLabs_io $BABY #baby

Not financial advice. Do your own research.