CustodyStress
Archive › Browse by outcome and stress › Blocked — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
BlockedSeed phrase unavailable

Blocked — Seed phrase unavailable

Cases where Bitcoin was permanently inaccessible because the seed phrase was unavailable. Seed unavailability with a blocked outcome is the most structurally unrecoverable failure mode in the archive — no seed phrase means no recovery path.

90% of all seed-unavailable cases in the archive result in a blocked outcome. These 69 cases represent the full 90% — the subset where this specific combination of stress condition and outcome is documented. The most common recovery path is estate process.

69
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

69 observed cases
Blocked
69 (100%)
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
Block.io Permanent Loss: Forgotten PIN and Missing Secret Mnemonic Backup
Exchange custody
Blocked 2016
In February 2016, a BitcoinTalk user identifying as CaRLoSXXX posted a distress message after losing access to their Block.io wallet. Block.io is a non-custodia
Blockchain.com Wallet (2016): Partial Password Recovery Attempt, Seed Phrase Absent
Exchange custody
Blocked 2016
The subject created a Blockchain.com account in 2016 and deposited approximately 0.03 BTC (valued at roughly $20 at 2016 exchange rates of $600/BTC). Immediatel
Blockchain.info iOS Wallet: $3,600 Lost to Missing Mnemonic and Unresettable Password
Exchange custody
Blocked 2015
In September 2015, TheLoser created a Bitcoin wallet on Blockchain.info using an iOS mobile device. Unlike documented Blockchain.info workflows, the wallet crea
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
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
Gabriel Abed: 800 BTC Private Keys Destroyed by Accidental Laptop Reformat
Software wallet
Blocked 2011
In 2011, Gabriel Abed, co-founder of Bitt and a prominent figure in Caribbean blockchain infrastructure, lost approximately 800 BTC when a colleague accidentall
Ulti Loses 28 BTC to Incomplete SSD Migration — October 2011
Software wallet
Blocked 2011
On October 1, 2011, a Bitcointalk user identified as Ulti posted an account of a custody failure resulting from routine hardware maintenance. While upgrading hi
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
BitcoinTalk User 'td' Loses 50 BTC Mined Block After Deleting Wallet Without Backup
Software wallet
Blocked 2011
In May 2011, a BitcoinTalk forum user identified as 'td' reported the loss of 50 BTC—the full block reward from a successfully mined block. At the time of loss,
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
26 BTC Lost: Developer Formats Drive Containing Wallet, Gives to Mother-in-Law
Software wallet
Blocked 2011
In October 2021, a Hacker News user identified as jakewins disclosed a significant custody failure from the early Bitcoin era. The user possessed 26 BTC stored
Seed unavailable — software wallet (2010)
Software wallet
Blocked 2010
On July 14, 2010, a BitcoinTalk user with the handle ksd5 reported a critical loss in a forum thread posted just two days after account creation. The user held
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
8,999 BTC Lost to Non-Deterministic Wallet Change Address Design
Software wallet
Blocked 2010
In 2010, a Bitcoin user held approximately 9,000 BTC in a Bitcoin Core wallet. To validate his backup and recovery procedure, he executed a test transaction to
← PreviousNext →
Browse by outcome and stress
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