CustodyStress
Archive › Browse by era and stress › Early Bitcoin (2009–2013) — Device loss
Part of the CustodyStress archive of observed Bitcoin custody incidents
Early BitcoinDevice loss

Early Bitcoin (2009–2013) — Device loss

Device loss cases from Early Bitcoin (2009–2013). The most structurally terminal failure mode of the early period — devices lost before seed phrase standards existed meant no recovery path.

36 cases from this period are included in this archive. 83% of determinate cases resulted in a blocked outcome. The most frequently observed stress condition is device-loss cases.

15
Blocked
0
Constrained
3
Survived
18
Indeterminate

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

36 observed cases
Blocked
15 (42%)
Survived
3 (8%)
Indeterminate
18 (50%)
10 BTC Gifted in 2011, Lost in Unrecoverable Hard Drive Crash
Software wallet
Blocked 2011
Greg received 10 bitcoin as a gift during the earliest phase of Bitcoin adoption, when the asset was trading around 10 cents per coin. The bitcoin was stored on
80 BTC Recovery After Hard Drive Format: Pywallet Raw Data Reconstruction
Software wallet
Survived 2011
In December 2011, a BitcoinTalk user's friend experienced critical wallet inaccessibility when his computer crashed. The friend brought the machine to a technic
Wallet File Swap Causes Transaction Invisibility: Blockchain Index Desynchronization (2011)
Software wallet
Survived 2011
Michael_S was running Bitcoin client version 0.3.19 on Ubuntu Linux in May 2011 and sought to improve security by splitting his holdings across two wallet.dat f
Fragmented Wallet.dat Recovery: Disk Image Mining Loss Without Backup
Software wallet
Indeterminate 2011
In 2011–2012, callerman used Bitcoin-QT to mine Bitcoin on a personal computer with limited technical knowledge of cryptocurrency infrastructure. Facing disk sp
1,000+ BTC from 2010: Lost USB Drive, Corrupted Hardware, Incomplete Seed Recovery
Software wallet
Indeterminate 2010
In 2010, theunionjack purchased over 1,000 Bitcoin at a fraction of a cent by creating two PGP keys using GPG4Win/Kleopatra and importing them into what he beli
Lost Bitcoin Mining Wallet on Decommissioned PC: Data Overwritten Beyond Recovery
Software wallet
Blocked 2010
In 2009 or 2010, rosnick92 and his father mined Bitcoin on a personal computer for several days, earning what he recalls as 'a few pennies per day'—an amount he
10,000 Bitcoin Lost When Laptop Discarded as Junk (2010)
Software wallet
Blocked 2010
In March or April 2010, while a final-year student at St. John's University in New York, an individual purchased 10,000 BTC from a local seller for approximatel
Early Bitcoin Client Wallet Partially Overwritten: File Recovery and Data Loss Analysis
Software wallet
Indeterminate 2010
In January 2010, furyo87 ran the Bitcoin client on a Windows machine for several days while experiencing stability issues. The user was uncertain whether any BT
1,000 BTC Lost to Repeated Hard Drive Formatting: Self-Custody Without Backup
Software wallet
Blocked 2009
In January 2017, a BitcoinTalk forum user identified as myBitcoin2009 posted a recovery request describing a custody loss rooted in the earliest era of Bitcoin
Deleted 2009-2010 Bitcoin Mining Wallet: Disk Overwrite and Recovery Failure
Software wallet
Indeterminate 2009
In December 2017, a BitcoinTalk user identified as idelcoins posted a detailed account of attempting to recover Bitcoin wallet files from hard disks containing
1000 BTC from 2009 Mining: Wallet Recovery After Hard Drive Reformat
Software wallet
Indeterminate 2009
The original poster ('unluckysoul') described losing access to approximately 1000 BTC generated during the earliest Bitcoin mining period using Bitcoin-Qt, the
← PreviousNext →
Browse by era and stress
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