CustodyStress
Archive › Browse by trigger and stress condition › File Deleted — No Backup — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
File_deleted_no_backupSeed phrase unavailable

File Deleted — No Backup — Seed phrase unavailable

Cases where deleting a wallet file with no backup produced a seed-unavailable condition. The wallet file was the only copy of the key material.

22 cases in this intersection. 91% of determinate cases resulted in a blocked outcome and 9% in access survived. The most common recovery path is no path available.

Archive analysis — 22 cases
Outcomes
91% of determinate cases resulted in blocked access — 22 percentage points above the archive-wide average of 69%.
Documentation coverage
50% of cases have indeterminate outcomes — higher than the archive average of 43%.
Documentation
73% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Time distribution
Cases span 2010–2023. Only 9% occurred in 2022 or later — concentrated in earlier periods.
Structural dependency
100% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
10
Blocked
0
Constrained
1
Survived
11
Indeterminate

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

22 observed cases
Blocked
10 (45%)
Survived
1 (5%)
Indeterminate
11 (50%)
Deleted wallet.dat Recovery Attempt: Corruption Barrier (Tigerbill, May 2023)
Software wallet
Indeterminate 2023
In May 2023, Tigerbill, a junior member of the BitcoinTalk forum, permanently deleted their wallet.dat file containing an unspecified quantity of Bitcoin. The u
Seed Phrases Lost in Computer Reformat — angrybirdy's Unrecoverable Self-Custody Failure
Software wallet
Blocked 2023
angrybirdy, a BitcoinTalk Sr. Member, accumulated Bitcoin through legitimate cryptocurrency work: signature campaigns and white paper translation projects condu
1.5M Dogecoins Trapped in Corrupted wallet.dat: Recovery Attempt Stalled
Software wallet
Indeterminate 2021
In 2013, the user purchased over 3,000,000 dogecoins for approximately $1,000 USD. After spending roughly half, they retained 1,500,000 dogecoins and created a
Bitcoin-qt wallet.dat Corruption: Passphrase Known, File Unrecoverable
Software wallet
Indeterminate 2017
A BitcoinTalk user identified as 'lolika' posted a recovery request on December 1, 2017, describing a corrupted Bitcoin Core wallet.dat file created between 201
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
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
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
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
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
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
MultiBit Wallet Deletion and File Corruption: ~100 BTC Permanent Loss
Software wallet
Blocked 2011
In March 2013, a Bitcoin holder generated a private key from a passphrase using bitaddress.org on a Xubuntu Live CD, then imported it into MultiBit desktop wall
1,000 BTC Lost After Accidental Deletion of GPG-Encrypted Dropbox Wallet File
Software wallet
Blocked 2011
An early Bitcoin contributor made a generous gift of 1,000 BTC to the brother of a Hacker News user, with a casual remark that it would someday be valuable. The
AWS EC2 and Local VM Wallet Deletion: Early Backup Failure Pattern
Software wallet
Blocked 2011
In May 2011, BitcoinTalk user opticbit reported losing approximately 0.01 BTC stored on an AWS EC2 instance that was subsequently deleted, and an additional sma
Davyd Arakhamia Loses 400 BTC After Deleting Encrypted Key File
Software wallet
Blocked 2011
Davyd Arakhamia, a Ukrainian entrepreneur and later member of the Verkhovna Rada (elected 2019), accumulated approximately 400 BTC through a business that accep
2,700 BTC Lost to Antivirus Deletion and Unverified Drive Format
Software wallet
Blocked 2010
An individual received a hard drive containing a wallet.dat file—allegedly holding approximately 2,700 BTC—sent by an early Bitcoin adopter around 2010 via emai
9,000 BTC Lost to Unrebacked Change Address: Early Bitcoin Wallet Flaw (2010)
Software wallet
Blocked 2010
In August 2010, a Bitcoin user purchased 9,000 BTC and conducted a single test transaction: sending 1 BTC to his own address to confirm network functionality. T
350 Bitcoin Wallet.dat Deleted During OS Reinstall — Data Recovery Attempted
Software wallet
Indeterminate
An individual who had acquired approximately 350 bitcoin at roughly $10 per coin maintained the wallet as an encrypted wallet.dat file stored in cold storage on
MultiBit Wallet Lost to Full Drive Format — Single Backup Copy Destroyed
Software wallet
Indeterminate
An early Bitcoin adopter stored their MultiBit wallet file (.wallet extension) exclusively on their Windows C: drive without creating any external backup. Multi
Electrum Wallet File Overwritten: New Wallet Lost Without Seed Phrase Backup
Software wallet
Blocked
An Electrum 1.9.8 user attempted to consolidate Bitcoin holdings by creating a new wallet to replace a bloated default_wallet file. The procedure involved openi
Notepad Backup Illusion: Seed Phrases Lost After Mobile Phone Firmware Reset
Software wallet
Blocked
A cryptocurrency holder maintained seed phrases for Bitcoin, Monero, and Ethereum in a notepad application on their mobile phone. The strategy reflected a funda
2011 Bitcoin Wallet Lost After Hard Drive Formatted Twice: Passphrase Retained, File Unrecoverable
Software wallet
Indeterminate
In 2011, an individual purchased Bitcoin and generated a wallet using Bitcoin-Qt or a similar early desktop client software. The wallet created an encrypted wal
Unverified Wallet File Recovery After Drive Format: 2010 GPU-Mined Bitcoin
Software wallet
Indeterminate
In 2010, during Bitcoin's GPU-mining era, the user mined a small quantity of Bitcoin on a desktop computer. Years later, the user deleted the wallet.dat file an
Browse by trigger and stress condition
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