CustodyStress
Archive › Structural dependencies › Undocumented Procedure
Part of the CustodyStress archive of observed Bitcoin custody incidents

Undocumented Procedure

Cases where the recovery procedure was never documented or the documentation was insufficient to reconstruct access.

73% of determinate cases in this category resulted in a blocked outcome.

174
Blocked
11
Constrained
52
Survived
309
Indeterminate

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

546 observed cases
Blocked
174 (32%)
Constrained
11 (2%)
Survived
52 (10%)
Indeterminate
309 (57%)
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
Early Miner Loses 50 BTC: Private Key Gone, Wallet.dat Scattered Across Backup Media
Software wallet
Indeterminate 2010
In August 2017, a Bitcoin user (username lozzauk) posted on BitcoinTalk describing loss of access to a wallet containing approximately 50 BTC plus additional al
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
Early Bitcoin Client Wallet Partially Overwritten: File Recovery and Data Loss Analysis
Software wallet
Indeterminate 2010
In January 2010, furyo87 ran the Bitcoin client on a Windows machine for several days while experiencing stability issues. The user was uncertain whether any BT
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
Deleted 2009-2010 Bitcoin Mining Wallet: Disk Overwrite and Recovery Failure
Software wallet
Indeterminate 2009
In December 2017, a BitcoinTalk user identified as idelcoins posted a detailed account of attempting to recover Bitcoin wallet files from hard disks containing
2009 Bitcoin Purchase Lost to Paper Backup Destruction and Device Absence
Software wallet
Indeterminate 2009
Plinxer, a BitcoinTalk user, posted in May 2023 describing a Bitcoin purchase made in 2009 for approximately £50 (then ~$60–65 USD). The transaction occurred vi
2009 Bitcoin Mining Wallet Recovery: Fragmented wallet.dat on Deleted Drive
Software wallet
Indeterminate 2009
TheMadGenius07 downloaded and briefly mined Bitcoin on a high-performance gaming rig in summer 2009, then uninstalled the Bitcoin application when mining activi
1000 BTC from 2009 Mining: Wallet Recovery After Hard Drive Reformat
Software wallet
Indeterminate 2009
The original poster ('unluckysoul') described losing access to approximately 1000 BTC generated during the earliest Bitcoin mining period using Bitcoin-Qt, the
Bitcoin Transfer Stalled Between Bither Wallets—Old Laptop to New, 3+ Months Unresolved
Software wallet
Indeterminate 2008
A caregiver assisted their friend (who has disability-related constraints preventing direct technical engagement) in attempting to consolidate Bitcoin holdings.
Seed Phrase Restored but Zero Balance: Unknown Derivation Path Blocks Recovery
Software wallet
Indeterminate
A Bitcoin holder maintained a 12-word seed phrase from an offline wallet application, possibly a Coinbase product, for several years. The wallet displayed the u
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
18 BTC Bitcoin-Qt Wallet.dat: Database Corruption and Filesystem Recovery
Software wallet
Survived
A Bitcoin holder possessed an early Bitcoin-Qt wallet file containing 18 BTC that had been abandoned for years after the wallet appeared corrupted. When Bitcoin
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
Bitcoin Core Wallet Reopened After 7 Years: Passphrase Status Unknown
Software wallet
Indeterminate
In August 2017, a Bitcoin Core user reopened their wallet software for the first time in nearly seven years and discovered an unexpected balance. The account co
GreenAddress User Locked Out by 2FA Requirement Despite Mnemonic Backup
Collaborative custody
Constrained
A GreenAddress user transferred Bitcoin from Bitfinex to a GreenAddress multisig wallet, securing an encrypted backup of their recovery mnemonics using their Br
Coinkite Platform Shutdown: Encrypted Private Key Available, Recovery Status Indeterminate
Exchange custody
Indeterminate
In 2014, a Bitcoin newcomer purchased BTC via Coinkite, an online hosted wallet service. The user then disengaged entirely from cryptocurrency for several years
Widow Left Without Access to Deceased Husband's Bitcoin Holdings
Unknown custody system
Indeterminate
Following her husband's death, a widow learned he had held Bitcoin at some point in his life but had managed all financial affairs independently and left no doc
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
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
Incomplete Mnemonic Seed Phrase: 11 of 12 Words Retained, Missing Word Recovery Feasibility
Software wallet
Indeterminate
A Bitcoin wallet user lost access to one word of their mnemonic seed phrase, retaining only 11 of 12 words. The user became aware that BIP39 uses a curated Engl
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
← PreviousNext →
Structural dependencies
By 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.

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