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%)
Opticbit Loses 2 BTC After CyanogenMod 9 Flash Without Locatable Wallet Backup
Software wallet
Blocked 2012
On June 25, 2012, a Bitcoin user operating under the handle opticbit reported the loss of 2 BTC stored in a mobile wallet on an Android phone. The loss occurred
Campbell Simpson Discards 1,400 BTC on Failing Hard Drive Without Backup
Software wallet
Blocked 2012
Campbell Simpson, editor of Gizmodo Australia, purchased approximately 1,400 Bitcoin in early 2010 when a single coin traded for roughly 1.5 cents, investing ar
Brad Yasar: Desktop-Mined Bitcoin Locked by Forgotten Passwords
Software wallet
Blocked 2012
Brad Yasar, a Los Angeles-based entrepreneur, mined Bitcoin on multiple desktop computers during the network's earliest years when mining was accessible to indi
Device discarded — software wallet (2011)
Software wallet
Blocked 2011
In 2011, when Bitcoin mining was still largely a hobbyist pursuit, the user identified as 'bubbabojangles' mined 103 BTC using standard desktop equipment. At th
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
Ulti Loses 28 BTC to Incomplete SSD Migration — October 2011
Software wallet
Blocked 2011
On October 1, 2011, a Bitcointalk user identified as Ulti posted an account of a custody failure resulting from routine hardware maintenance. While upgrading hi
10 BTC Gifted in 2011, Lost in Unrecoverable Hard Drive Crash
Software wallet
Blocked 2011
Greg received 10 bitcoin as a gift during the earliest phase of Bitcoin adoption, when the asset was trading around 10 cents per coin. The bitcoin was stored on
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
MultiBit Wallet Deletion and File Corruption: ~100 BTC Permanent Loss
Software wallet
Blocked 2011
In March 2013, a Bitcoin holder generated a private key from a passphrase using bitaddress.org on a Xubuntu Live CD, then imported it into MultiBit desktop wall
1,000 BTC Lost After Accidental Deletion of GPG-Encrypted Dropbox Wallet File
Software wallet
Blocked 2011
An early Bitcoin contributor made a generous gift of 1,000 BTC to the brother of a Hacker News user, with a casual remark that it would someday be valuable. The
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
AWS EC2 and Local VM Wallet Deletion: Early Backup Failure Pattern
Software wallet
Blocked 2011
In May 2011, BitcoinTalk user opticbit reported losing approximately 0.01 BTC stored on an AWS EC2 instance that was subsequently deleted, and an additional sma
BitcoinTalk User 'td' Loses 50 BTC Mined Block After Deleting Wallet Without Backup
Software wallet
Blocked 2011
In May 2011, a BitcoinTalk forum user identified as 'td' reported the loss of 50 BTC—the full block reward from a successfully mined block. At the time of loss,
Davyd Arakhamia Loses 400 BTC After Deleting Encrypted Key File
Software wallet
Blocked 2011
Davyd Arakhamia, a Ukrainian entrepreneur and later member of the Verkhovna Rada (elected 2019), accumulated approximately 400 BTC through a business that accep
Lost Bitcoin from 2011 Dialcoin Purchase — Wallet Unknown, Documentation Discarded
Unknown custody system
Blocked 2011
In May 2017, a Bitcoin Stack Exchange user identified as David posted about bitcoins purchased in 2011 from Dialcoin, a now-defunct early exchange platform. Dav
26 BTC Lost: Developer Formats Drive Containing Wallet, Gives to Mother-in-Law
Software wallet
Blocked 2011
In October 2021, a Hacker News user identified as jakewins disclosed a significant custody failure from the early Bitcoin era. The user possessed 26 BTC stored
Lost Bitcoin Mining Wallet on Decommissioned PC: Data Overwritten Beyond Recovery
Software wallet
Blocked 2010
In 2009 or 2010, rosnick92 and his father mined Bitcoin on a personal computer for several days, earning what he recalls as 'a few pennies per day'—an amount he
Seed unavailable — software wallet (2010)
Software wallet
Blocked 2010
On July 14, 2010, a BitcoinTalk user with the handle ksd5 reported a critical loss in a forum thread posted just two days after account creation. The user held
2,700 BTC Lost to Antivirus Deletion and Unverified Drive Format
Software wallet
Blocked 2010
An individual received a hard drive containing a wallet.dat file—allegedly holding approximately 2,700 BTC—sent by an early Bitcoin adopter around 2010 via emai
9,000 BTC Lost to Unrebacked Change Address: Early Bitcoin Wallet Flaw (2010)
Software wallet
Blocked 2010
In August 2010, a Bitcoin user purchased 9,000 BTC and conducted a single test transaction: sending 1 BTC to his own address to confirm network functionality. T
8,999 BTC Lost to Non-Deterministic Wallet Change Address Design
Software wallet
Blocked 2010
In 2010, a Bitcoin user held approximately 9,000 BTC in a Bitcoin Core wallet. To validate his backup and recovery procedure, he executed a test transaction to
Stone Man Loses 8,999 BTC to Unbacked Change Address After Live CD Shutdown
Software wallet
Blocked 2010
In August 2010, a BitcoinTalk user known as Stone Man purchased 9,000 BTC on an exchange and transferred them to a Bitcoin client running on a Debian Linux live
10,000 Bitcoin Lost When Laptop Discarded as Junk (2010)
Software wallet
Blocked 2010
In March or April 2010, while a final-year student at St. John's University in New York, an individual purchased 10,000 BTC from a local seller for approximatel
PC Miner Overwrites wallet.dat During OS Reinstall, Loses ~12 BTC (2010)
Software wallet
Blocked 2010
In 2010, the user known as 'kingcharles' was mining Bitcoin on a personal computer during the currency's early adoption phase. At that time, mined bitcoins were
1,000 BTC Lost to Repeated Hard Drive Formatting: Self-Custody Without Backup
Software wallet
Blocked 2009
In January 2017, a BitcoinTalk forum user identified as myBitcoin2009 posted a recovery request describing a custody loss rooted in the earliest era of Bitcoin
← 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