CustodyStress
Archive › Browse by outcome and custody type › Indeterminate — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
IndeterminateSoftware wallet

Indeterminate — Software wallet

Cases where a software wallet access failure has an unknown or unresolved outcome. These cases represent custody situations where the structural failure is documented but whether recovery was ultimately achieved is not recorded in available sources.

253 observed cases
Indeterminate
253 (100%)
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
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
Hard Drive Discarded in Landfill: £4 Million Bitcoin Lost Without Backup
Software wallet
Indeterminate
A UK individual reportedly discarded a hard drive containing Bitcoin assets valued at approximately £4 million GBP and subsequently attempted to locate and reco
Recovering Bitcoin After Owner Death: Paper Wallet and Computer Access
Software wallet
Indeterminate
In December 2013, a user posted to Bitcoin Stack Exchange asking for help recovering Bitcoin belonging to their brother, who had died in April of that year. The
Mycelium Mobile Wallet Theft With Seed Phrase Inaccessible in Forgotten Password Manager
Software wallet
Indeterminate
A Mycelium mobile wallet user experienced device theft and discovered a critical structural gap in their backup approach. The 12-word seed phrase had been store
350 Bitcoin Wallet.dat Deleted During OS Reinstall — Data Recovery Attempted
Software wallet
Indeterminate
An individual who had acquired approximately 350 bitcoin at roughly $10 per coin maintained the wallet as an encrypted wallet.dat file stored in cold storage on
Wallet Passphrase Rejected Despite Correct Entry: Bitcoin Custody Failure
Software wallet
Indeterminate
In June 2019, a Bitcoin Core user reported that their wallet passphrase was not being accepted during an attempted transaction, despite having written it down c
Multibit Wallet Lost to Hard Drive Format Without Backup
Software wallet
Indeterminate
In January 2015, a Multibit user experienced total loss of wallet access after formatting their hard drive due to computer problems. The user retained only an a
Deleted Bitcoin Core Wallet: Recovered Passphrase Cannot Decrypt Corrupted File
Software wallet
Indeterminate
In 2013, the subject purchased one Bitcoin on a family desktop computer when the asset traded near $11.92 per unit. The wallet was created using Bitcoin Core, t
MultiBit Wallet Lost to Full Drive Format — Single Backup Copy Destroyed
Software wallet
Indeterminate
An early Bitcoin adopter stored their MultiBit wallet file (.wallet extension) exclusively on their Windows C: drive without creating any external backup. Multi
10 BTC Locked on Obsolete Sony Memory Stick: The Format Obsolescence Problem
Software wallet
Indeterminate
A Bitcoin holder retained approximately 10 BTC from 2010 mining operations stored on a Sony Memory Stick, one of several proprietary formats Sony introduced in
Deceased Son's Bitcoin Wallet: Found Backup, Lost Passphrase
Software wallet
Indeterminate
A family member discovered a hard drive among their deceased son's belongings containing a file named BACKUP.dat, believed to be a backup of a Bitcoin Core wall
Exodus Desktop Wallet After PC Failure: Hard Drive Recovery and the Seed Phrase Requirement
Software wallet
Indeterminate
A Bitcoin holder experienced total failure of their Windows 10 personal computer and removed the hard drive. When connected via SATA to another computer, the dr
TrueCrypt-Encrypted Wallet.dat: Partial Passphrase, Uncertain Recovery Path
Software wallet
Indeterminate
A Bitcoin and Litecoin miner from the early 2014 era encrypted his wallet.dat file inside a TrueCrypt volume, motivated by security paranoia despite acknowledgi
Restored wallet.dat from Inherited Laptop Shows Zero Balance
Software wallet
Indeterminate
A user inherited an old laptop believed to contain Bitcoin holdings from a deceased or incapacitated family member. The device held a wallet.dat file located in
25 BTC Paper Wallet Destroyed by Fire and Water Exposure
Software wallet
Indeterminate
A Bitcoin holder maintained 25 BTC on a paper wallet as their primary custody method. The holder attempted to protect this physical printout—which contained bot
Water-Damaged Mobile Wallet: 0.25 BTC Inaccessible Without Seed Backup
Software wallet
Indeterminate
A user accumulated approximately 0.25 bitcoins over several weeks through mobile mining activity, storing the funds directly in a mobile wallet application. The
1000 BTC Across 13 Hard Drives: No Passphrase, No Documentation, No Access
Software wallet
Indeterminate
A Bitcoin holder died intestate or with a will naming a relative as beneficiary of a hard drive allegedly containing approximately 1000 BTC. The estate's execut
2011 Bitcoin Wallet Lost After Hard Drive Formatted Twice: Passphrase Retained, File Unrecoverable
Software wallet
Indeterminate
In 2011, an individual purchased Bitcoin and generated a wallet using Bitcoin-Qt or a similar early desktop client software. The wallet created an encrypted wal
MultiBit Classic USB Loss With Incomplete Backup Recovery Path
Software wallet
Indeterminate
A Bitcoin holder experienced loss of a USB stick containing a MultiBit Classic wallet holding what they described as life-changing amounts of Bitcoin. The incid
3000 BTC Mined on Pentium 3: Multiple Reformatted Drives, Wallet Location Unknown
Software wallet
Indeterminate
During Bitcoin's early years, this user established mining operations on a Pentium 3 computer and accumulated approximately 3000 BTC before ceasing work as netw
House Fire Destroyed Mycelium Mobile Wallet: 1.1 BTC With Unrecorded 15-Character Passphrase
Software wallet
Indeterminate
A Bitcoin holder maintained 1.1 BTC in a Mycelium mobile wallet on an Android device, secured by a 15-character passphrase created over three years before the i
Unverified Wallet File Recovery After Drive Format: 2010 GPU-Mined Bitcoin
Software wallet
Indeterminate
In 2010, during Bitcoin's GPU-mining era, the user mined a small quantity of Bitcoin on a desktop computer. Years later, the user deleted the wallet.dat file an
Mycelium Wallet Uninstalled During Device Reset Without Seed Phrase Export
Software wallet
Indeterminate
A user stored Bitcoin in Mycelium, a mobile wallet application for Android. The device developed malware infections requiring routine maintenance and factory re
← PreviousNext →
Browse by outcome and custody type
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