I deposited into TBV testnet expecting the vault to go live the moment my transaction confirmed. It didn't. There was a wait I hadn't planned for, and figuring out why changed how I think about the whole flow.
A peg-in isn't "live" after one Bitcoin confirmation. TBV needs enough confirmations stacked on top before the vault is treated as settled, because a single confirmation can still get reorged off the chain. On an EVM deposit, one block final is basically final. On Bitcoin, one block is a claim, not a settlement — the real guarantee only shows up a few blocks later, once reversing it would mean rewriting real proof-of-work.
Reminded me of a wire transfer showing "pending" in your bank app before it's actually cleared. The number's on the screen immediately, but the bank won't let you touch the funds until it's sure the sender's side can't still bounce.
What surprised me is that TBV can't shortcut this the way a custodian could. A custodian just says "trust me, it's in," and moves on. TBV has no one to say that — it has to wait for Bitcoin to actually settle the claim, because the entire point is not needing anyone's word for it.
So the confirmation wait isn't a UX rough edge that gets optimized away later. It's the cost of skipping a custodian who'd normally absorb that uncertainty for you and just tell you it's fine.
Makes me wonder how many people testing this expect deposit speed to eventually match a normal DeFi app, versus realizing that wait is actually the trustless part working correctly, not a bug waiting to be fixed.
@BabylonLabs_io $BABY #baby $BLESS $TAKE #Babylon
A peg-in isn't "live" after one Bitcoin confirmation. TBV needs enough confirmations stacked on top before the vault is treated as settled, because a single confirmation can still get reorged off the chain. On an EVM deposit, one block final is basically final. On Bitcoin, one block is a claim, not a settlement — the real guarantee only shows up a few blocks later, once reversing it would mean rewriting real proof-of-work.
Reminded me of a wire transfer showing "pending" in your bank app before it's actually cleared. The number's on the screen immediately, but the bank won't let you touch the funds until it's sure the sender's side can't still bounce.
What surprised me is that TBV can't shortcut this the way a custodian could. A custodian just says "trust me, it's in," and moves on. TBV has no one to say that — it has to wait for Bitcoin to actually settle the claim, because the entire point is not needing anyone's word for it.
So the confirmation wait isn't a UX rough edge that gets optimized away later. It's the cost of skipping a custodian who'd normally absorb that uncertainty for you and just tell you it's fine.
Makes me wonder how many people testing this expect deposit speed to eventually match a normal DeFi app, versus realizing that wait is actually the trustless part working correctly, not a bug waiting to be fixed.
@BabylonLabs_io $BABY #baby $BLESS $TAKE #Babylon