CustodyStress
Archive › Browse by documentation and custody type › Present and Interpretable — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Present And InterpretableSoftware wallet

Present and Interpretable — Software wallet

Cases where clear documentation existed for a software wallet but a custody failure still occurred. These cases reveal documentation limitations: recorded credentials that were outdated, incorrect derivation paths, or passphrases that were documented but inaccessible.

105 cases in this intersection. 70% of determinate cases resulted in a blocked outcome and 29% in access survived. The most common recovery path is no path available.

66
Blocked
1
Constrained
27
Survived
11
Indeterminate

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

105 observed cases
Blocked
66 (63%)
Constrained
1 (1%)
Survived
27 (26%)
Indeterminate
11 (10%)
James Howell Bitcoin Hard Drive: Decade-Long Landfill Recovery Attempt Denied
Software wallet
Blocked 2015
James Howell, a Bitcoin holder from the 2014–2015 era when Bitcoin traded below $1,000, discarded a hard drive containing his private keys while cleaning his of
Bitcoin Core Wallet Corruption: Selective Key Decryption Failure and Community Recovery
Software wallet
Survived 2015
Henke created an encrypted wallet backup on December 20, 2015, containing approximately 4 BTC. After refreshing his Windows 7 system and reinstalling Bitcoin Co
Deleted Temporary Wallet Recovery via Private Key Forensic Extraction
Software wallet
Survived 2015
In September 2015, a Bitcoin user known as dooglus encountered a self-imposed custody failure during a transaction resend operation. After noticing an unconfirm
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
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 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
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
Electrum Wallet Recovery After Seed Backup Loss: electrum.dat File Decryption
Software wallet
Survived 2014
In April 2014, a BitcoinTalk forum user (DarkHyudrA) experienced custody access failure after formatting their personal computer without preserving a backup cop
1,000 BTC Permanently Lost After Brother Deletes wallet.dat From Shared Dropbox Folder
Software wallet
Blocked 2013
In 2017, Hacker News user illumin8 disclosed a permanent loss of 1,000 BTC resulting from a wallet file deletion in a shared Dropbox folder. The Bitcoin wallet
Bitcoin-Qt 0.8.0-beta Wallet Corruption on OS X Mountain Lion — Unrecovered After Five Months
Software wallet
Blocked 2013
In late April 2013, jordan.dev, a Bitcoin-Qt user on macOS Mountain Lion 10.8.3, encountered a crash (EXC_BAD_ACCESS/SIGBUS) when launching Bitcoin-Qt 0.8.0-bet
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
43.6 BTC Recovered via RoboForm RNG Reverse-Engineering After TrueCrypt Corruption
Software wallet
Survived 2013
Michael, a European Bitcoin holder, generated and secured a 20-character password using RoboForm in April 2013 and transferred 43.6 BTC into a software wallet.
Armory Wallet Synchronization Failure: Access Restored After Software Upgrade
Software wallet
Survived 2013
In October 2013, a BitcoinTalk user holding approximately 0.1008 BTC in an encrypted Armory wallet encountered a critical access failure. The user possessed bot
Encrypted wallet.dat passphrase mismatch: offline wallet creation to recovery (2013)
Software wallet
Survived 2013
In July 2013, a user created an encrypted wallet on an Ubuntu live CD and stored the wallet.dat file offline. Several months later, in December 2013, he importe
Matthew Moody: Bitcoin Miner Dies in Plane Crash, Wallet Inaccessible
Software wallet
Blocked 2013
Matthew Moody was an early Bitcoin miner who began accumulating coins during the network's nascent period when mining remained feasible on standard consumer har
Kristoffer Koch Recovers Forgotten 5,000 BTC Wallet After Four Years
Software wallet
Survived 2013
In 2009, Kristoffer Koch, a Norwegian engineering student, purchased 5,000 Bitcoin for approximately 150 Norwegian kroner (roughly $27 USD at the time) as resea
Noitev's Lost Electrum Password: 1.8–1.9 BTC Recovered via Brute-Force Attack
Software wallet
Constrained 2013
On April 8, 2013, BitcoinTalk user Noitev reported losing access to an Electrum wallet holding approximately 1.8–1.9 BTC due to a forgotten password. The wallet
Bitcoin-Qt Wallet Loss: Executable Backup Without Private Key File (2013)
Software wallet
Blocked 2013
TheD1ceMan, a forum user, experienced an irrecoverable loss of approximately 1.8 BTC (valued at $2,300–$2,700 USD at May 2013 market prices) due to a critical m
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Software wallet
Blocked 2013
James Howells, a UK resident, discarded a hard drive containing an encrypted Bitcoin wallet during a routine office clearance in 2013. The device was disposed o
Australian Miner Loses Early Bitcoin When Sole USB Backup Drive Fails Irrecoverably
Software wallet
Blocked 2013
Alex, an Australian Bitcoin miner based in Melbourne, mined Bitcoin around 2010 when mining was still a hobbyist activity with negligible monetary value. Unlike
Bomben Recovers 2013 Bitcoin Wallet Locked by Nonstandard Private Key Encoding
Software wallet
Survived 2013
Bomben created a Bitcoin wallet in 2013 using software that implemented a nonstandard encoding for private keys, diverging from the Wallet Import Format (WIF) s
Maxime: Hard Drive Corruption Destroyed Only Copy of Seed Phrase
Software wallet
Blocked 2013
Maxime, a Canadian journalist, began mining Bitcoin during the 2012–2013 period when the technology represented an emerging alternative financial system. He suc
Multibit Wallet Recovered From Formatted Hard Drive After 5 Years
Software wallet
Survived 2013
In 2013, a Bitcoin holder stored funds in a Multibit wallet on a work desktop computer. The hard drive was subsequently formatted, and the user assumed the Bitc
Rahazan Develops and Shares PowerShell Wallet Recovery Script (2013)
Software wallet
Indeterminate 2013
In 2013, a BitcoinTalk user identifying as Rahazan faced a common early custody problem: an encrypted Bitcoin-Qt wallet with a forgotten passphrase. Rather than
← PreviousNext →
Browse by documentation 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