CustodyStress
Archive › Browse by dependency and custody › Undocumented Recovery Procedure — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Undocumented Recovery ProcedureSoftware wallet

Undocumented Recovery Procedure — Software wallet

Cases where a mobile wallet had no documented recovery procedure. When the original holder became unavailable, there was no written record to guide recovery.

84% of all Software wallet cases in the archive involve this structural dependency. The blocked rate among them is 73% — 4 points above the archive-wide blocked rate of 69%. The most common recovery path is password bruteforce.

116
Blocked
2
Constrained
40
Survived
222
Indeterminate

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

380 observed cases
Blocked
116 (31%)
Constrained
2 (1%)
Survived
40 (11%)
Indeterminate
222 (58%)
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.
Zombie Paintball Incident: Written Password Loss Blocks Access to $20K Bitcoin
Software wallet
Blocked 2015
Luke purchased his first Bitcoin around 2013 for approximately $200 and continued accumulating holdings over roughly two years, investing between $15,000 and $2
Father Died in 2015 With Bitcoin: Daughter Searches 200 USBs, Finds Nothing
Software wallet
Blocked 2015
A father purchased Bitcoin in the early 2010s, a decision that created friction within his marriage. He died unexpectedly in 2015 without documenting his holdin
Bitcoin Core USB Wallet (2015): Passphrase Lost, Balance Unconfirmed After Reimport
Software wallet
Indeterminate 2015
In 2015, an individual secured Bitcoin on a Bitcoin Core wallet stored on an external USB drive, encrypted with a passphrase. Years later, the owner connected t
Encrypted Bitcoin Core Wallet Loss: Forgotten Passphrase, Selective Key Export Failure
Software wallet
Blocked 2015
In October 2015, forum user phantitox reported recovering a wallet.dat file from a damaged hard drive, only to discover the passphrase protecting the encrypted
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
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
Forgotten Bitcoin Core Passphrase: Third-Party Recovery Service Success — Community Skepticism
Software wallet
Constrained 2015
In July 2015, a BitcoinTalk user (bassride2) discovered that while they had meticulously backed up their Bitcoin Core wallet.dat file multiple times, they had f
Electrum Wallet Password Loss Without Seed Phrase Backup
Software wallet
Indeterminate 2015
In November 2015, a BitcoinTalk user created a password-protected Electrum software wallet for testing purposes and set a password they believed followed the pa
0.22 BTC Inaccessible in Electrum Watch-Only Wallet After Bitcoin Core Import Error
Software wallet
Indeterminate 2015
In October 2015, a macOS user (ginko3000) discovered they could not spend 0.22 BTC held in an Electrum wallet despite the balance being visible on screen. The w
Forgotten Passphrase and Overwritten Wallet.dat: 0.50 BTC Permanently Lost
Software wallet
Blocked 2015
In May 2015, BitcoinTalk user grovearmada discovered they had lost access to an encrypted Bitcoin wallet containing 0.50 BTC (approximately $115–120 USD at 2015
Ruairi's Lost Paper Backup: €80 Bitcoin, Both Credentials on One Document
Software wallet
Blocked 2015
Ruairi purchased approximately €80 worth of Bitcoin in late 2015, driven by curiosity about the emerging technology and its associations with dark web markets.
Electrum Desktop Wallet: 0.7 BTC Locked by Forgotten Password, Missing Seed Phrase
Software wallet
Indeterminate 2014
Liam, a new Bitcoin user (BitcoinTalk username AbeTheCat), purchased 0.7 BTC in October 2014 and stored it in an Electrum desktop software wallet on his origina
Bitcoin-Qt Wallet Shows Zero Balance After Windows Installation on SSD
Software wallet
Indeterminate 2014
In January 2014, a Bitcoin holder experienced a system failure (repeated Blue Screen of Death) on their PC. Rather than repair the existing installation, they p
Electrum Seed Phrase Lost to Accidental File Deletion — Windows Recovery Attempt
Software wallet
Indeterminate 2014
In mid-2014, a user identified as Evolution created an Electrum Bitcoin wallet using Tails live operating system running inside VMware on Windows 7. The user ge
BIP38 Passphrase Recovery Service Abandonment (2014)
Software wallet
Indeterminate 2014
In July 2014, a BitcoinTalk forum user identified as houseo posted in the Services section describing a custody access failure involving a forgotten BIP38 passp
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,
Electrum Wallet Access Failure: Lost Printed Seed and Empty CSV Export
Software wallet
Indeterminate 2014
In February 2014, a BitcoinTalk forum user identified as 'Howinthe?' reported the loss of access to 2 BTC acquired years earlier when the asset traded at approx
KeePass Database Corruption: 11.7 BTC Locked Behind Unrecoverable Password
Software wallet
Indeterminate 2014
In April 2014, a BitcoinTalk user reported that their cousin had lost access to 11.7 BTC held in an encrypted wallet.dat file. The cousin had generated a strong
Forgotten Passphrase: 3.3 BTC Recovered by Third-Party Service for 20% Fee
Software wallet
Constrained 2014
In June 2014, a BitcoinTalk user identified as marsje007 discovered they could no longer access a wallet containing 3.3 BTC after changing the passphrase and fa
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
22.1 BTC Bitcoin-Qt Wallet Password Recovery via Community Brute Force (2014)
Software wallet
Survived 2014
In November 2014, a Bitcoin-Qt wallet containing 22.1 BTC became inaccessible when its owner forgot the passphrase. The owner had documented the password creati
MultiBit 16-Word Seed Recovery Failure: Non-Standard Implementation
Software wallet
Indeterminate 2014
In 2014, NickyGH attended a Bitcoin wallet setup workshop in Shoreditch, London organized through a community meetup. A technician guided attendees through Mult
10,000 DOGE from Bittylicious (2014): Device Loss, No Backup, SSD Wiped
Software wallet
Blocked 2014
In December 2014, a UK-based BitcoinTalk user (apda) received 10,000 DOGE from Bittylicious, a London-regulated cryptocurrency exchange (BIOM Ltd), and directed
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
← Previous
167891016
Next →
Browse by dependency and custody
Related pages
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