At first I assumed vault activation in Trustless Bitcoin Vaults (TBV) was coordinated the boring way, some service watching both chains and flipping a switch when things line up. Thats the part I got wrong, and the actual mechanism is better than I expected. At peg-in the depositor generates a 32-byte secret and submits only its SHA-256 hash to the vault registry on Ethereum. The bitcoin they deposit gets locked into a Taproot address committed to that same hashlock. Two chains, one fingerprint, and neither side has moved yet.
Activation is the depositor revealing the secret on Ethereum. That single reveal does two things at once, the Ethereum contract verifies the preimage and registers the collateral as live, and the revealed secret becomes the missing piece of the witness for the final PegIn transaction on bitcoin. The Vault Provider just picks the secret up from the public reveal and constructs the broadcast. No coordinator decides the moment. The depositor does, becuase only they hold the preimage.
So the binding between chains isnt a message or an oracle, its a piece of math only one person can complete. I keep coming back to how small the trust surface is there. One secret, held by the one party who should control the timing anyway.
#baby @BabylonLabs_io $BABY
Activation is the depositor revealing the secret on Ethereum. That single reveal does two things at once, the Ethereum contract verifies the preimage and registers the collateral as live, and the revealed secret becomes the missing piece of the witness for the final PegIn transaction on bitcoin. The Vault Provider just picks the secret up from the public reveal and constructs the broadcast. No coordinator decides the moment. The depositor does, becuase only they hold the preimage.
So the binding between chains isnt a message or an oracle, its a piece of math only one person can complete. I keep coming back to how small the trust surface is there. One secret, held by the one party who should control the timing anyway.
#baby @BabylonLabs_io $BABY