CustodyStress
Archive › Browse by dependency and outcome › Undocumented Recovery Procedure — Blocked
Part of the CustodyStress archive of observed Bitcoin custody incidents
Undocumented Recovery ProcedureBlocked

Undocumented Recovery Procedure — Blocked

Cases where an undocumented recovery procedure produced a blocked outcome. No written record existed to guide anyone through recovery when the original holder became unavailable.

174 cases in this intersection. 100% of determinate cases resulted in a blocked outcome. The most common recovery path is no path available.

174
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

174 observed cases
Blocked
174 (100%)
Multibit Desktop Wallet: Bitcoin Inaccessible After Platform Closure and File Loss
Software wallet
Blocked
A professional received a Bitcoin payment to an address generated by Multibit, a lightweight desktop wallet widely used during the early-to-mid 2010s. At the ti
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
Encrypted Bitcoin Core wallet.dat (2015)—Passphrase Known, Recovery Failed
Software wallet
Blocked
A Bitcoin Core user encrypted their wallet.dat file in 2015 using the application's built-in passphrase feature and made no further transactions after 2018. Whe
2.3 Bitcoin Inaccessible on Ledger Nano S: Owner Incapacity and Undocumented Credentials
Hardware wallet (single key)
Blocked
In 2019, one partner in a 16-year relationship created a Ledger Nano S hardware wallet and transferred 2.3 Bitcoin to it. The partner deliberately withheld both
Desktop Software Wallet Erased During PC Reset — Seed Phrase Never Recorded
Software wallet
Blocked
A Bitcoin holder maintained their first cryptocurrency wallet as a hot wallet on a personal computer, following a common early-adoption pattern of minimal secur
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
50 BTC Lost After Accidental Hard Drive Format
Software wallet
Blocked
A Bitcoin holder maintained a wallet file on a hard drive without maintaining a backup. The drive was formatted, destroying the wallet data, before the loss was
James Howells' 7,500 Bitcoin: Hard Drive Lost in Newport Landfill
Software wallet
Blocked
James Howells, a software engineer in Newport, South Wales, accidentally discarded a hard drive containing approximately 7,500 to 8,000 Bitcoin in the early 201
100 Bitcoin Lost on Discarded Flash Drive: Permanent Access Failure
Software wallet
Blocked
During Bitcoin's early adoption phase, when the asset had negligible market value and was treated primarily as an experimental hobby, the original poster create
100 Bitcoin Lost to Discarded Flash Drive Without Backup
Software wallet
Blocked
An early Bitcoin adopter stored approximately 100 bitcoins on a flash drive during Bitcoin's formative years, likely before 2013, when the asset carried minimal
When Bitcoin Seed Phrases Are Lost at Death: Community Debate on Permanent Custody Failure
Hardware wallet (single key)
Blocked
A Reddit discussion explored a recurring custody failure scenario: an individual holds Bitcoin in self-custody using only a seed phrase known solely to them, wi
30 BTC Destroyed in House Fire — Hardware Wallet Loss Without Backup
Hardware wallet (single key)
Blocked
A Reddit forum user posted approximately six years ago that their neighbor had lost a hardware wallet containing 30 BTC in a house fire. The device was physical
Hard Drive Format Renders 300,000 Satoshis Permanently Inaccessible
Software wallet
Blocked
An individual user accidentally formatted a hard drive containing 300,000 satoshis, equivalent to approximately $20 USD at the time of the incident. The wallet
Copay Wallet Recovery Failed: Mnemonic Word Sequence Error
Software wallet
Blocked
In February 2020, a Copay wallet user posted to Bitcoin Stack Exchange reporting total loss of funds despite possessing a complete 12-word mnemonic backup. The
Mycelium Mobile Wallet Glitch: Bitcoin Inaccessible Despite Blockchain Confirmation
Software wallet
Blocked
In February 2020, a Bitcoin user purchased coins on the Mycelium mobile wallet application. Shortly after the purchase, the user attempted to create a backup bu
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
MultiBit Wallet Lost on Dead Hard Drive with No Backup Files
Software wallet
Blocked
In September 2016, a South African user posted to Bitcoin Stack Exchange describing total loss of access to their MultiBit wallet following hard drive failure.
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
The Hard Drive in the Landfill: $80 Million in Inaccessible Bitcoin
Hardware wallet (single key)
Blocked
In the early years of Bitcoin adoption, a miner accumulated a substantial holding on a single hard drive. At the time of disposal, the device contained Bitcoin
Mycelium on Encrypted Samsung Galaxy Note 4: 0.1 BTC Inaccessible, 6 Password Attempts Remaining
Software wallet
Blocked
The owner stored 0.1 BTC in a Mycelium wallet installed on a Samsung Galaxy Note 4 at a time when Bitcoin's price was materially lower. The device's screen frac
0.7 BTC Permanently Inaccessible After Confusing Coldcard Authentication Words With Seed Backup
Hardware wallet (single key)
Blocked
A Bitcoin holder stored 0.7 BTC on a Coldcard hardware wallet and created what they believed to be a complete paper backup. The backup contained only the device
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
Android Bitcoin Wallet Destroyed in Factory Reset: 0.5 BTC Unrecovered
Software wallet
Blocked
A Bitcoin holder maintained approximately 0.5 BTC using the Bitcoin Wallet application by Andreas Schildbach on a Samsung Galaxy Note 2 running Android. The hol
MultiBit Change Address Private Key Generation Failure
Software wallet
Blocked
A MultiBit user transferred Bitcoin from blockchain.info into the lightweight desktop wallet in order to conduct online transactions. To prepare for sales activ
Blockchain.info Account Inaccessible: Valid Credentials Defeated by Email Verification Gate
Exchange custody
Blocked
An early adopter maintained a Blockchain.info wallet account from the platform's initial era, retaining both the wallet ID and a valid password. The account rem
← PreviousNext →
Browse by dependency and outcome
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