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%)
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
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
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
Accidental Deletion and Overwriting of 2011 Mining wallet.dat Files
Software wallet
Indeterminate 2014
Japanese2212, a BitcoinTalk forum user, posted in July 2021 describing a custody failure stemming from accidental file deletion and data overwriting. The user c
ASUS Netbook Wallet Deletion: Corrupted Files Block $9,000 Recovery Effort
Software wallet
Indeterminate 2014
In January 2014, Igor76200 purchased a second-hand ASUS Eee PC 1001PX netbook and created approximately 5–6 Bitcoin wallets on it on January 7, 2014. The user c
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
Forgotten Encryption Passphrase Blocks Access to 10+ BTC in Bitcoin Core Wallet
Software wallet
Indeterminate 2014
In December 2014, a BitcoinTalk user identifying as casperround publicly sought help recovering access to an encrypted Bitcoin Core wallet containing over 10 BT
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user eric89 reported a custody failure involving a Litecoin wallet mined in April 2013. The user had encrypted the wallet using Li
Armory Wallet Lost via VirtualBox Snapshot Rollback—Binary Recovery Attempt
Software wallet
Indeterminate 2013
In October 2013, a BitcoinTalk user known as HowlingMad lost access to 6.59159344 BTC stored in Armory, a then-leading Bitcoin wallet application running on Win
Encrypted Wallet Recovery After Accidental Partition Deletion (2013)
Software wallet
Indeterminate 2013
On July 17, 2013, a Bitcoin holder identified as Praxis posted to a cryptocurrency forum after losing access to multiple wallet files stored in hidden Linux dir
2013 Electrum Wallet File Blocked by Version Incompatibility
Software wallet
Indeterminate 2013
SirKhaal, a Bitcoin holder from the early mining era, retained an Electrum wallet file (electrum.dat) from 2013 along with its original passphrase. When attempt
Passphrase unavailable — software wallet (2013)
Software wallet
Indeterminate 2013
On February 5, 2014, BitcoinTalk user repukken posted in the encrypted wallet recovery thread seeking help to brute-force access to a Dogecoin wallet after forg
BTC Guild Miner's Lost Self-Custody Wallet: 0.05 BTC Inaccessible Without Seed or Backup File
Software wallet
Indeterminate 2013
In 2013–2014, user haihong8787 mined Bitcoin using a graphics card on the BTC Guild mining pool (user ID 97249). The pool distributed mining rewards directly to
Dogecoin Wallet Passphrase Mismatch: 50,000 DOGE Inaccessible Despite Documentation
Software wallet
Indeterminate 2013
On December 27, 2013, a BitcoinTalk user named Alohaboy posted seeking help recovering access to a Dogecoin wallet. The user had documented their passphrase ('d
13.8 BTC Lost to Forgotten Wallet.dat Password: DIY and Professional Recovery Attempts
Software wallet
Indeterminate 2013
A Bitcoin user created an encrypted Bitcoin Core wallet in 2013 containing 13.8 BTC. The passphrase was forgotten, rendering the wallet inaccessible. In Septemb
TrueCrypt Volume Corruption Across All Backups: Wallet Recovery Attempt
Software wallet
Indeterminate 2013
In 2011, a Bitcoin user created two TrueCrypt encrypted containers on Windows 7: one holding wallet.dat, the second holding unimportant files as a control. Afte
Multibit Wallet Lost After Mac Reformat Without Backup
Software wallet
Indeterminate 2013
In November 2013, a BitcoinTalk user identified as funkonaut posted about losing access to their Bitcoin holdings following a critical self-inflicted data loss
BitcoinTalk User RTQ1154 Locks 78 BTC Behind Mistyped Wallet Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user identifying as RTQ1154 posted in a community thread titled 'Let's add up the KNOWN lost bitcoins' describing a custody lo
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'veryveryinteresting' posted in topic 85495, the community's primary encrypted wallet recovery thread, describin
BitcoinTalk User 'Liquid': 30 BTC Inaccessible Due to Forgotten Bitcoin-Qt Encryption Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user operating under the handle 'Liquid' posted in the encrypted wallet recovery thread (topic 85495) describing an inaccessib
Hidden wallet discovered — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user nobbie discovered that Bitcoin-Qt's wallet encryption feature had been activated, locking access to the wallet with a passwor
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'legitnick' posted in topic 85495, the primary community support thread for locked wallet recovery during the 20
← Previous
15678911
Next →
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