CustodyStress
ArchiveSingle-Person Knowledge › Seed Unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents

Single-Person Knowledge — Seed Unavailable

Cases where operational knowledge of the custody arrangement existed only with the holder. No second person had sufficient understanding to execute recovery independently. This page shows archive cases where both conditions were present.

79% of all Seed Unavailable cases in the archive involve this structural dependency. Among them, 93% of determinate cases resulted in a blocked outcome. The most common recovery path is password bruteforce.

56
Blocked
0
Constrained
4
Survived
64
Indeterminate

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

124 observed cases
Blocked
56 (45%)
Survived
4 (3%)
Indeterminate
64 (52%)
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
2013 Bitcoin Core Wallet.dat Corruption After Version Incompatibility
Software wallet
Indeterminate 2013
The subject purchased a used desktop computer from a thrift store and discovered an installed Bitcoin QT client with an associated wallet.dat file dating to 201
Inherited 2009 Bitcoin Mining Hard Drive: Unrecoverable wallet.dat After OS Reinstall
Software wallet
Indeterminate 2013
A Bitcoin holder inherited a hard drive from their father's computer, which had been used for Bitcoin mining in November 2009. The drive had been powered down a
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
2012 Electrum Wallet Recovery Attempt: 9-Word Seed Phrase, Missing wallet.dat Backup
Software wallet
Indeterminate 2012
In May 2021, a BitcoinTalk user identified as philipp0815 posted a recovery request for Bitcoin held in an Electrum wallet created in 2012. The user possessed o
Seed unavailable — Bitcoin Core (2012)
Software wallet
Indeterminate 2012
In the era before hierarchical deterministic wallets and seed phrases, Bitcoin holders using the original Bitcoin Core client stored their private keys in a sin
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
Father Lost Access to 1,500 BTC on Hardware Wallet—Child Attempts Recovery
Hardware wallet (single key)
Indeterminate 2011
A father purchased approximately 1,500 Bitcoin around 2011 and stored them on a hardware wallet. At some point, access to the device was lost—either through for
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
30+ BTC Sent to Wrong Address in 2011: Private Key Never Located
Software wallet
Indeterminate 2011
In 2011, blocparty_ received approximately 30 BTC from an exchange and transferred the amount (minus fees) to what they believed was a secondary address of thei
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
2010 Bitcoin Wallet Deleted and Partially Recovered: Data Integrity Compromised by Subsequent Disk Writes
Software wallet
Indeterminate 2010
rok95 mined Bitcoin using CPU mining in 2010 during the network's earliest phase, when such activity was accessible to casual users with standard computing hard
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
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
Multibit Desktop Wallet: Bitcoin Inaccessible After Platform Closure and File Loss
Software wallet
Blocked
A professional received a Bitcoin payment to an address generated by Multibit, a lightweight desktop wallet widely used during the early-to-mid 2010s. At the ti
Desktop Software Wallet Erased During PC Reset — Seed Phrase Never Recorded
Software wallet
Blocked
A Bitcoin holder maintained their first cryptocurrency wallet as a hot wallet on a personal computer, following a common early-adoption pattern of minimal secur
← PreviousNext →
Related archive views
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