CustodyStress
Archive › Browse by dependency and custody › Single-Person Knowledge — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Single-Person KnowledgeSoftware wallet

Single-Person Knowledge — Software wallet

Cases where only one person understood how to access a mobile wallet. When that person became unavailable or failed to communicate access credentials, no independent recovery path existed.

77% of all Software wallet cases in the archive involve this structural dependency. The blocked rate among them is 81% — 12 points above the archive-wide blocked rate of 69%. The most common recovery path is password bruteforce.

121
Blocked
5
Constrained
24
Survived
201
Indeterminate

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

351 observed cases
Blocked
121 (34%)
Constrained
5 (1%)
Survived
24 (7%)
Indeterminate
201 (57%)
Mycelium Mobile Wallet Balance Access Failure — December 2017
Software wallet
Indeterminate 2017
In mid-December 2017, a Bitcoin user (Myrr) discovered a critical custody access failure in the Mycelium mobile wallet on their iPhone. The user had purchased B
Accidental Wallet.dat Deletion on Mac SSD — Unrecoverable Bitcoin Loss
Software wallet
Indeterminate 2017
On November 2, 2017, a Bitcoin user identified as chrisf199 posted on BitcoinTalk seeking professional help to recover a wallet.dat file they had accidentally d
BIP38 Paper Wallet Passphrase Lost — 0.7 BTC Inaccessible (2020)
Software wallet
Indeterminate 2017
A BitcoinTalk user (arkaraj) purchased approximately 0.7 BTC in 2017 and generated a paper wallet using bitaddress.org with BIP38 passphrase encryption. The use
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,
Bitcoin Core Fatal Error After Moving Block Folder: wallet.dat Accessible But Program Won't Launch
Software wallet
Indeterminate 2016
In December 2016, a Bitcoin Core user installed the software on their PC and began purchasing Bitcoin before full blockchain synchronization was complete. Appro
Armory Desktop Wallet: 2 BTC Inaccessible Despite Paper and Encrypted Backups
Software wallet
Indeterminate 2016
A user purchased 2 BTC via Coinbase approximately 2013–2014 and transferred them to a self-hosted Armory wallet running on a personal server. The transfer compl
Incomplete Electrum Seed Phrase: 0.032 BTC Inaccessible Since 2016
Software wallet
Indeterminate 2016
In December 2024, a BitcoinTalk user (winnerorlooser) disclosed a custody failure spanning eight years. Around 2016, the user transferred 0.032 BTC from an obso
75 BTC Access Loss: Bitcoin Core Wallet Reset Without Backup (2016)
Software wallet
Indeterminate 2016
In 2016, forum user bridget1 installed Bitcoin Core v0.13.0 and deposited 75 BTC into the newly created wallet. At the time, 75 BTC had a market value of approx
Rafel Marcel: Bitcoin Acquired via BitX in 2016, Seed Phrase Never Recorded
Software wallet
Indeterminate 2016
Rafel Marcel purchased Bitcoin approximately ten years prior to March 2026—around late 2016—through an exchange called BitX (later rebranded as Luno). A friend
Passphrase unavailable — Bitcoin Core, Finland (2016)
Software wallet
Indeterminate 2016
On February 5, 2016, a user identifying as mikkihiiri posted in the Bitcoin Technical Support section of BitcoinTalk seeking help to recover access to an encryp
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
Lost Electrum Wallet Password (2 BTC) – No Recovery Path Identified
Software wallet
Indeterminate 2016
In September 2016, a BitcoinTalk forum user with username Ashkaan posted a public bounty request seeking professional assistance to recover access to an Electru
Smartphone Wallet Reset Without Backup: 15 BTC Private Key Unverified
Software wallet
Indeterminate 2016
In November 2016, a user identified as 'Farer' created a Bitcoin wallet on a smartphone and accumulated 15 bitcoins. Approximately one year later, the user rese
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
Watching-Only Wallet With Lost Seed Phrase: Password Insufficient for Recovery
Software wallet
Indeterminate 2016
In June 2016, a BitcoinTalk user identified as Tully96 posted in the Wallet Software forum seeking help after discovering they had lost access to Bitcoin stored
Electrum Wallet Loss After Hard Disk Failure: No Seed Phrase or Backup
Software wallet
Indeterminate 2016
In March 2016, a BitcoinTalk user operating under the handle 'knowhow' experienced total loss of access to an Electrum Bitcoin wallet after their hard drive fai
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
Bitcoin-Qt Passphrase Encoding Mismatch: Known Password Rejected Across Versions
Software wallet
Indeterminate 2015
StaleCoinz created a Bitcoin-Qt wallet on macOS in 2013 and encrypted it in 2015 using a passphrase he distinctly remembered. When he attempted to access the wa
Lost BIP38 Passphrase on Paper Wallet: 256 Case Combinations, No Documentation
Software wallet
Indeterminate 2015
In March 2015, a user known as 'germanuniv' created a paper wallet using bitaddress.org with BIP38 encryption enabled. To generate the passphrase, the user deri
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
Father Died in 2015 With Bitcoin: Daughter Searches 200 USBs, Finds Nothing
Software wallet
Blocked 2015
A father purchased Bitcoin in the early 2010s, a decision that created friction within his marriage. He died unexpectedly in 2015 without documenting his holdin
Bitcoin Core USB Wallet (2015): Passphrase Lost, Balance Unconfirmed After Reimport
Software wallet
Indeterminate 2015
In 2015, an individual secured Bitcoin on a Bitcoin Core wallet stored on an external USB drive, encrypted with a passphrase. Years later, the owner connected t
← Previous
15678915
Next →
Browse by dependency and custody
Related pages
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