Lost Blockchain.info iOS Wallet Password (2014) — Recovery Attempt via BTCRecover
IndeterminateWallet passphrase was unavailable — whether access was ultimately recovered is not known.
In December 2021, a BitcoinTalk user identified as Quix77 disclosed loss of access to a Blockchain.info wallet created in August 2014 via the iOS Blockchain app. The user had forgotten the account password and no longer possessed the original iPhone or the computer used during initial wallet setup. The only remaining artifact was a wallet file (wallet.aes.json) downloaded from the original account email in 2014, which remained accessible in the user's email archive. However, the password reset link embedded in that email was no longer functional.
The user had created a password marked "strong" by the app's built-in password strength advisor, likely containing uppercase letters, lowercase letters, numbers, and punctuation marks. Community analysis of Blockchain.info's archived interface from January 2014 indicated the platform recommended a minimum 10-character password with no explicit character type restrictions, though the strength meter guided users toward complex passwords. Based on historical standards and the user's recollection, community members estimated the actual password was likely 10–11 characters long.
Crucially, the user lacked any recovery phrase—Blockchain.info used 16–20 word recovery phrases during this era that would have enabled password reset through the official forgot-password function at login.blockchain.com/wallet/forgot-password. The user's recovery strategy centered on brute-forcing the wallet.aes.json file using BTCRecover, a specialized password recovery tool, constrained by character sets and length parameters inferred from documented Blockchain.info standards of 2014.
The thread does not disclose whether the user ultimately regained access, the amount of Bitcoin held in the wallet, or the final outcome of the recovery effort. This case illustrates a compound custody failure: loss of the passphrase combined with absence of a documented recovery phrase and loss of access to the devices and email accounts used during wallet creation.
| Stress condition | Passphrase unavailable |
| Custody system | Exchange custody |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2014 |
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.