Entropy — The Randomness That Guards Your Keys
From The Weekly BOLT ·
Last week we examined how Bitcoin's rules resist change, using the failed BIP-110 fork as a live case study. This week we turn from the protocol to the individual, prompted by the most serious self-custody incident in years: the ongoing exploit of Coldcard hardware wallets, which has drained well over $100 million from thousands of wallets since late July. The story sounds like an indictment of self-custody. Understood properly, it's the opposite — but only if you understand the concept at its center, which is entropy.
The Basics: When you create a Bitcoin wallet, the device generates a seed — the master secret from which every private key, and therefore every address you'll ever control, is mathematically derived. That seed is just a very large random number, usually presented to you as a 12- or 24-word recovery phrase. Bitcoin's security rests entirely on that number being genuinely unpredictable. "Entropy" is the technical term for how much true randomness went into generating it, measured in bits. A properly generated seed carries 128 or 256 bits of entropy, meaning the number of possible seeds is 2 raised to that power — a figure so vast that searching it exhaustively is beyond any conceivable computer. Your bitcoin isn't protected by a password someone might guess. It's protected by the sheer size of the number space your key was drawn from.
Why It Matters: Cryptography has a brutal property: it fails silently. A key generated with insufficient entropy looks identical to a properly generated one. It produces valid addresses, receives coins, signs transactions, and gives no indication of weakness — right up until someone with the right tools searches the reduced space and finds it. This is precisely what happened here. Reporting indicates that a firmware update from March 2021 caused certain devices to draw seed material from a weak software fallback rather than the hardware random-number generator they were designed to use. The practical effect was to collapse the effective security of affected units from an intended 128 bits down to roughly 40 bits. That difference is not incremental — it is the difference between a number space no machine can search and one that modern computing can grind through. Attackers were able to regenerate users' private keys without ever touching the physical device, then drain the coins. Notably, this was not phishing, and users did nothing wrong.
The Long-Term Lesson: The practical takeaways are worth stating plainly. Diversify your custody approach rather than concentrating everything behind a single device or vendor. Understand that hardware wallets from reputable manufacturers use dedicated hardware random-number generators precisely because software randomness is difficult to get right, and that this incident stemmed from a fallback that bypassed that hardware. Consider generating seeds through methods you can independently verify — dice rolls and coin flips are genuinely used for this purpose, and the fact that you can verify your own entropy is a feature no traditional financial system offers. Keep firmware current, but treat any update to the key-generation path as a moment for extra caution. And for large holdings, multi-signature arrangements that require keys from multiple independent devices mean no single vendor's flaw can drain you. The deeper point is the one that has run through this entire series: Bitcoin hands you genuine sovereignty over your wealth, and sovereignty comes with genuine responsibility. This week's episode was a costly reminder that the responsibility is real — and also a demonstration that the underlying system, and every properly secured coin within it, held up exactly as designed.