CustodyStress
Archive › Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents

Lost Bitcoin seed phrase — documented cases

Cases in this category involve wallets for which the seed phrase could not be located. Without the seed phrase, access to the wallet was not possible.

Browse all archive sections — situations, patterns, dependencies, events →
147 observed cases

Outcome distributions are available in archive statistics.

Custody system
Outcome
Documentation
Year
Dependencies
Country
Incomplete Seed Backup + Device Loss: ipsbruno3's GPU-Powered Recovery Attempt
Software wallet
Indeterminate2026
ipsbruno3 has held Bitcoin since 2013 and stored the majority in a wallet protected by a 12-word BIP39 seed phrase. The holder implemented a four-layer backup s
Los Angeles Wildfire Destroys Only Seed Phrase Backup — Total Loss
Software wallet
Blocked2025
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
Pre-HD Bitcoin Core Wallet Lost in OS Upgrade: Backup Strategy Failure
Software wallet
Indeterminate2025
In June 2025, a Bitcoin forum user reported a custody failure involving a Bitcoin Core wallet created circa 2014, during the era before hierarchical determinist
Lost Phone Containing All Wallets; $300 Trapped in Unknown Address
Software wallet
Blocked2025
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
Blocked2024
On January 26, 2024, BitcoinTalk user riverdip initiated a community thread soliciting incident reports about Bitcoin inaccessibility. The thread surfaced multi
BRD Wallet Access Loss: Incomplete Backup, Missing Seed Phrase
Exchange custody
Blocked2024
MLNiemczyk2411 created a BRD wallet several years before November 2024 but neglected to properly document the recovery materials. During wallet initialization,
Ledger Nano S with Incomplete 9-Word Recovery Phrase: $10K Trapped
Hardware wallet (single key)
Indeterminate2024
In March 2024, a BitcoinTalk user reported that their partner had lost access to a Ledger Nano S purchased approximately seven years earlier. During initial set
Bitcoin Core Wallet Encryption Generated New Seed: Lost Access to Funded Addresses
Software wallet
Blocked2024
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
Lost Recovery Seed on Trezor Hardware Wallet: Permanent Access Failure
Hardware wallet (single key)
Blocked2024
In January 2024, a BitcoinTalk user identified as carlosrodriguez88 reported a critical access failure involving a Trezor hardware wallet running firmware versi
Fragmented BIP39 Seed Recovery: $25M Ethereum Wallet with 6 Missing Words
Hardware wallet (single key)
Indeterminate2024
In November 2024, a Bitcoin Forum user identified as 'yzeb' disclosed a self-inflicted custody access failure involving an Ethereum HD wallet derived from a BIP
Ledger HW1 v1.0.1 Device Locked: Firmware Obsolete, Seed Phrase Lost, No Recovery Path
Hardware wallet (single key)
Blocked2024
In March 2024, a BitcoinTalk forum user (nimrodlehavi) reported complete inability to access Bitcoin stored on a Ledger HW1 version 1.0.1 hardware wallet. The u
Deleted wallet.dat Recovery Attempt: Corruption Barrier (Tigerbill, May 2023)
Software wallet
Indeterminate2023
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
Incomplete Seed Phrase and Lost Email Access Lock Blockchain.info Wallet
Exchange custody
Indeterminate2023
In September 2023, a forum user posted on behalf of an elderly relative seeking recovery assistance for a Bitcoin wallet created on Blockchain.info in 2015 or 2
Corrupted Bitcoin Core wallet.dat: Encrypted mkey Recovery Without Wallet Access
Software wallet
Indeterminate2023
A Bitcoin Core user encountered wallet corruption and successfully extracted a 94-digit encrypted master key (mkey) from the damaged wallet.dat file. The user r
Seed Phrases Lost in Computer Reformat — angrybirdy's Unrecoverable Self-Custody Failure
Software wallet
Blocked2023
angrybirdy, a BitcoinTalk Sr. Member, accumulated Bitcoin through legitimate cryptocurrency work: signature campaigns and white paper translation projects condu
Lost Seed Phrase and 2FA Access on Coinbase Commerce Self-Custody Wallet
Exchange custody
Indeterminate2022
In December 2022, a Coinbase Commerce user (cryptoask2022) encountered a cascading custody failure after losing access to their self-managed wallet. The user re
Bitcoin Core Wallet Database Corruption: Berkeley DB Panic Blocks 2016 Backup Access
Software wallet
Indeterminate2022
In January 2022, a BitcoinTalk user (cold_chardonnay) located a wallet.dat backup file from approximately 2016 stored on a backup disc. The user had minimal Bit
Lost 3 of 12 Mnemonic Words With Unknown Word Order — Brute-Force Recovery Attempted
Software wallet
Indeterminate2022
In early 2022, a Bitcoin holder discovered they had lost three words from a twelve-word mnemonic seed phrase and could not reliably recall the order of the rema
Bitcoin Armory Private Key Lost After Health Issue: 60 BTC Inaccessible
Software wallet
Blocked2022
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
Blocked2022
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
← PreviousPage 1 of 8
Other stress categories
By structural dependency
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