CustodyStress
Archive › Browse by custody type and stress › Software wallet — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Software walletSeed phrase unavailable

Software wallet — Seed phrase unavailable

Cases where the seed phrase for a mobile wallet was never recorded, was lost, or became inaccessible. Without the seed, device loss or wallet deletion produces permanent access failure.

92% of determinate cases in this intersection resulted in a blocked outcome — 2 points higher than the 90% blocked rate for this stress condition overall. This custody type accounts for 75% of all cases with this stress condition in the archive. The most common recovery path is technical recovery.

54
Blocked
0
Constrained
5
Survived
58
Indeterminate

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

117 observed cases
Blocked
54 (46%)
Survived
5 (4%)
Indeterminate
58 (50%)
Bitcoin-Qt Wallet Shows Zero Balance After Windows Installation on SSD
Software wallet
Indeterminate 2014
In January 2014, a Bitcoin holder experienced a system failure (repeated Blue Screen of Death) on their PC. Rather than repair the existing installation, they p
Electrum Seed Phrase Lost to Accidental File Deletion — Windows Recovery Attempt
Software wallet
Indeterminate 2014
In mid-2014, a user identified as Evolution created an Electrum Bitcoin wallet using Tails live operating system running inside VMware on Windows 7. The user ge
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
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
10,000 DOGE from Bittylicious (2014): Device Loss, No Backup, SSD Wiped
Software wallet
Blocked 2014
In December 2014, a UK-based BitcoinTalk user (apda) received 10,000 DOGE from Bittylicious, a London-regulated cryptocurrency exchange (BIOM Ltd), and directed
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
Bitcoin-Qt Wallet Corruption After Power Loss — Salvage Command Failed to Recover
Software wallet
Blocked 2014
In 2014, a Bitcoin holder stored their funds in a wallet.dat file managed by Bitcoin-Qt on a Windows machine with an SSD. The wallet had been dormant for approx
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
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
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
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
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
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
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
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
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
2013 Bitcoin Core Wallet.dat Corruption After Version Incompatibility
Software wallet
Indeterminate 2013
The subject purchased a used desktop computer from a thrift store and discovered an installed Bitcoin QT client with an associated wallet.dat file dating to 201
Inherited 2009 Bitcoin Mining Hard Drive: Unrecoverable wallet.dat After OS Reinstall
Software wallet
Indeterminate 2013
A Bitcoin holder inherited a hard drive from their father's computer, which had been used for Bitcoin mining in November 2009. The drive had been powered down a
125 BTC Lost on SSD After Windows Reinstall Without Backup
Software wallet
Indeterminate 2012
Robert23 reported on January 5, 2012, that they had lost access to 125 BTC stored in a wallet.dat file after performing a clean Windows reinstall on an SSD driv
Lost Private Key in 2012 Bitcoin Core Wallet: 5 mBTC Unspendable
Software wallet
Blocked 2012
Gemwolf installed Bitcoin Core 0.6.3 in 2012, performed brief mining activity, and abandoned the wallet after one day. In November 2022, while searching old sto
Private Key Accessible but Wallet Balance Unrecoverable: bread45's 2011 Mt.Gox Withdrawal
Software wallet
Indeterminate 2012
In June 2011, bread45 purchased Bitcoin on Mt.Gox and transferred coins to Bitcoin-QT desktop wallet software for self-custody. In 2012, the user accidentally d
250 BTC Lost After Windows Profile Deletion and Repeated System Restore Overwrites
Software wallet
Blocked 2012
In early 2012, a Windows user operating under the handle kentrolla reported losing access to a Bitcoin wallet containing approximately 250 BTC. The wallet.dat f
2012 Electrum Wallet Recovery Attempt: 9-Word Seed Phrase, Missing wallet.dat Backup
Software wallet
Indeterminate 2012
In May 2021, a BitcoinTalk user identified as philipp0815 posted a recovery request for Bitcoin held in an Electrum wallet created in 2012. The user possessed o
Seed unavailable — Bitcoin Core (2012)
Software wallet
Indeterminate 2012
In the era before hierarchical deterministic wallets and seed phrases, Bitcoin holders using the original Bitcoin Core client stored their private keys in a sin
← PreviousNext →
Browse by custody type and stress
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