CustodyStress
Archive › Halving cycles › Halving Cycle 1 (2009–2012)
Part of the CustodyStress archive of observed Bitcoin custody incidents

Halving Cycle 1 (2009–2012)

Bitcoin custody incidents from the first halving cycle, before formal wallet standards existed. Hardware wallets did not exist, BIP39 seed phrases had not been standardised, and most Bitcoin was held in unencrypted desktop wallet.dat files. An 84% blocked rate among determinate cases reflects how structurally unrecoverable early Bitcoin custody was.

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

41
Blocked
3
Constrained
5
Survived
38
Indeterminate

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

87 observed cases
Blocked
41 (47%)
Constrained
3 (3%)
Survived
5 (6%)
Indeterminate
38 (44%)
Fiyasko's Forgotten Passphrase: Mining Savings Lost to Single Point of Failure (2012)
Software wallet
Indeterminate 2012
In December 2012, a Bitcoin miner operating under the username Fiyasko (also known as JackRabiit) created a dedicated savings wallet to store one month of accum
Brainwallet Passphrase Mismatch — Address Generation Failure After Fund Transfer
Software wallet
Indeterminate 2012
In December 2012, a BitcoinTalk user identified as 'thoughtfan' encountered a critical custody failure after using brainwallet.org to generate a Bitcoin address
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
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
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
Formatted Computer, Lost Wallet.dat Access—Recovered via Time Machine Backup
Software wallet
Survived 2011
On July 3, 2011, forum user Omega0255 reported a critical custody error with a 1 BTC mining pool payment. The user had formatted their SSD drive using a secure
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
2011 Bitcoin Estate: Encrypted Drives and an Undocumented Private Key
Unknown custody system
Indeterminate 2011
A technology-focused father who held libertarian views died in late 2011, when Bitcoin was trading near $3 per unit. On his deathbed, he transferred several enc
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
Bitomat.pl Exchange Loses 17,000 BTC to AWS Instance Restart
Exchange custody
Constrained 2011
Bitomat.pl operated as the third-largest Bitcoin exchange globally and the largest in Poland during the early 2011 cryptocurrency market. On July 26, 2011, the
BTCex Exchange Users Discover 83% Bitcoin Missing After Temporary Closure
Exchange custody
Blocked 2011
BTCex was a Russian-based cryptocurrency exchange founded in September 2010 that facilitated trades between bitcoin and fiat currencies including Russian Rubles
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
Stefan Thomas and 7,002 Bitcoin: Locked Behind a Forgotten Passphrase
Hardware wallet (single key)
Blocked 2011
Stefan Thomas held 7,002 Bitcoin stored on an encrypted hard drive containing the private keys. Access to the device required a passphrase that Thomas had forgo
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
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
Bitcointalk User Locked Out of Encrypted 2011 Wallet — Passphrase Unrecoverable
Software wallet
Blocked 2011
In early 2013, a Bitcointalk user posted in the Bitcoin Technical Support section describing their inability to access an encrypted wallet created approximately
92 BTC Inaccessible: Passphrase Deleted From Password Manager Vault
Software wallet
Indeterminate 2011
In 2011, a high school graduate purchased approximately 92 BTC for roughly $100 using the Bitcoin reference client on a flash drive. The wallet was encrypted wi
9 Bitcoin Inaccessible: Encrypted Desktop Wallet Software Crash on Passphrase Entry
Software wallet
Indeterminate 2011
In 2011, a Bitcoin user encrypted a desktop software wallet using Bitcoin Core and transferred approximately 9 BTC to it. Only after the transaction confirmed d
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
← PreviousNext →
Halving cycles
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.