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

Halving Cycle 1 (2009–2012) — Passphrase unavailable

Passphrase and wallet encryption failures from Halving Cycle 1 (2009–2012). Early wallet software used password-based encryption — forgotten encryption passwords from this period are the earliest documented passphrase failures in the archive.

17 cases in this intersection. 75% of determinate cases resulted in a blocked outcome and 25% in access survived. The most common recovery path is password bruteforce.

Archive analysis — 17 cases
Outcomes
75% of determinate cases resulted in blocked access — 6 percentage points above the archive-wide average of 69%. 25% resulted in recovered access — above the archive average.
Documentation coverage
53% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
94% of cases involved software wallet, followed by hardware wallet (single key) at 6%.
Recovery path
Password Bruteforce is the most documented recovery path (6 cases, 35% of subset).
Documentation
35% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
24% of cases involved large or very large holdings (10+ BTC).
17 observed cases
Blocked
6 (35%)
Survived
2 (12%)
Indeterminate
9 (53%)
BitcoinTalk User ez1btc: Encryption Password Transcription Error Blocks Large Bitcoin Wallet
Software wallet
Indeterminate 2012
In the encrypted wallet recovery thread on BitcoinTalk, user 'ez1btc' documented a custody failure rooted in transcription error rather than forgetfulness. At t
Brad Yasar: Desktop-Mined Bitcoin Locked by Forgotten Passwords
Software wallet
Blocked 2012
Brad Yasar, a Los Angeles-based entrepreneur, mined Bitcoin on multiple desktop computers during the network's earliest years when mining was accessible to indi
Anonymous Reddit User: 7,500 BTC Inaccessible Due to Forgotten Wallet Password
Software wallet
Blocked 2012
An anonymous Reddit user posted in 2014 about a significant custody failure: he had purchased approximately 7,500 Bitcoin in 2012 and stored them in an encrypte
Wallet Encryption Without Post-Encryption Backup: 5 BTC Change Address Lost
Software wallet
Indeterminate 2012
In December 2012, a BitcoinTalk user reported a custody failure involving wallet encryption and backup timing. The user had received 10 BTC across two transacti
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
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
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
Bitcointalk User Locks Self Out of Bitcoin Core Wallet After Forgetting Encryption Passphrase
Software wallet
Blocked 2011
In 2011, a user on the Bitcointalk forum reported having encrypted their Bitcoin Core wallet.dat file with a passphrase—a security practice recommended at the t
KnightMB: 370,000 BTC Accumulated in Early Mining, Sold or Lost to Access Failure
Software wallet
Indeterminate 2011
KnightMB, a pseudonymous user on Bitcointalk, posted in 2011 documenting an accumulation of over 370,000 BTC acquired through mining and pool operation during 2
Brad Yasar: Early Miner Locks Out Thousands of BTC Across Multiple Drives
Software wallet
Blocked 2011
Brad Yasar, a Los Angeles-based entrepreneur, mined thousands of Bitcoin on several desktop computers during the earliest years of the network when solo mining
2010 Mining Pool Wallet.dat: Passphrase Lost After Decade of Storage
Software wallet
Indeterminate 2010
Between 2010 and 2011, the source participated in Bitcoin pool mining and retained the resulting wallet.dat file on a local system. The wallet remained untouche
Early Miner Loses 50 BTC: Private Key Gone, Wallet.dat Scattered Across Backup Media
Software wallet
Indeterminate 2010
In August 2017, a Bitcoin user (username lozzauk) posted on BitcoinTalk describing loss of access to a wallet containing approximately 50 BTC plus additional al
Norwegian Student Successfully Recovered Forgotten Bitcoin Wallet Password From 2009
Software wallet
Survived 2009
In 2009, a Norwegian student purchased approximately $27 worth of Bitcoin as part of an academic exploration of the emerging cryptocurrency. The purchase and wa
Kristoffer Koch Recovers 5000 BTC After Forgotten Wallet Password — 2013
Software wallet
Survived 2009
Kristoffer Koch, a Norwegian engineering student, encountered Bitcoin in late 2009 while researching encryption for his university thesis. Intrigued by the emer
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