i used to assume a Vault Provider in Babylon was basically another name for a custodian.
after reading the vault creation docs, i realised that's not actually how the role works.

the Vault Provider coordinates things like proof material, pre-signed transactions and redemption, but it never controls the BTC itself. the Bitcoin spend conditions are fixed when the vault is created, so the provider's job is operational rather than custodial. even if a provider later becomes unavailable, the protocol still includes a depositor self-claim path to recover the BTC. �
Create a vault Babylon Docs.pdf
that also changed how i think about the $BABY ecosystem.
instead of building trust around a company or operator, Babylon is trying to build trust around predefined protocol rules. for me, that's a much more interesting direction because it reduces the importance of who is coordinating and increases the importance of how the protocol is designed.
do you think removing operational trust is just as important as removing custody risk?
@BabylonLabs_io $BABY #baby

Is reducing operational trust as important as removing custody risk in Babylon's Trustless Bitcoin Vaults (TBV)?