CustodyStress
Archive › Browse three-way intersections › Software wallet — Seed phrase unavailable — Blocked
Part of the CustodyStress archive of observed Bitcoin custody incidents
Software walletBlocked

Software wallet — Seed phrase unavailable — Blocked

Cases where a software wallet with unavailable seed phrase resulted in permanently blocked access. Without the seed phrase, no recovery path exists — this combination has the highest permanence rate of any self-custody failure pattern.

54 cases in this intersection. 100% of determinate cases resulted in a blocked outcome. The most common recovery path is no path available.

Archive analysis — 54 cases
Outcomes
100% of determinate cases resulted in blocked access — 31 percentage points above the archive-wide average of 69%. Only 0% resulted in recovered access — one of the lower survival rates in the archive.
Documentation
44% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Structural dependency
96% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
54
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

54 observed cases
Blocked
54 (100%)
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
Lost Phone Containing All Wallets; $300 Trapped in Unknown Address
Software wallet
Blocked 2025
On July 7, 2025, a user copied what they believed to be their own wallet address from their phone's clipboard and sent $300 in Bitcoin to it. The transaction co
BitcoinTalk Seed Phrase Loss Reports: Computer Crash, Device Corruption, Paper Wallet Failures
Software wallet
Blocked 2024
On January 26, 2024, BitcoinTalk user riverdip initiated a community thread soliciting incident reports about Bitcoin inaccessibility. The thread surfaced multi
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
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
Bitcoin Armory Private Key Lost After Health Issue: 60 BTC Inaccessible
Software wallet
Blocked 2022
In May 2022, a Bitcoin holder reported losing access to approximately 60 Bitcoin stored in Bitcoin Armory since 2014. The loss occurred following a health probl
Phone Lost With 12-Word Recovery Phrase Stored: Permanent Bitcoin Loss
Software wallet
Blocked 2022
On April 4, 2022, a Bitcoin holder reported losing their mobile phone on which they had stored their 12-word recovery phrase. The user retained knowledge of the
Electrum Watch-Only Wallet With Lost Seed Phrase: No Recovery Path
Software wallet
Blocked 2021
In June 2021, a BitcoinTalk user (Ed801) discovered that their Electrum wallet, created nine months prior in September 2020, had become functionally inaccessibl
Recovery Phrase Failed to Restore Imported Addresses: Funds Permanently Inaccessible
Software wallet
Blocked 2021
A Blockchain.com user had deposited Bitcoin into imported addresses within their wallet application, unaware that funds in imported addresses required separate
Bitcoin Lost After Hard Disk Format Without wallet.dat Backup
Software wallet
Blocked 2021
A Bitcoin Core user received bitcoin in 2013 but did not understand the criticality of wallet.dat at that time. In 2017, the user formatted their hard disk and
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
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
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
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
Recovered 12-Word Seed Phrase but Balance Shows Zero: Imported Address Problem
Software wallet
Blocked 2018
In September 2018, a Bitcoin holder attempted to recover wallet access after forgetting which software they had originally used. They obtained a 12-word recover
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
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
Ruairi's Lost Paper Backup: €80 Bitcoin, Both Credentials on One Document
Software wallet
Blocked 2015
Ruairi purchased approximately €80 worth of Bitcoin in late 2015, driven by curiosity about the emerging technology and its associations with dark web markets.
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
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
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
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
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
← PreviousNext →
Browse three-way intersections
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