CustodyStress
Archive › More United States cases › United States — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
United StatesSeed phrase unavailable

United States — Seed phrase unavailable

Cases from the United States where the seed phrase for a self-custody wallet was unavailable, lost, or never recorded. Seed unavailability is the leading cause of permanent access failure in US self-custody cases.

75% of determinate cases in this country with this stress condition resulted in a blocked outcome — 15 points below the global rate of 90% for this stress condition. This country accounts for 10% of all archive cases with this stress condition. The most common recovery path is password bruteforce.

Archive analysis — 16 cases
Outcomes
75% of determinate cases resulted in blocked access — 6 percentage points above the archive-wide average of 69%. 25% resulted in recovered access — above the archive average.
Documentation coverage
50% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
75% of cases involved software wallet, followed by hardware wallet (single key) at 19%.
Documentation
63% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Geographic distribution
United States accounts for 100% of cases in this subset (16 of 16).
Structural dependency
81% of cases carry a undocumented recovery procedure dependency tag — the most common structural factor in this subset.
16 observed cases
Blocked
6 (38%)
Survived
2 (13%)
Indeterminate
8 (50%)
Los Angeles Wildfire Destroys Only Seed Phrase Backup — Total Loss
Software wallet
Blocked 2025
In January 2025, a Reddit user reported that their 70-year-old aunt had lost her entire cryptocurrency savings during the Los Angeles wildfires. The aunt had st
Bitcoin Core Wallet Encryption Generated New Seed: Lost Access to Funded Addresses
Software wallet
Blocked 2024
In June 2024, a Bitcoin Core user deleted their server and all associated data, but retained a backup copy of wallet.dat on their computer. The user encrypted t
Coinbase Wallet $15,000 Loss: Deferred Seed Phrase, iPhone Update, No Recovery
Software wallet
Indeterminate 2021
A long-term Coinbase customer transferred approximately $15,000 USD to a newly created Coinbase Wallet in February 2021, intending to access Uniswap for decentr
Missing 2 of 12 Mnemonic Words: Brute Force Recovery Feasibility
Hardware wallet (single key)
Indeterminate 2020
In March 2020, a Bitcoin holder wrote their 12-word BIP39 mnemonic on paper. During storage or handling, the last two words were torn away and lost, leaving onl
Wallet.dat Corruption and Salvage Failure After Bitcoin.org Wallet Import
Software wallet
Blocked 2020
An individual who ran Bitcoin software during 2009 and 2010 located an old data file (renamed to xxxx.dat) years later and attempted to recover it. In July 2020
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
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
Ledger Nano S: 23 of 24 Mnemonic Words with Passphrase, Missing Final Word
Hardware wallet with passphrase
Indeterminate 2018
In May 2018, a Ledger Nano S user accidentally wiped their device during testing and discovered they had retained 23 of 24 seed words, written down in order, pl
Mark Frauenfelder's 7.4 BTC: Seed Phrase Discarded by Housecleaner, Recovered via Hardware Vulnerability
Hardware wallet (single key)
Survived 2017
Mark Frauenfelder, editor-in-chief of Boing Boing and Wired contributor, purchased 7.4 Bitcoin in January 2016 for approximately $3,000 and transferred it to a
25 Bitcoin Lost After Computer Crash: Wallet Identity Unknown
Software wallet
Indeterminate 2017
In November 2017, a Bitcoin Stack Exchange user disclosed that they had purchased 25 bitcoins years prior and deposited them into a wallet on a personal compute
Bitcoin Lost After Hard Drive Format: wallet.dat Unrecovered, Private Key Missing
Software wallet
Blocked 2017
A Bitcoin holder received cryptocurrency in 2013 via Bitcoin Core but did not understand the critical role of the wallet.dat file in securing access to funds. I
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
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
2009 Bitcoin Mining Wallet Recovery: Fragmented wallet.dat on Deleted Drive
Software wallet
Indeterminate 2009
TheMadGenius07 downloaded and briefly mined Bitcoin on a high-performance gaming rig in summer 2009, then uninstalled the Bitcoin application when mining activi
Incomplete Mnemonic Seed Phrase: 11 of 12 Words Retained, Missing Word Recovery Feasibility
Software wallet
Indeterminate
A Bitcoin wallet user lost access to one word of their mnemonic seed phrase, retaining only 11 of 12 words. The user became aware that BIP39 uses a curated Engl
Mark Frauenfelder's 7 Bitcoin: Household Cleaner Discards Written Seed Phrase
Hardware wallet (single key)
Survived
Mark Frauenfelder, a US journalist, purchased approximately 7 Bitcoin in early 2016 at roughly $3,000 total investment. As the asset price appreciated significa
More United States cases
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