COLDCARD Seed-Generation Flaw Triggers a Mass Bitcoin Theft and Emergency Wallet Migration

On July 30, Bitcoin users and developers identified a severe vulnerability affecting wallets whose seed material had been generated by certain COLDCARD hardware-signing devices. Bitcoin Optech reported that some users had discovered unexpected theft transactions from the previous day and that affected Mk3 seeds generated without supplemental dice rolls could have roughly 40 bits of effective entropy instead of the intended 128. Researchers were able to reproduce the weakness quickly, and affected seeds had to be treated as compromised rather than merely “patched.”

The security failure cut directly into Bitcoin’s self-custody model. Users can follow the usual discipline—keep a seed offline, never expose it to a computer, and store funds behind a dedicated signing device—and still fail if the device itself creates a secret with insufficient randomness. That distinction made the event more consequential than an ordinary wallet bug. The vulnerability attacked the assumption that properly generated private keys are unknowable, which is the foundation on which self-custody rests.

The response was correspondingly urgent. Users were told to move funds to wallets created with unaffected entropy and not to assume that a firmware upgrade could make an already weak seed safe. Bitcoin-native programs treated the incident as an emergency, reflecting a broader confidence problem rather than a narrow implementation issue. The initial July event belongs separately from the August phase, when losses expanded and the episode developed into a wider self-custody confidence crisis.

The historical lesson is uncomfortable but central to Bitcoin’s use case: removing a bank or custodian does not remove trust entirely. Self-custody shifts trust toward hardware, randomness, software supply chains, backup procedures, and the user’s own operational choices. COLDCARD’s failure made that hidden dependency visible on a large scale.