Passphrase unavailable — exchange custody, unknown (2019)
BlockedWallet passphrase could not be recalled or recovered — access was permanently blocked.
A 2019 BitcoinTalk thread documented a recurring custody failure pattern affecting blockchain.com (formerly blockchain.info) users from the 2011–2014 era. The original poster described a friend who created a blockchain.com wallet in 2013, accumulated significant holdings, but lost the associated password. When attempting account recovery, the friend discovered that the email provider used for the account had ceased operations, eliminating the only recovery mechanism blockchain.com offered: password reset via email backup. The platform design stored wallet IDs and JSON-format encrypted backups server-side but required the user's email to initiate recovery. With the email account inaccessible and the password forgotten, no recovery path existed.
A second user reported a similar scenario from the faucet-claiming era (circa 2013–2014). He accumulated what he described as 'a big amount of faucet rewards' in a blockchain.com wallet but lost the JSON backup file. Despite searching his hard drive, he could not locate it. He noted that blockchain.com later removed the email login requirement, but this change did not unlock his account, as the password remained unknown.
A third user reported losing access to an early blockchain.info wallet holding approximately 10,000 satoshis after misplacing the written password record.
Community responses from technically knowledgeable users (NeuroticFish, o_e_l_e_o) confirmed that blockchain.com does not retain unencrypted access to user private keys. The coins are cryptographically locked by AES-256 encryption; recovery is only possible through password recovery or computationally infeasible brute-force attack. The thread consensus was that such coins are permanently lost. This pattern reflects a broader custody risk of the early web wallet era: users who did not maintain offline backups, did not record credentials in secure offline storage, and relied on email recovery faced irreversible loss if either the password or the recovery email became unavailable.
| Stress condition | Passphrase unavailable |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Present and interpretable |
| Year observed | 2019 |
| 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