@BabylonLabs_io Per the documentation on Trustless Bitcoin Vaults (TBV)'s trust model residual trust the parts that aren't fully eliminated falls into two categories governance and emergency response multi sigs.
I'd been treating trustless as close to absolute before reading this framed so specifically. It isn't. It's trustless for the day to day mechanism with two narrow named exceptions sitting behind it.
Governance multi sigs handle protocol level parameter changes the kind of decisions that need some coordinated authority to exist at all. Emergency response multi sigs are the backstop for genuinely catastrophic scenarios the Security Council's domain specifically.
What I find worth sitting with naming these two categories explicitly is more honest than most systems that quietly have similar residual trust points without ever labeling them.
Does naming the exceptions clearly make the overall trustless claim feel stronger to you or does it just relocate where the skepticism should live?
#baby $BABY
I'd been treating trustless as close to absolute before reading this framed so specifically. It isn't. It's trustless for the day to day mechanism with two narrow named exceptions sitting behind it.
Governance multi sigs handle protocol level parameter changes the kind of decisions that need some coordinated authority to exist at all. Emergency response multi sigs are the backstop for genuinely catastrophic scenarios the Security Council's domain specifically.
What I find worth sitting with naming these two categories explicitly is more honest than most systems that quietly have similar residual trust points without ever labeling them.
Does naming the exceptions clearly make the overall trustless claim feel stronger to you or does it just relocate where the skepticism should live?
#baby $BABY