CustodyStress
Archive › Browse by outcome and stress › Blocked — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
BlockedPassphrase unavailable

Blocked — Passphrase unavailable

Cases where a wallet became permanently inaccessible because the passphrase was unavailable. A passphrase-protected wallet without the passphrase is cryptographically unrecoverable — the seed phrase alone is insufficient.

52% of all passphrase-unavailable cases in the archive result in a blocked outcome. These 46 cases represent the full 52% — the subset where this specific combination of stress condition and outcome is documented. The most common recovery path is estate process.

46
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

46 observed cases
Blocked
46 (100%)
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
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
Bitcointalk User Locks Self Out of Bitcoin Core Wallet After Forgetting Encryption Passphrase
Software wallet
Blocked 2011
In 2011, a user on the Bitcointalk forum reported having encrypted their Bitcoin Core wallet.dat file with a passphrase—a security practice recommended at the t
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
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
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
Deceased Father's 14 BTC Locked on Blockchain.com: Forgotten Password Blocks Access
Exchange custody
Blocked
A Reddit user reported discovering their deceased or incapacitated father's Blockchain.com wallet containing 14 BTC. While the heir had gained access to the acc
BIP38-Encrypted Paper Wallet: Permanent Loss After Forgotten Passphrase
Software wallet
Blocked
In December 2017, a new Bitcoin user created a paper wallet using BitAddress.org and elected to encrypt it with BIP38 (Bitcoin Improvement Proposal 38), a stand
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
Hardware Wallet and Seed Phrase Lost in House Fire
Hardware wallet (single key)
Blocked
A Bitcoin holder experienced a catastrophic loss when a house fire destroyed multiple custody components at once: the hardware wallet itself, the computer used
10.5 BTC Locked in Electrum: Forgotten Passphrase, Public Recovery Attempt Failed
Software wallet
Blocked
In October 2016, a Bitcoin holder transferred 10.511 BTC from a Bitcoin Core wallet stored on a thumb drive to Electrum. The motivation was straightforward: the
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
Trezor Hardware Wallet: 0.1 BTC Inaccessible After PIN Loss and Seed Destruction
Hardware wallet (single key)
Blocked
A Trezor hardware wallet user held 0.1 Bitcoin on the device approximately two years after initial purchase. The recovery seed phrase had been written down on p
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
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
Seed Phrase and Wallet Password Lost in Personal Journal
Software wallet
Blocked
A Bitcoin holder maintained a split custody arrangement, allocating approximately half their stack to a custodial exchange and the remainder to self-custody. Th
BlueWallet Password Lock Prevents Seed Phrase Restoration
Software wallet
Blocked
A BlueWallet user set a password to protect their wallet, then forgot it. Standard custody protocol suggested the recovery seed phrase—held safely in written fo
Stefan Thomas: 7,002 Bitcoin Inaccessible on IronKey With 2 Password Attempts Remaining
Hardware wallet with passphrase
Blocked
Stefan Thomas, a German-born software developer based in San Francisco, accumulated 7,002 Bitcoin over years of work in the technology sector. In the early-to-m
0.7 BTC Trapped in Unencrypted Change Address: Bitcoin Core Legacy Wallet
Software wallet
Blocked
A Bitcoin user mined cryptocurrency in the early era using an unencrypted Bitcoin Core wallet.dat file. Years later, he encrypted the wallet software and execut
← PreviousNext →
Browse by outcome and stress
Related pages
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.

Original text
Rate this translation
Your feedback will be used to help improve Google Translate