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%)
Unauthorized Drive Format and Corrupted Wallet File Recovery Failure (2011)
Software wallet
Indeterminate 2011
On September 17, 2011, a Bitcoin holder identified as cablepair discovered that an office network administrator had reformatted the hard drive of a shared offic
Corrupted wallet.dat Recovery After Hard Drive Failure: 2011 Case Study
Software wallet
Indeterminate 2011
In May 2011, forum user zrataj (John) experienced a critical storage failure when his hard drive crashed, destroying both his primary wallet.dat file and the ba
33.54 BTC Trapped in Corrupted Bitcoin-Qt Wallet Since 2011
Software wallet
Indeterminate 2011
In December 2017, a BitcoinTalk user identified as ketubi posted about 33.54 BTC held in a corrupted wallet.dat file from Bitcoin-Qt version 0.4.0. The last rec
Corrupted wallet.dat from 2011 Hard Drive — Fire Damage and Data Loss
Software wallet
Indeterminate 2011
In January 2021, a forum user known as 'french' reported discovering a wallet.dat file on a hard drive that had experienced both partial data erasure and fire d
Corrupted ext3 Hard Drive & Fragmented wallet.dat: HEX-Level Recovery Attempt (2011)
Software wallet
Indeterminate 2011
In June 2011, a Bitcoin holder identified as TurboIan reported catastrophic custody failure on a 65 GB ext3-formatted Linux hard drive. The drive suffered files
2010–2011 Windows XP GPU Mining Recovery: Unknown Pool, Lost Wallet Metadata, No Seed Record
Software wallet
Indeterminate 2011
ALANL ran continuous GPU mining on Windows XP using a GeForce 8800 GT graphics card for approximately three months in 2010–2011. The card eventually burned out
92 BTC Inaccessible: Passphrase Deleted From Password Manager Vault
Software wallet
Indeterminate 2011
In 2011, a high school graduate purchased approximately 92 BTC for roughly $100 using the Bitcoin reference client on a flash drive. The wallet was encrypted wi
9 Bitcoin Inaccessible: Encrypted Desktop Wallet Software Crash on Passphrase Entry
Software wallet
Indeterminate 2011
In 2011, a Bitcoin user encrypted a desktop software wallet using Bitcoin Core and transferred approximately 9 BTC to it. Only after the transaction confirmed d
30+ BTC Sent to Wrong Address in 2011: Private Key Never Located
Software wallet
Indeterminate 2011
In 2011, blocparty_ received approximately 30 BTC from an exchange and transferred the amount (minus fees) to what they believed was a secondary address of thei
KnightMB: 370,000 BTC Accumulated in Early Mining, Sold or Lost to Access Failure
Software wallet
Indeterminate 2011
KnightMB, a pseudonymous user on Bitcointalk, posted in 2011 documenting an accumulation of over 370,000 BTC acquired through mining and pool operation during 2
Fragmented Wallet.dat Recovery: Disk Image Mining Loss Without Backup
Software wallet
Indeterminate 2011
In 2011–2012, callerman used Bitcoin-QT to mine Bitcoin on a personal computer with limited technical knowledge of cryptocurrency infrastructure. Facing disk sp
1,000+ BTC from 2010: Lost USB Drive, Corrupted Hardware, Incomplete Seed Recovery
Software wallet
Indeterminate 2010
In 2010, theunionjack purchased over 1,000 Bitcoin at a fraction of a cent by creating two PGP keys using GPG4Win/Kleopatra and importing them into what he beli
2010–2011 Windows XP GPU Mining: Lost Bitcoin Wallet, No Documentation
Software wallet
Indeterminate 2010
ALANL conducted Bitcoin GPU mining around 2010–2011 on a Windows XP system using a GeForce 8800 GT graphics card in a continuous 3-month operation before the ha
2010 Mining Pool Wallet.dat: Passphrase Lost After Decade of Storage
Software wallet
Indeterminate 2010
Between 2010 and 2011, the source participated in Bitcoin pool mining and retained the resulting wallet.dat file on a local system. The wallet remained untouche
2010 Bitcoin Wallet Deleted and Partially Recovered: Data Integrity Compromised by Subsequent Disk Writes
Software wallet
Indeterminate 2010
rok95 mined Bitcoin using CPU mining in 2010 during the network's earliest phase, when such activity was accessible to casual users with standard computing hard
533 BTC Inaccessible After Brother's Death; Laptop Hard Drive Removed and Lost
Software wallet
Indeterminate 2010
Shotukan purchased 533 BTC in 2010 for approximately $60, storing the private keys on a Dell laptop's wallet.dat file. He later gave the laptop to his brother,
Early Miner Loses 50 BTC: Private Key Gone, Wallet.dat Scattered Across Backup Media
Software wallet
Indeterminate 2010
In August 2017, a Bitcoin user (username lozzauk) posted on BitcoinTalk describing loss of access to a wallet containing approximately 50 BTC plus additional al
Early Bitcoin Client Wallet Partially Overwritten: File Recovery and Data Loss Analysis
Software wallet
Indeterminate 2010
In January 2010, furyo87 ran the Bitcoin client on a Windows machine for several days while experiencing stability issues. The user was uncertain whether any BT
Deleted 2009-2010 Bitcoin Mining Wallet: Disk Overwrite and Recovery Failure
Software wallet
Indeterminate 2009
In December 2017, a BitcoinTalk user identified as idelcoins posted a detailed account of attempting to recover Bitcoin wallet files from hard disks containing
2009 Bitcoin Purchase Lost to Paper Backup Destruction and Device Absence
Software wallet
Indeterminate 2009
Plinxer, a BitcoinTalk user, posted in May 2023 describing a Bitcoin purchase made in 2009 for approximately £50 (then ~$60–65 USD). The transaction occurred vi
2009 Bitcoin Mining Wallet Recovery: Fragmented wallet.dat on Deleted Drive
Software wallet
Indeterminate 2009
TheMadGenius07 downloaded and briefly mined Bitcoin on a high-performance gaming rig in summer 2009, then uninstalled the Bitcoin application when mining activi
1000 BTC from 2009 Mining: Wallet Recovery After Hard Drive Reformat
Software wallet
Indeterminate 2009
The original poster ('unluckysoul') described losing access to approximately 1000 BTC generated during the earliest Bitcoin mining period using Bitcoin-Qt, the
Bitcoin Transfer Stalled Between Bither Wallets—Old Laptop to New, 3+ Months Unresolved
Software wallet
Indeterminate 2008
A caregiver assisted their friend (who has disability-related constraints preventing direct technical engagement) in attempting to consolidate Bitcoin holdings.
Seed Phrase Restored but Zero Balance: Unknown Derivation Path Blocks Recovery
Software wallet
Indeterminate
A Bitcoin holder maintained a 12-word seed phrase from an offline wallet application, possibly a Coinbase product, for several years. The wallet displayed the u
Bitcoin Core Wallet Reopened After 7 Years: Passphrase Status Unknown
Software wallet
Indeterminate
In August 2017, a Bitcoin Core user reopened their wallet software for the first time in nearly seven years and discovered an unexpected balance. The account co
← 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