CustodyStress
Archive › Browse by documentation and stress › Present and Interpretable — Device loss
Part of the CustodyStress archive of observed Bitcoin custody incidents
Present And InterpretableDevice loss

Present and Interpretable — Device loss

Cases where interpretable documentation existed but device loss still produced a custody failure. These cases typically involve documentation of the access procedure without the seed phrase itself.

24 cases in this intersection. 62% of determinate cases resulted in a blocked outcome and 38% in access survived. The most common recovery path is technical recovery.

Archive analysis — 24 cases
Outcomes
62% of determinate cases resulted in blocked access — 7 percentage points below the archive-wide average of 69%. 38% resulted in recovered access — above the archive average.
Custody type
96% of cases involved software wallet, followed by hardware wallet (single key) at 4%.
Recovery path
Technical Recovery is the most documented recovery path (9 cases, 38% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
100% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
17% of cases involved large or very large holdings (10+ BTC).
Time distribution
Cases span 2011–2020. Only 0% occurred in 2022 or later — concentrated in earlier periods.
13
Blocked
0
Constrained
8
Survived
3
Indeterminate

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

24 observed cases
Blocked
13 (54%)
Survived
8 (33%)
Indeterminate
3 (13%)
Mobile Wallet Hardware Failure: No Seed Backup, Permanent Loss
Software wallet
Blocked 2020
Hippocrypto, a BitcoinTalk user, lost access to Bitcoin stored exclusively on a mobile software wallet after the smartphone suffered catastrophic internal hardw
Corrupted wallet.dat Recovery from 2009 Hard Drive: Hex Search Method
Software wallet
Indeterminate 2018
In January 2018, a BitcoinTalk user reported discovering a hard drive containing a wallet.dat file created during 2009 Bitcoin mining. The drive had suffered si
Wallet.dat Corruption After Accidental Drive Format — Recovery via Data Recovery and Pywallet
Software wallet
Survived 2017
In July 2017, AleksTo, a newcomer to Bitcoin, accidentally formatted their hard drive, destroying the only local copy of their wallet.dat file. The user immedia
Corrupted 2013 wallet.dat Recovery via Community-Guided Disk Scanning
Software wallet
Survived 2017
In December 2017, a macOS Bitcoin Core user attempted to restore access to two wallet.dat files created in late 2013. The user had downloaded a contemporary ver
1,000+ BTC Permanently Lost: Multiple Hard Drive Formats Destroyed Wallet Data
Software wallet
Blocked 2016
In 2009, a teenager claiming to be an early Bitcoin adopter received over 1,000 BTC allegedly directly from Satoshi Nakamoto. The user stored the wallet on a de
Corrupted Encrypted wallet.dat Recovered via Partition-Level Recovery
Software wallet
Survived 2016
In March 2016, a Bitcoin Core user discovered their only backup of an encrypted wallet.dat file had become corrupted, likely due to improper shutdown of Bitcoin
Recovering Deleted Bitcoin Core wallet.dat via pywallet: Device Loss and Forensic Key Extraction
Software wallet
Survived 2015
Edgar's Bitcoin Core wallet became inaccessible in 2015 when the wallet.dat file was removed from the active system while the Bitcoin Core client remained open.
Hard Drive Format Recovery: 2 BTC Restored via Sector Scanning and wallet.dat Reconstruction
Software wallet
Survived 2015
In approximately 2015, marilyn4325 formatted a hard drive and installed Windows 10, intending to preserve wallet data via backup first. However, the backup beca
Windows System Refresh and Data Recovery Failure: Bitcoin Permanently Inaccessible
Software wallet
Blocked 2014
In 2014, sachalamp's Windows 7 or 8 computer experienced a system failure. The user performed a Windows refresh operation, which reset Bitcoin Core and severed
James Howell's Hard Drive: 8,000 Bitcoin Lost in Welsh Landfill
Hardware wallet (single key)
Blocked 2014
James Howell, a British-based individual, accidentally discarded a hard drive containing private keys to approximately 8,000 Bitcoin while cleaning his office a
Bitcoin-Qt 0.8.0-beta Wallet Corruption on OS X Mountain Lion — Unrecovered After Five Months
Software wallet
Blocked 2013
In late April 2013, jordan.dev, a Bitcoin-Qt user on macOS Mountain Lion 10.8.3, encountered a crash (EXC_BAD_ACCESS/SIGBUS) when launching Bitcoin-Qt 0.8.0-bet
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Software wallet
Blocked 2013
James Howells, a UK resident, discarded a hard drive containing an encrypted Bitcoin wallet during a routine office clearance in 2013. The device was disposed o
Australian Miner Loses Early Bitcoin When Sole USB Backup Drive Fails Irrecoverably
Software wallet
Blocked 2013
Alex, an Australian Bitcoin miner based in Melbourne, mined Bitcoin around 2010 when mining was still a hobbyist activity with negligible monetary value. Unlike
Multibit Wallet Recovered From Formatted Hard Drive After 5 Years
Software wallet
Survived 2013
In 2013, a Bitcoin holder stored funds in a Multibit wallet on a work desktop computer. The hard drive was subsequently formatted, and the user assumed the Bitc
Deep Freeze Software Erases Bitcoin Wallet.dat Before Incoming Payment
Software wallet
Blocked 2012
In September 2012, a Bitcoin user operating under the handle blackjhon909 discovered that their Bitcoin wallet had become inaccessible following an unexpected s
1,300 BTC Inaccessible: BitLocker Encryption Key Lost on Failed Flash Drive
Software wallet
Indeterminate 2012
In June 2012, forum user mb300sd disclosed on BitcoinTalk's 'known lost bitcoins' thread that approximately 1,300 BTC had become permanently inaccessible due to
Early CPU Miner Loses 27,000 BTC to Unrecoverable Drive Failure
Software wallet
Blocked 2012
Dalkore mined 27,000 BTC during Bitcoin's earliest period using CPU mining, when the network was still in its first year and coins carried no meaningful market
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
Corrupted wallet.dat Recovery After Hard Drive Failure: 2011 Case Study
Software wallet
Indeterminate 2011
In May 2011, forum user zrataj (John) experienced a critical storage failure when his hard drive crashed, destroying both his primary wallet.dat file and the ba
80 BTC Recovery After Hard Drive Format: Pywallet Raw Data Reconstruction
Software wallet
Survived 2011
In December 2011, a BitcoinTalk user's friend experienced critical wallet inaccessibility when his computer crashed. The friend brought the machine to a technic
Wallet File Swap Causes Transaction Invisibility: Blockchain Index Desynchronization (2011)
Software wallet
Survived 2011
Michael_S was running Bitcoin client version 0.3.19 on Ubuntu Linux in May 2011 and sought to improve security by splitting his holdings across two wallet.dat f
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
Browse by documentation and stress
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.