Passphrase unavailable — software wallet (2013)
IndeterminateWallet passphrase was unavailable — whether access was ultimately recovered is not known.
In December 2013, BitcoinTalk user goldbishop posted in the encrypted wallet recovery forum that two altcoin wallets—one holding Protoshares (PTS) and another holding Datacoin (DTC)—had become inaccessible. Both wallets were encrypted with an identical password that the user had copy-pasted directly from a Wikipedia article, chosen as a mnemonic device for creating a long, difficult-to-guess passphrase. When goldbishop attempted to unlock the wallets, the stored password no longer worked, despite the user's stated certainty that the copied text was correct. The user suspected a spacing or invisible character issue introduced during copy-paste.
Community member Revalin offered a critical diagnosis: the Wikipedia page itself had likely been edited after the password was created, meaning the source text had changed between the time of wallet encryption and the unlock attempt. This scenario represented an unusual but not unique failure mode in early Bitcoin custody practice. Some users in the 2013 era chose passphrases from arbitrary text sources—Wikipedia articles, song lyrics, book passages—as a method of creating memorable yet cryptographically strong passwords. The practice was technically sound in isolation but introduced a novel risk: if the source was dynamic rather than static (a live web page versus a memorized string or archived copy), the source could change, rendering the password unusable.
Revalin provided a double-typo recovery Ruby script to assist with recovery attempts. No confirmed outcome was posted to the thread, leaving the final disposition of the PTS and DTC holdings unknown. The case documents an early-stage custody literacy gap: the conflation of a passphrase creation method with a passphrase backup method.
| Stress condition | Passphrase unavailable |
| Custody system | Software wallet |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2013 |
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