The Trusted Third Parties of a Trustless System

This week, a self-custody Bitcoin wallet lost around $70 million. Not to a hack of the device. Not to a phishing link or a five-dollar wrench attack. The coins were taken because the wallet generated its seeds badly, and roughly 1,200 wallets became guessable. The devices were never touched. They could have been powered off in a safe on another continent, and I’ve read that some were.

Here is the part worth sitting with. That wallet is open source. Anyone could read the code. And it still shipped a build where the one number that was supposed to be unguessable was about as secret as a mother’s maiden name. It complicates the thing Bitcoin says about itself.

“Don’t trust, verify” is the closest thing this ecosystem has to a creed. It’s a solid creed, and the reason any of this matters. But a trust-minimized system has a way of quietly regrowing the very thing it was built to remove, and if you follow the wiring, or ask a lot of questions, you find that some of Bitcoin’s load-bearing trust points sit in remarkably few hands.

Consider that a builder who makes one of the most trusted self-custody devices also runs the website that has become the ledger of record for how many coins the large corporate treasuries hold. Custody and the count, two of the most important trust points in the whole space, are routed through one person. The work is real and beyond impressive, much of it is open, and the person did not appoint himself. The market handed him the authority by citing him.

Now notice that both of those trust points are “verify” in name and trust in practice. The wallet asked you to trust that its seed was sound, and gave you no way to test it. No self-check tells you whether your own key sits inside a guessable range. You trusted. That is not verification.

The treasury scoreboard asks you to trust that the coins are where the filings say. The numbers come from disclosures, announcements, and self-reporting, not from proof of reserves you can check on-chain. Some are at least backed by SEC filings, but a filing verifies a document, not the coins, and for the one asset on earth you can actually verify on-chain, taking a company’s word on paper is a strange thing to settle for. Most of the other entries are just a company saying a number. Almost none publish an address you could verify. When someone tells you how many coins a treasury holds, they are usually citing a trusted third party who was, in turn, citing another one.

The bug lived in a build path that nobody’s eyes were actually on, and it shipped because no test forced the question, and no check a user could run. The failure was not too much openness. It was a verification you could not perform.

Open code is necessary. It is not sufficient. The line to hold is not open versus closed. It is open code and checkable claims, while keeping secret the only thing that must stay secret. You publish the lock and the blueprint, never the key.

The same principle scales up from the device to the scoreboard. If corporate treasuries want to be believed, they can prove their reserves on-chain instead of asking the rest of us to trust a filing and a website. “Verify” should mean you can check it yourself, not that someone appointed trustworthy checked it for you and you are taking their word for it. Eff that. Seriously.

Bitcoin did not abolish trust. It made trust optional in the places where we bother to build the tools that let people verify. Everywhere we skip that work, we have quietly reappointed a trusted third party, and this week, one of them failed in public, in front of everyone, for $70 million.

The answer is not to close the code and hope no one looks. It is to open it further and give people something real to look at. Publish the code. Publish the proof. Let the eyes do what the eyes are for. Do the work. Do it for Bitcoin.

Here is ours. The library that generates our seeds, keys, and signatures is open and in public. Read it, question it, tell us what we missed please.

https://github.com/CadenaWizard/cryptlib

Disclosure: I’ve had commercial relations with BitcoinTreasuries.net, and hope to have moar in the future. I hold the creator’s work and the entire team in high regard. I am not anti Bitcoin Treasury companies, I am pro on-chain proof of reserves.

Follow us on socials:

X: https://x.com/cadenabitcoin

GitHub: https://github.com/CadenaWizard/oracle

YouTube: https://youtube.com/@cadenabitcoin?si=VNgOLehpTTVFELbt