CustodyStress
Archive › Browse by halving cycle and stress › Halving Cycle 1 (2009–2012) — Device loss
Part of the CustodyStress archive of observed Bitcoin custody incidents
Cycle 1Device loss

Halving Cycle 1 (2009–2012) — Device loss

Device loss cases from Halving Cycle 1 (2009–2012). No seed phrase standard existed — the device held the only copy of the keys. Device loss in this period is almost universally terminal.

27 cases in this intersection. 82% of determinate cases resulted in a blocked outcome and 18% in access survived. The most common recovery path is no path available.

Archive analysis — 27 cases
Outcomes
82% of determinate cases resulted in blocked access — 13 percentage points above the archive-wide average of 69%.
Documentation coverage
59% of cases have indeterminate outcomes — higher than the archive average of 43%.
Documentation
30% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
19% of cases involved large or very large holdings (10+ BTC).
Structural dependency
100% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
9
Blocked
0
Constrained
2
Survived
16
Indeterminate

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

27 observed cases
Blocked
9 (33%)
Survived
2 (7%)
Indeterminate
16 (59%)
Deep Freeze Software Erases Bitcoin Wallet.dat Before Incoming Payment
Software wallet
Blocked 2012
In September 2012, a Bitcoin user operating under the handle blackjhon909 discovered that their Bitcoin wallet had become inaccessible following an unexpected s
Mac Formatted Without Backup: wallet.dat Recovery Attempt (2012)
Software wallet
Indeterminate 2012
On July 5, 2012, forum user Mashrock reported formatting a Mac computer running OS X 10.7 and subsequently losing access to Bitcoin stored in a wallet.dat file.
Accidental Windows User Account Deletion: 78 BTC Wallet.dat Lost Without Backup
Software wallet
Indeterminate 2012
On April 28, 2012, a Bitcoin Forum user under the alias 'spinnin' reported a critical custody failure. The user had generated 78 BTC using the official Bitcoin
1,300 BTC Inaccessible: BitLocker Encryption Key Lost on Failed Flash Drive
Software wallet
Indeterminate 2012
In June 2012, forum user mb300sd disclosed on BitcoinTalk's 'known lost bitcoins' thread that approximately 1,300 BTC had become permanently inaccessible due to
Early CPU Miner Loses 27,000 BTC to Unrecoverable Drive Failure
Software wallet
Blocked 2012
Dalkore mined 27,000 BTC during Bitcoin's earliest period using CPU mining, when the network was still in its first year and coins carried no meaningful market
Opticbit Loses 2 BTC After CyanogenMod 9 Flash Without Locatable Wallet Backup
Software wallet
Blocked 2012
On June 25, 2012, a Bitcoin user operating under the handle opticbit reported the loss of 2 BTC stored in a mobile wallet on an Android phone. The loss occurred
Campbell Simpson Discards 1,400 BTC on Failing Hard Drive Without Backup
Software wallet
Blocked 2012
Campbell Simpson, editor of Gizmodo Australia, purchased approximately 1,400 Bitcoin in early 2010 when a single coin traded for roughly 1.5 cents, investing ar
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
Scattered Wallet Fragments: Passphrase Known, Decryption Blocked by Checksum Failure
Software wallet
Indeterminate 2012
Between 2011 and 2012, a user mined Bitcoin using Bitcoin-QT on a personal computer. Lacking technical knowledge about the software and wallet format, he delete
Unauthorized Drive Format and Corrupted Wallet File Recovery Failure (2011)
Software wallet
Indeterminate 2011
On September 17, 2011, a Bitcoin holder identified as cablepair discovered that an office network administrator had reformatted the hard drive of a shared offic
Corrupted wallet.dat Recovery After Hard Drive Failure: 2011 Case Study
Software wallet
Indeterminate 2011
In May 2011, forum user zrataj (John) experienced a critical storage failure when his hard drive crashed, destroying both his primary wallet.dat file and the ba
33.54 BTC Trapped in Corrupted Bitcoin-Qt Wallet Since 2011
Software wallet
Indeterminate 2011
In December 2017, a BitcoinTalk user identified as ketubi posted about 33.54 BTC held in a corrupted wallet.dat file from Bitcoin-Qt version 0.4.0. The last rec
Corrupted wallet.dat from 2011 Hard Drive — Fire Damage and Data Loss
Software wallet
Indeterminate 2011
In January 2021, a forum user known as 'french' reported discovering a wallet.dat file on a hard drive that had experienced both partial data erasure and fire d
Corrupted ext3 Hard Drive & Fragmented wallet.dat: HEX-Level Recovery Attempt (2011)
Software wallet
Indeterminate 2011
In June 2011, a Bitcoin holder identified as TurboIan reported catastrophic custody failure on a 65 GB ext3-formatted Linux hard drive. The drive suffered files
2010–2011 Windows XP GPU Mining Recovery: Unknown Pool, Lost Wallet Metadata, No Seed Record
Software wallet
Indeterminate 2011
ALANL ran continuous GPU mining on Windows XP using a GeForce 8800 GT graphics card for approximately three months in 2010–2011. The card eventually burned out
Device discarded — software wallet (2011)
Software wallet
Blocked 2011
In 2011, when Bitcoin mining was still largely a hobbyist pursuit, the user identified as 'bubbabojangles' mined 103 BTC using standard desktop equipment. At th
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
← PreviousNext →
Browse by halving cycle 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