Stefan Thomas: 7,200 Bitcoin Inaccessible Behind IronKey Passphrase
BlockedWallet passphrase could not be recalled or recovered — access was permanently blocked.
Stefan Thomas, former Chief Technology Officer of Ripple, stored 7,200 BTC on an IronKey encrypted hard drive. The drive implemented a deliberate security constraint: only ten login attempts permitted before permanent, irreversible lockout. By 2021, when the case became public, Thomas had exhausted eight attempts over a nine-year recovery effort beginning in 2012. Two attempts remained.
Thomas had no record of the passphrase and no backup seed phrase or recovery key. The wallet existed only on this single device, making the encryption credential the exclusive point of access to approximately $187 million USD in value at the time of disclosure.
Thomas investigated theoretical recovery pathways. Destructive physical access—removing the encrypted chip and using a scanning electron microscope to read flash memory cells—represented the only technical option. He concluded the approach was impractical: specialized expertise would be required, the process would be time-intensive, and success was not guaranteed. Data corruption, unrecoverability, or additional unforeseen obstacles could render the effort futile. While the cost might theoretically justify itself against $187 million in value, no institutional capacity or trusted third party capable of executing such recovery was accessible to him.
By his own account, Thomas eventually made peace with the loss and ceased active recovery attempts. The passphrase remained unknown. No institutional recovery mechanism, no secondary custodian, no documented failover existed. The Bitcoin remained on the device—technically present but functionally inaccessible under any normal operating conditions. The case exemplified a custody structure built entirely on a single authentication credential, with no recovery redundancy and no third-party involvement.
| Stress condition | Passphrase unavailable |
| Custody system | Hardware wallet with passphrase |
| Outcome | Blocked |
| Documentation | Present and interpretable |
Why passphrases fail years after they are set
The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.
What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.
Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.
The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.
Translate