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%)
Widow Unable to Locate Deceased Husband's Bitcoin Wallet or Recovery Documents
Software wallet
Indeterminate 2019
In November 2019, a woman posted on Bitcoin Stack Exchange asking for help recovering her husband's Bitcoin holdings following his death weeks earlier. She had
Lost Electrum Wallet Password: wallet.dat File Encrypted, No Backup Credential
Software wallet
Indeterminate 2019
In February 2019, a forum user identified as bitbemining posted a custody failure case involving an Electrum wallet. The user possessed the encrypted wallet.dat
Electrum Seed Version 18 Password Recovery: btcrecover Incompatibility Resolved
Software wallet
Survived 2019
In December 2019, a BitcoinTalk user (red14159) discovered a wallet.dat file from an Electrum wallet they had lost access to approximately three years earlier.
Electrum Seed Phrase Mismatch: Valid Addresses, Missing Funds
Software wallet
Indeterminate 2018
In January 2018, forum user 'thenarog' encountered a nuanced custody failure involving an Electrum desktop wallet. The user held a wallet.dat backup file protec
Computer Crash with wallet.dat Backup: Bitcoin Core Recovery Without Private Key Export
Software wallet
Survived 2018
In February 2018, a Bitcoin Core user experienced a total computer crash requiring complete system reinstallation. The user had previously used an Armory wallet
PIVX Encrypted Wallet Access Failure After System Update and Forced Shutdown
Software wallet
Indeterminate 2018
In May 2018, a user encrypted a PIVX wallet using PIVX Core version 3.1.0.2 on Windows 64-bit and confirmed the passphrase worked across multiple unlock cycles
131 BTC Inaccessible: Forgotten Wallet Password, No Recovery Mechanism
Software wallet
Indeterminate 2018
In December 2018, a BitcoinTalk user known as 'jackang' posted a public plea for help recovering access to a wallet containing 131 BTC. The wallet had been crea
Paper Wallet QR Code Case Mismatch: Single Character Locked Access for 2.5 Years
Software wallet
Survived 2018
Al Reno generated an offline paper wallet using bitaddress.org in August 2018, manually printing both public and private keys with QR codes to physical paper. H
Bither Desktop Wallet Application Crash: 3-Year Recovery via Password Rediscovery
Software wallet
Survived 2018
Sygun created a Bither wallet in March 2018 holding approximately 0.019 BTC. At an unspecified point, the Bither application ceased launching entirely—double-cl
Corrupted 2011 Bitcoin Mining Wallet: File Recovery Attempted but Balance Unverifiable
Software wallet
Blocked 2018
In September 2018, a Bitcoin forum user discovered an old wallet.dat file originating from 2011 Bitcoin mining activity on his original hard drive. After a frie
College-Era Bitcoin Miner: Wallet.dat Recovered, But Addresses Empty
Software wallet
Indeterminate 2018
In early 2018, a Bitcoin Forum user identified as cdcine sought help recovering Bitcoin he had mined during his college years using Bitcoin Core version 0.3.23,
Bitcoin-Qt HD Wallet Change Address Lost to Deleted wallet.dat File
Software wallet
Blocked 2018
In May 2018, a BitcoinTalk user identified as Tuee22 performed a transaction sending 0.01 BTC to an online vendor using Bitcoin-Qt. The user had maintained a si
4 BTC Inaccessible in BIP38-Encrypted Paper Wallet After Passphrase Loss
Software wallet
Indeterminate 2018
In February 2018, a Bitcoin holder discovered that access to 4 BTC distributed across three BIP38-encrypted paper wallet addresses had become impossible due to
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
Electrum Wallet Lost to Laptop Hardware Failure: No Seed Phrase Backup
Software wallet
Indeterminate 2018
On October 12, 2018, a BitcoinTalk forum user identified as Chabole007 reported losing access to an Electrum software wallet after their laptop experienced hard
Recovered 12-Word Seed Phrase but Balance Shows Zero: Imported Address Problem
Software wallet
Blocked 2018
In September 2018, a Bitcoin holder attempted to recover wallet access after forgetting which software they had originally used. They obtained a 12-word recover
MultiBit Classic Password Lock: Recovery Through Backup Key File Import
Software wallet
Survived 2018
A BitcoinTalk user (cluuze130) deposited Bitcoin into MultiBit Classic approximately one year before attempting withdrawal in February 2018. At the time of depo
BitcoinTalk User: Encrypted Wallet.dat Passphrase Lost, Recovery Deemed Infeasible
Software wallet
Indeterminate 2018
In January 2018, a BitcoinTalk forum user identified as moztec reported an access failure involving a wallet.dat file encrypted with Bitcoin Core. The user had
Encrypted Wallet, Forgotten Passphrase: Self-Custody Encryption Without Backup
Software wallet
Indeterminate 2018
On January 14, 2018, BitcoinTalk user AsJoshScreams posted a recovery plea for an encrypted cryptocurrency wallet. The user had encrypted their private key with
Mycelium Bitcoin Access Loss: PIN Change and Seed Phrase Recovery Confusion
Software wallet
Indeterminate 2017
In November 2017, a Mycelium wallet user (AdunToridas) encountered a critical access loss incident after routine account maintenance. The user had created a Myc
Armory Paper Backup Recovery Displays Zero Balance Despite Correct Restoration
Software wallet
Indeterminate 2017
In November 2017, user xTwin25 initiated recovery of Bitcoin holdings stored in Armory, a desktop software wallet. The user possessed a paper backup containing
Lost Android Wallet.dat After Device Wipe and Lending — No Backup
Software wallet
Indeterminate 2017
In December 2017, a BitcoinTalk user identified as dandyret described losing access to a Bitcoin wallet stored on an Android phone. The user had wiped the devic
Dash Core Wallet Passphrase Forgotten: Permanent Access Loss
Software wallet
Blocked 2017
In April 2017, a BitcoinTalk forum user identified as 'Ramchandra' posted describing a custody failure involving a Dash Core software wallet. The user had encry
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
← Previous
13456716
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.