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%)
Peter Schiff Lost Access to Gifted Bitcoin After App Update, Never Recorded Seed Phrase
Software wallet
Blocked 2020
On January 19, 2020, Peter Schiff, an economist and well-known Bitcoin critic, announced on Twitter that he had lost access to all his Bitcoin. The funds—approx
Vietnamese Police Officers Charged in $1.6 Million Bitcoin Robbery
Software wallet
Blocked 2020
In May 2020, Le Duc Nguyen, a Bitcoin holder in Ho Chi Minh City, Vietnam, became the victim of a coordinated robbery by police officers. The officers seized ap
Inherited Bitcoin Recovery After Mother's Death: 10 BTC Sold, Remainder Secured
Software wallet
Survived 2020
A sole heir inherited Bitcoin holdings from their mother, who died the day after Thanksgiving 2020. The heir possessed complete recovery documentation: a 12-wor
Iroro Wisdom Ovie Killed in Bitcoin-Motivated Home Invasion, Nigeria 2020
Software wallet
Blocked 2020
In January 2020, Iroro Wisdom Ovie was killed during a home invasion in Abraka, Delta State, Nigeria. The attackers were motivated specifically by knowledge tha
Mobile Wallet Hardware Failure: No Seed Backup, Permanent Loss
Software wallet
Blocked 2020
Hippocrypto, a BitcoinTalk user, lost access to Bitcoin stored exclusively on a mobile software wallet after the smartphone suffered catastrophic internal hardw
Mark Cheng Jin Quan Kidnapped and Extorted for Bitcoin in Bangkok
Software wallet
Blocked 2020
Mark Cheng Jin Quan, a Singapore-based blockchain advisor, was kidnapped in Bangkok, Thailand in January 2020 and held at gunpoint by his captors. Under physica
Atomic Wallet: 2 BTC Permanently Inaccessible After OS Reinstall Without Seed Backup
Software wallet
Blocked 2020
In September 2020, a BitcoinTalk user (dovjann) disclosed a complete custody failure involving approximately 2 BTC held in Atomic Wallet on a Windows laptop. At
Forgotten 115-Character Wallet Password Recovered via GPU Typo-Bruteforce
Software wallet
Survived 2019
In August 2017, a Bitcoin enthusiast created a Bitcoin Core wallet secured by a 115-character sentence-based password and wrote it down. In June 2019, when they
Shahid Naseer: 9 BTC Extorted Under Kidnapping in Lahore, 2019
Software wallet
Blocked 2019
Shahid Naseer, an information technology professor in Lahore, Pakistan, was kidnapped in March 2019 by a student acting in coordination with corrupt police offi
Bitcoin Core Wallet Deleted During Hard Drive Format — No Backup
Software wallet
Blocked 2019
In April 2019, a Bitcoin Core user downloaded the full-node software but encountered synchronization delays due to insufficient storage space. The installation
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.
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
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
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
Alexander Halavais: Forgotten Password on 2010 Experimental Bitcoin Purchase
Software wallet
Blocked 2017
Alexander Halavais, an Associate Professor in the School of Social and Behavioral Sciences at Arizona State University, purchased a small quantity of Bitcoin ar
Wallet.dat Corruption After Accidental Drive Format — Recovery via Data Recovery and Pywallet
Software wallet
Survived 2017
In July 2017, AleksTo, a newcomer to Bitcoin, accidentally formatted their hard drive, destroying the only local copy of their wallet.dat file. The user immedia
Jaxx Mobile Wallet — Permanent Loss After Android Factory Reset Without Seed Backup
Software wallet
Blocked 2017
In September 2017, a BitcoinTalk user (Mikekom) reported installing the Jaxx wallet application on an Android smartphone to hold Bitcoin earned by their 13-year
Hidden Line Feed Character Blocks Bitcoin Core Wallet Access
Software wallet
Survived 2017
In February 2017, scutzi128 documented a Bitcoin Core wallet access failure on the Bitcoin Technical Support forum. The user had encrypted their wallet with a 2
Corrupted 2013 wallet.dat Recovery via Community-Guided Disk Scanning
Software wallet
Survived 2017
In December 2017, a macOS Bitcoin Core user attempted to restore access to two wallet.dat files created in late 2013. The user had downloaded a contemporary ver
33.54 BTC Corrupted in Wallet.dat: Binary File Opened in Text Editor
Software wallet
Blocked 2017
In July 2016 or earlier, ketubi saved a wallet.dat file from Bitcoin Core to a USB drive, intending to create an offline backup. Years later, in December 2017,
1,000+ BTC Permanently Lost: Multiple Hard Drive Formats Destroyed Wallet Data
Software wallet
Blocked 2016
In 2009, a teenager claiming to be an early Bitcoin adopter received over 1,000 BTC allegedly directly from Satoshi Nakamoto. The user stored the wallet on a de
Electrum Wallet Password Loss: 4 BTC Inaccessible Without Seed Backup
Software wallet
Blocked 2016
On April 6, 2016, Andi300 posted on forum.bitcoin.com describing an immediate custody failure: the user had just received 4 BTC but was unable to send or access
Andreas1324 Permanently Locked Out of Electrum Wallet: Forgotten Password, No Seed Backup (May 2016)
Software wallet
Blocked 2016
In May 2016, a BitcoinTalk user posting as Andreas1324 opened a public thread in the Electrum wallet subforum describing complete loss of access to a wallet hol
Corrupted Encrypted wallet.dat Recovered via Partition-Level Recovery
Software wallet
Survived 2016
In March 2016, a Bitcoin Core user discovered their only backup of an encrypted wallet.dat file had become corrupted, likely due to improper shutdown of Bitcoin
BIP39 Passphrase Confusion: How a Mobile PIN Hid Bitcoin for Five Years
Software wallet
Survived 2016
In mid-2016, the user's Android device failed. They recovered their MyCelium wallet using their seed phrase but found all pre-2016 Bitcoin gone. The wallet show
← 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