CustodyStress
Archive › Recovery paths › Seed Phrase Located
Part of the CustodyStress archive of observed Bitcoin custody incidents

Seed Phrase Located

Cases where recovery succeeded or was attempted by locating a previously unknown or forgotten seed phrase backup.

Seed phrase recovery succeeds in 83% of determinate cases — when the seed exists and can be located, recovery is typically straightforward regardless of device loss. The majority of blocked cases in this path involve seeds that were partially damaged or only partially recorded.

Archive analysis — 17 cases
Outcomes
8% of determinate cases resulted in blocked access — 61 percentage points below the archive-wide average of 69%. 83% resulted in recovered access — above the archive average.
Custody type
65% of cases involved software wallet, followed by exchange custody at 24%.
Primary stress condition
35% of cases involve device loss. Passphrase unavailable accounts for a further 24%.
Documentation
76% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
82% of cases carry a undocumented recovery procedure dependency tag — the most common structural factor in this subset.
1
Blocked
1
Constrained
10
Survived
5
Indeterminate

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

17 observed cases
Blocked
1 (6%)
Constrained
1 (6%)
Survived
10 (59%)
Indeterminate
5 (29%)
Blockchain.info Legacy Wallet Recovery: Partial Success via btcrecover, Platform Access Blocked
Exchange custody
Constrained 2025
Between 2013 and 2015, a user in Taiwan established multiple Blockchain.info wallets and created printed paper backups containing wallet GUIDs, passwords, and 1
Partial Seed Backup + Missing Passphrase Flag: BTCRecover Recovery Success
Software wallet
Survived 2025
gab0miner created an Electrum wallet offline using a Linux Live CD on an unspecified date, recording only 11 of the required 12 BIP39 seed words into KeePass al
External Hard Drive Theft with Private Key Recovery Attempt
Software wallet
Indeterminate 2024
On May 26, 2024, a BitcoinTalk user (Niandertal@2024) reported the theft of an external hard drive containing a Bitcoin wallet file. The user had retained posse
Samourai Wallet Seizure: Recovering Bitcoin After Platform Shutdown
Software wallet
Survived 2024
On April 28, 2024, a BitcoinTalk user reported that Bitcoin deposited to their Samourai Wallet became inaccessible following the FBI's shutdown of the platform.
Trezor Passphrase Forgotten After Factory Reset — Successful Recovery via Community Support
Hardware wallet with passphrase
Survived 2024
BTCRSMD, a moderately experienced Bitcoin user, executed a deliberate custody strategy in July 2024. The user purchased Bitcoin via Swan and routed the coins th
Inherited Bitcoin Recovery After Mother's Death: 10 BTC Sold, Remainder Secured
Software wallet
Survived 2020
A sole heir inherited Bitcoin holdings from their mother, who died the day after Thanksgiving 2020. The heir possessed complete recovery documentation: a 12-wor
Lost Copay Phone With Recovery Seed: Device Access Gone, Funds Technically Recoverable
Software wallet
Indeterminate 2020
In February 2026, a BitcoinTalk user posted on behalf of a Bitcoin holder who had lost physical access to an iPhone or Android device containing a Copay wallet
0.19 BTC Recovery Attempt After Bitcoin Core Crash and Wallet.dat Restoration
Software wallet
Indeterminate 2019
In August 2019, owenzane posted to the Bitcoin Technical Support forum seeking help recovering 0.19 BTC from a wallet he had created and backed up approximately
Computer Crash with wallet.dat Backup: Bitcoin Core Recovery Without Private Key Export
Software wallet
Survived 2018
In February 2018, a Bitcoin Core user experienced a total computer crash requiring complete system reinstallation. The user had previously used an Armory wallet
Blockchain.info Wallet Access Lost After Signup—Recovery Phrase Known
Exchange custody
Indeterminate 2018
On March 16, 2018, a user with the handle ilovegambling created a new Blockchain.info wallet to receive Bitcoin from an online betting platform. The user record
MultiBit Classic Password Lock: Recovery Through Backup Key File Import
Software wallet
Survived 2018
A BitcoinTalk user (cluuze130) deposited Bitcoin into MultiBit Classic approximately one year before attempting withdrawal in February 2018. At the time of depo
Blockchain.info Legacy Wallet: Mnemonic Present, Backup File Present—Funds Inaccessible
Exchange custody
Blocked 2015
In 2015, the user created a Blockchain.info wallet and purchased Bitcoin, then implemented two backup strategies: a 17-word legacy mnemonic phrase and an encryp
Recovery of Dormant Blockchain.info Wallet via Legacy 20-Word Mnemonic (2017)
Exchange custody
Survived 2014
Roland808, a BitcoinTalk user, discovered a text file on their computer in March 2017 dated from 2014 containing a label 'bitcoin nmemonic' followed by 20 rando
2012 Bitcoin Core Wallet Lost to PC Crash: Backup Files Exist, Access Blocked
Software wallet
Indeterminate 2012
In August 2020, a Bitcoin holder posted to Bitcoin Stack Exchange describing a custody failure spanning eight years. The individual had downloaded a GUI miner o
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
Android Smartphone Theft: Bitcoin Recovery via Archived Email Wallet Backup
Software wallet
Survived
An Android smartphone user experienced theft of an older device worth approximately $80. The phone contained a mobile wallet application with roughly $150 in Bi
Armory Wallet Sync Failure: 2 BTC Recovered Through Manual Key Export
Software wallet
Survived
A user transferred 2 BTC from Coinbase to a self-hosted Armory wallet in multiple transactions approximately three years before attempting recovery. Both a pape
Recovery paths
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