Second Password Lost on Blockchain.com Wallet: 0.34 BTC Inaccessible for 8 Years
BlockedWallet passphrase could not be recalled or recovered — access was permanently blocked.
Approximately eight years before disclosure, the user created a Blockchain.com hosted wallet using the platform's dual-password security model. This architecture required both a primary password for account login and a secondary password—functionally equivalent to a PIN or transaction authorization code—to execute any outbound transfer. The user lost the secondary password and did not maintain a backup or recovery record.
At the time of the password loss, the wallet held 0.34 BTC, a balance the user did not regard as significant. Over the subsequent eight years, Bitcoin appreciated substantially, transforming the inaccessible holdings into a meaningful asset. The user retained continuous login access to the account and could view the wallet balance and full transaction history, but remained unable to initiate any send operation without the missing second password.
This created a jurisdictional custody trap: the funds were neither lost to the user nor accessible for use. The user contacted Blockchain.com support seeking recovery assistance. The platform declined to intervene, citing institutional policy limitations on password recovery procedures. Support offered a referral to an external third-party recovery service but provided no endorsement or verification of the service's legitimacy.
The user expressed documented skepticism about the trustworthiness of the external recovery service and hesitated to engage with it. Community responses on the user's public forum post emphasized the prevalence of social engineering attacks and scams targeting individuals known to hold inaccessible Bitcoin, cautioning against unsolicited direct contact from recovery operators.
No resolution was documented. The user remained uncertain whether any legitimate technical recovery mechanism existed or whether the funds should be accepted as permanently lost.
| Stress condition | Passphrase unavailable |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Partial |
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.