CustodyStress
Archive › Browse by trigger and stress condition › Forgotten Passphrase — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Forgotten_passphrasePassphrase unavailable

Forgotten Passphrase — Passphrase unavailable

Cases where a forgotten passphrase was the specific trigger for a passphrase-unavailable stress condition. The passphrase existed but the holder could not recall it — distinct from passphrases never recorded or lost after recording.

104 cases in this intersection. 46% of determinate cases resulted in a blocked outcome and 43% in access survived. The most common recovery path is password bruteforce.

17
Blocked
4
Constrained
16
Survived
67
Indeterminate

57% of determinate cases resulted in blocked or constrained access.

104 observed cases
Blocked
17 (16%)
Constrained
4 (4%)
Survived
16 (15%)
Indeterminate
67 (64%)
BitcoinTalk User ez1btc: Encryption Password Transcription Error Blocks Large Bitcoin Wallet
Software wallet
Indeterminate 2012
In the encrypted wallet recovery thread on BitcoinTalk, user 'ez1btc' documented a custody failure rooted in transcription error rather than forgetfulness. At t
Anonymous Reddit User: 7,500 BTC Inaccessible Due to Forgotten Wallet Password
Software wallet
Blocked 2012
An anonymous Reddit user posted in 2014 about a significant custody failure: he had purchased approximately 7,500 Bitcoin in 2012 and stored them in an encrypte
Fiyasko's Forgotten Passphrase: Mining Savings Lost to Single Point of Failure (2012)
Software wallet
Indeterminate 2012
In December 2012, a Bitcoin miner operating under the username Fiyasko (also known as JackRabiit) created a dedicated savings wallet to store one month of accum
Brainwallet Passphrase Mismatch — Address Generation Failure After Fund Transfer
Software wallet
Indeterminate 2012
In December 2012, a BitcoinTalk user identified as 'thoughtfan' encountered a critical custody failure after using brainwallet.org to generate a Bitcoin address
Stefan Thomas and 7,002 Bitcoin: Locked Behind a Forgotten Passphrase
Hardware wallet (single key)
Blocked 2011
Stefan Thomas held 7,002 Bitcoin stored on an encrypted hard drive containing the private keys. Access to the device required a passphrase that Thomas had forgo
Bitcointalk User Locked Out of Encrypted 2011 Wallet — Passphrase Unrecoverable
Software wallet
Blocked 2011
In early 2013, a Bitcointalk user posted in the Bitcoin Technical Support section describing their inability to access an encrypted wallet created approximately
Brad Yasar: Early Miner Locks Out Thousands of BTC Across Multiple Drives
Software wallet
Blocked 2011
Brad Yasar, a Los Angeles-based entrepreneur, mined thousands of Bitcoin on several desktop computers during the earliest years of the network when solo mining
2010 Mining Pool Wallet.dat: Passphrase Lost After Decade of Storage
Software wallet
Indeterminate 2010
Between 2010 and 2011, the source participated in Bitcoin pool mining and retained the resulting wallet.dat file on a local system. The wallet remained untouche
Kristoffer Koch Recovers 5000 BTC After Forgotten Wallet Password — 2013
Software wallet
Survived 2009
Kristoffer Koch, a Norwegian engineering student, encountered Bitcoin in late 2009 while researching encryption for his university thesis. Intrigued by the emer
7500 BTC Permanently Locked on IronKey Device After Passphrase Loss
Hardware wallet with passphrase
Blocked
A British engineer encrypted approximately 7500 BTC on an IronKey device, a third-party encrypted storage solution designed with progressive lockout mechanisms
Forgotten Electrum Wallet and Zip Archive Passwords — Multiple Encrypted Backups Inaccessible
Software wallet
Indeterminate
In December 2024, a BitcoinTalk user identified as 'fanya' disclosed a multi-year custody failure rooted in encryption key loss rather than theft or technical c
Forgotten Bitcoin Wallet Passphrases: Forum Cases of Successful Third-Party Recovery (2014–2021)
Software wallet
Survived
Between 2014 and 2021, seven Bitcoin holders posted testimonials on a forum documenting their recovery of wallets encrypted with forgotten passphrases. Cases ra
Armory 0.88.1 Wallet Passphrase Loss: 50 BTC Access Blocked
Software wallet
Indeterminate
A BitcoinTalk user posting as vect0rz reported losing access to an Armory version 0.88.1 wallet containing over 50 BTC. The encrypted wallet file and chain code
Stefan Thomas: 7,200 Bitcoin Inaccessible Behind IronKey Passphrase
Hardware wallet with passphrase
Blocked
Stefan Thomas, former Chief Technology Officer of Ripple, stored 7,200 BTC on an IronKey encrypted hard drive. The drive implemented a deliberate security const
Second Password Lost on Blockchain.com Wallet: 0.34 BTC Inaccessible for 8 Years
Exchange custody
Blocked
Approximately eight years before disclosure, the user created a Blockchain.com hosted wallet using the platform's dual-password security model. This architectur
TrueCrypt-Encrypted Wallet.dat: Partial Passphrase, Uncertain Recovery Path
Software wallet
Indeterminate
A Bitcoin and Litecoin miner from the early 2014 era encrypted his wallet.dat file inside a TrueCrypt volume, motivated by security paranoia despite acknowledgi
Passphrase Recovery Success and OPSEC Failure: 2014 WalletRecoveryServices Case
Software wallet
Survived
A Bitcoin holder in 2014 created private keys but lost the passphrase required to access them. The funds remained locked for an unknown duration until the owner
241 BTC Trezor Custody Loss: Forgotten PIN and Failed Seed Recovery
Hardware wallet (single key)
Indeterminate
A Bitcoin holder transferred 241 BTC to a Trezor hardware wallet in late 2015, securing it with a 9-digit PIN. The user documented the seed phrase and initially
BIP38 Paper Wallet: Seven-Year Inaccessibility Resolved via Single-Character Error
Software wallet
Survived
In 2017, an individual encrypted a paper wallet using BIP38 encryption, protecting it with a passphrase derived from their favorite band—a mnemonic they believe
Second Password Lost on Blockchain.info — 0.3 BTC Rendered Inaccessible
Exchange custody
Blocked
A Bitcoin holder maintained approximately 0.3 BTC on Blockchain.info, a popular web-based wallet service that was standard during the early-to-mid 2010s. The ac
1 BTC Locked Behind Forgotten Electrum Passphrase: Professional Cracking Effort Failed
Software wallet
Blocked
A Reddit user received 1 BTC and secured it using Electrum, a popular Bitcoin desktop wallet, with a password-protected encrypted file. The user later forgot th
Stefan Thomas: 7,002 Bitcoin on IronKey S200, Passphrase Lost, 2 Attempts Remaining
Hardware wallet with passphrase
Blocked
Stefan Thomas possessed an IronKey S200 USB drive containing the private keys to 7,002 Bitcoin, worth approximately $235 million at the time of public reporting
Stefan Thomas and the IronKey Trap: 7,002 Bitcoin, 2 Attempts Left
Hardware wallet (single key)
Indeterminate
Stefan Thomas, a programmer, received 7,002 BTC in 2011 as payment for creating an animated educational video about Bitcoin. He stored the private keys on an Ir
Developer Locked Out of $240 Million Bitcoin After Forgetting Hardware Wallet Passphrase
Hardware wallet with passphrase
Blocked
A cryptocurrency developer became unable to access approximately $240 million in Bitcoin stored on a hardware wallet after forgetting the device's passphrase. T
IronKey Password Recovery: Developer Regains Access to $240M Bitcoin
Hardware wallet with passphrase
Survived
In the early 2010s, a software developer stored Bitcoin on an IronKey encrypted USB drive, securing it with a passphrase generated by RoboForm password manager.
← PreviousNext →
Browse by trigger and stress condition
Terms guide
Survived
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
Archive inclusion criteria

This archive documents cases where a legitimate owner, heir, or authorized party encountered barriers accessing or recovering Bitcoin due to a failure in the custody arrangement. The central question for inclusion is: did the custody structure fail a legitimate access or recovery attempt?

A case must satisfy all three of the following to be included:

  1. Legitimate access attempt. The person attempting to access or recover the Bitcoin was the owner, a designated heir, an executor, a legal authority, or another party with a legitimate claim — not a thief, attacker, or unauthorized third party.
  2. Custody structure failure. The failure was caused by a property of the custody arrangement — missing credentials, structural dependencies, documentation gaps, knowledge concentration, legal barriers, or institutional constraints — not market conditions, individual-level fraud or theft, or protocol-level issues. Platform-level failures that block legitimate user access are in scope regardless of their cause.
  3. Documentable outcome or access constraint. The case must have a stated or inferable outcome: access blocked, access constrained, access delayed, or access eventually achieved through a recovery path. Cases with entirely unknown outcomes are included only where the structural failure is documented and the constraint is unambiguous.
  • Owner death or incapacity — Bitcoin held in self-custody that becomes inaccessible to heirs or designated parties because credentials, documentation, or operational knowledge were not transferred
  • Passphrase loss — BIP39 passphrase forgotten or unavailable, blocking access to a funded wallet even where the seed phrase is present
  • Seed phrase or wallet backup unavailable — no independent recovery path existed or the backup was destroyed, lost, or never created
  • Device loss without independent backup — hardware wallet, phone, or computer lost or destroyed with no recovery path outside the device
  • Documentation absent or ambiguous — heirs or executors cannot determine that Bitcoin exists, which wallet holds it, or how to access it
  • Knowledge concentration — only one person knew the procedure, passphrase, or access method; that person is dead, incapacitated, or unreachable
  • Multisig quorum failure — a threshold signature arrangement cannot be completed because signers are unavailable, uncooperative, incapacitated, or have lost their keys
  • Legal authority / access mismatch — a court order, probate ruling, or power of attorney establishes legal entitlement but provides no technical path to access
  • Institutional custody barrier — exchange or platform hacks, insolvency, regulatory seizure, or operational failure that caused a access constraint or failure for legitimate users, whether temporary, prolonged, or permanent. The failure of the custodian to remain available or solvent is itself the in-scope event.
  • Forced relocation or geographic constraint — physical access to a device or location required for recovery is blocked by displacement, border restrictions, or political circumstances
  • Coercion — the holder was compelled under threat to transfer Bitcoin or disclose credentials during an access event
  • Hidden asset discovery — heirs or executors locate a wallet or account but cannot access it due to missing credentials or operational knowledge
  • Market losses, investment losses, yield scheme losses, or Ponzi scheme losses
  • Hacks or theft targeting an individual's personal security (phishing, SIM swap, social engineering, malware) where the custody architecture itself did not fail
  • Unauthorized transfers where the holder's custody system was not the cause of the failure
  • Ordinary transaction mistakes — wrong-address sends, fee errors, mistaken amounts
  • Protocol-level failures — cryptographic vulnerabilities, consensus bugs, firmware integrity failures
  • Deliberate burns or tribute burns
  • Cases where the stated loss is unverifiable and no structural custody failure is described

Cases are drawn from public sources including forum posts, news reporting, court documents, academic research, and direct submissions. Each case is reviewed against the inclusion criteria above before publication. Source material is retained and available on request for documented cases.

The archive is observational and descriptive. It does not attempt to document all Bitcoin custody failures — only those meeting the criteria above with sufficient documentation to describe the structural failure and its outcome.