CustodyStress
Archive › Browse by era and custody type › Early Bitcoin (2009–2013) — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Early BitcoinSoftware wallet

Early Bitcoin (2009–2013) — Software wallet

Software wallet failures from Early Bitcoin (2009–2013). The earliest documented custody failures involve wallet.dat files, unencrypted keys, and hardware discarded before seed phrase standards existed.

118 cases from this period are included in this archive. 75% of determinate cases resulted in a blocked outcome. The most frequently observed stress condition is passphrase-unavailable cases.

42
Blocked
1
Constrained
13
Survived
62
Indeterminate

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

118 observed cases
Blocked
42 (36%)
Constrained
1 (1%)
Survived
13 (11%)
Indeterminate
62 (53%)
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
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
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
533 BTC Inaccessible After Brother's Death; Laptop Hard Drive Removed and Lost
Software wallet
Indeterminate 2010
Shotukan purchased 533 BTC in 2010 for approximately $60, storing the private keys on a Dell laptop's wallet.dat file. He later gave the laptop to his brother,
Stone Man Loses 8,999 BTC to Unbacked Change Address After Live CD Shutdown
Software wallet
Blocked 2010
In August 2010, a BitcoinTalk user known as Stone Man purchased 9,000 BTC on an exchange and transferred them to a Bitcoin client running on a Debian Linux live
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 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
PC Miner Overwrites wallet.dat During OS Reinstall, Loses ~12 BTC (2010)
Software wallet
Blocked 2010
In 2010, the user known as 'kingcharles' was mining Bitcoin on a personal computer during the currency's early adoption phase. At that time, mined bitcoins were
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
2009 Bitcoin Purchase Lost to Paper Backup Destruction and Device Absence
Software wallet
Indeterminate 2009
Plinxer, a BitcoinTalk user, posted in May 2023 describing a Bitcoin purchase made in 2009 for approximately £50 (then ~$60–65 USD). The transaction occurred vi
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
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
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
← Previous
1345
Next →
Browse by era and custody type
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