I keep thinking about how much of TBV's design is really just working around a limitation everyone in Bitcoin already knows about: Bitcoin's scripting language doesn't support covenants, the mechanisms that would let you constrain how funds get spent in the future. That absence is why bridges have historically needed operators and signer committees at all. TBV's answer is different. The BTC gets locked in a Taproot UTXO on Bitcoin from deposit through redemption, with spending governed by script conditions rather than a party holding the keys. Redemption itself depends on on-chain rules, like whether a loan's been repaid, and settlement returns BTC directly to a UTXO controlled by whoever is redeeming. Nothing custodial happens in between. That's a meaningfully different lifecycle than a bridge, where the asset briefly becomes someone else's problem to hold honestly. What I don't know yet is how gracefully this handles edge cases, disputed claims, contested redemptions, the messier real-world paths. Script conditions are precise until reality is ambiguous. I'm watching how the fraud-proof window performs under an actual contested claim, not a theoretical one.

@BabylonLabs_io #baby $BABY