22.1 BTC Bitcoin-Qt Wallet Password Recovery via Community Brute Force (2014)
SurvivedWallet passphrase was unavailable — a recovery path existed and access was restored.
In November 2014, a Bitcoin-Qt wallet containing 22.1 BTC became inaccessible when its owner forgot the passphrase. The owner had documented the password creation method in a cryptic written clue, which he had emailed to himself. This allowed recovery of approximately 24 of the 25 characters with certainty; the owner knew that position 21 was definitely incorrect and suspected one additional character among the known 24 was also wrong.
This narrowed the search space to approximately 216,600 possible password combinations—a computationally feasible target for contemporary brute-force attacks. On November 12, 2014, the BitcoinTalk user 'spooderman' posted a technical support request on behalf of the wallet owner. The post initially reflected a common misunderstanding: the suggestion that ASIC miners could be repurposed for password cracking. Forum members including DannyHamilton and MCHouston corrected this, explaining that ASICs function only for SHA-256 block hashing, not password derivation functions.
They guided the user toward appropriate tools: custom brute-force software, GPU-based crackers, and AWS compute instances. Spooderman disclosed that he had previously assisted another friend with a similar password recovery using a custom program written by a mutual acquaintance, which had succeeded in 90 minutes after attempting 5 million passwords. A 2.2 BTC bounty was offered (approximately $300–400 USD at November 2014 prices), with funds to be paid from the receiving wallet address 15sZVJHZ8mSL29My2hsBN1njSivuQUPxn6.
By November 14, 2014—two days after the initial post—forum user guitarplinker noted that funds had been moved from the wallet, confirming the password had been successfully recovered. The thread does not explicitly identify who recovered the password or confirm whether the bounty was paid. Blockchain data corroborates that access was regained within 48 hours of the public request.
| Stress condition | Passphrase unavailable |
| Custody system | Software wallet |
| Outcome | Survived |
| Documentation | Present but ambiguous |
| Year observed | 2014 |
| Country | unknown |
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