CustodyStress
Archive › Browse by trigger and era › Device Loss Without Backup — Exchange Era (2014–2019)
Part of the CustodyStress archive of observed Bitcoin custody incidents
Device_loss_without_backupExchange Era

Device Loss Without Backup — Exchange Era (2014–2019)

Bitcoin custody cases involving device loss without backup and exchange era (2014–2019).

Archive analysis — 14 cases
Documentation coverage
79% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
93% of cases involved software wallet, followed by hardware wallet (single key) at 7%.
Primary stress condition
71% of cases involve device loss. Passphrase unavailable accounts for a further 14%.
Recovery path
Technical Recovery is the most documented recovery path (3 cases, 21% of subset).
Documentation
57% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
100% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
14 observed cases
Blocked
1 (7%)
Constrained
1 (7%)
Survived
1 (7%)
Indeterminate
11 (79%)
0.19 BTC Recovery Attempt After Bitcoin Core Crash and Wallet.dat Restoration
Software wallet
Indeterminate 2019
In August 2019, owenzane posted to the Bitcoin Technical Support forum seeking help recovering 0.19 BTC from a wallet he had created and backed up approximately
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
Bitcoin Knots Wallet Access Lost After SSD Migration: wallet.dat Location Mismatch
Software wallet
Indeterminate 2018
In May 2018, an inexperienced Bitcoin user (mortamuerte) initiated blockchain synchronization using Bitcoin Knots, a Bitcoin Core fork, on a laptop SSD. Partway
Bitcoin Core Wallet Database Lost After Disk-Full Error — Recovery Unknown
Software wallet
Indeterminate 2017
In November 2017, a Bitcoin Core user encountered a critical custody failure after receiving a 'no more free disk space' error notification while attempting to
15 BTC Lost to Smartphone Reset Without Backup – Private Key Format Unidentified
Software wallet
Indeterminate 2017
In November 2017, a BitcoinTalk forum user under the pseudonym 'Farer' posted a detailed account of custody failure involving a smartphone-based Bitcoin wallet
Armory Cold Wallet Restoration Created Unencrypted Wallet With Plaintext Private Keys
Hardware wallet (single key)
Indeterminate 2017
KillerTank maintained Bitcoin in offline cold storage on an air-gapped Raspberry Pi with an 18-word paper backup consisting of 4 random letters per set. In Dece
1,000 BTC Lost to Repeated Hard Drive Formats: 2009 Wallet Recovery Attempt
Software wallet
Indeterminate 2017
In January 2017, a BitcoinTalk forum user identified as myBitcoin2009 disclosed a custody failure spanning eight years. The user claimed to have received over 1
BIP39 Passphrase Confusion: How a Mobile PIN Hid Bitcoin for Five Years
Software wallet
Survived 2016
In mid-2016, the user's Android device failed. They recovered their MyCelium wallet using their seed phrase but found all pre-2016 Bitcoin gone. The wallet show
Forgotten Bitcoin Wallet on Lost Amazon Fire Phone: Data Recovery Failure
Software wallet
Indeterminate 2015
In 2015, a friend transferred approximately $10 worth of Bitcoin to a user's Amazon Fire phone using a mobile wallet application as payment for donuts. The user
MultiBit Wallet on Stolen Laptop: Recovery Phrase Format Ambiguity Blocks Access
Software wallet
Indeterminate 2014
In 2014, mcsteely purchased Bitcoin from a Bitcoin ATM and sent it to a MultiBit wallet installed on a laptop. The device was subsequently stolen. At the time,
20 Bitcoin Wallets Lost to Hard Drive Failure—Manual Recovery via Data Forensics and Private Key Extraction
Software wallet
Indeterminate 2014
In August 2014, Lucky Cris experienced simultaneous hardware failure affecting both primary and external backup drives, rendering all Bitcoin holdings inaccessi
Payment Processor: Passphrase Lost on Damaged Flash Drive, 200+ BTC Addresses at Risk
Software wallet
Constrained 2014
In June 2014, an operator running a Bitcoin payment processing system discovered that the flash drive storing the passphrase to their wallet had been irreversib
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
0.3 BTC Lost When Android Bitcoin Wallets Factory Reset Without Backup
Software wallet
Indeterminate 2014
In July 2014, a BitcoinTalk forum user (ejinte) reported transferring 0.3 BTC to family members—his mother and sister—by helping them download and set up an And
Browse by trigger and era
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