CustodyStress
Archive › Browse by trigger and custody type › Device Discarded — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Device_discardedSoftware wallet

Device Discarded — Software wallet

Cases where a mobile or desktop wallet device was discarded without securing the keys. Most cases involve computers or phones disposed of during hardware upgrades.

62 cases in this intersection. 79% of determinate cases resulted in a blocked outcome and 21% in access survived. The most common recovery path is no path available.

19
Blocked
0
Constrained
5
Survived
38
Indeterminate

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

62 observed cases
Blocked
19 (31%)
Survived
5 (8%)
Indeterminate
38 (61%)
Hard Drive Format Recovery: 2 BTC Restored via Sector Scanning and wallet.dat Reconstruction
Software wallet
Survived 2015
In approximately 2015, marilyn4325 formatted a hard drive and installed Windows 10, intending to preserve wallet data via backup first. However, the backup beca
ASUS Netbook Wallet Deletion: Corrupted Files Block $9,000 Recovery Effort
Software wallet
Indeterminate 2014
In January 2014, Igor76200 purchased a second-hand ASUS Eee PC 1001PX netbook and created approximately 5–6 Bitcoin wallets on it on January 7, 2014. The user c
Armory Wallet Lost via VirtualBox Snapshot Rollback—Binary Recovery Attempt
Software wallet
Indeterminate 2013
In October 2013, a BitcoinTalk user known as HowlingMad lost access to 6.59159344 BTC stored in Armory, a then-leading Bitcoin wallet application running on Win
Encrypted Wallet Recovery After Accidental Partition Deletion (2013)
Software wallet
Indeterminate 2013
On July 17, 2013, a Bitcoin holder identified as Praxis posted to a cryptocurrency forum after losing access to multiple wallet files stored in hidden Linux dir
1,000 BTC Permanently Lost After Brother Deletes wallet.dat From Shared Dropbox Folder
Software wallet
Blocked 2013
In 2017, Hacker News user illumin8 disclosed a permanent loss of 1,000 BTC resulting from a wallet file deletion in a shared Dropbox folder. The Bitcoin wallet
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
Multibit Wallet Lost After Mac Reformat Without Backup
Software wallet
Indeterminate 2013
In November 2013, a BitcoinTalk user identified as funkonaut posted about losing access to their Bitcoin holdings following a critical self-inflicted data loss
Bitcoin-Qt Wallet Loss: Executable Backup Without Private Key File (2013)
Software wallet
Blocked 2013
TheD1ceMan, a forum user, experienced an irrecoverable loss of approximately 1.8 BTC (valued at $2,300–$2,700 USD at May 2013 market prices) due to a critical m
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Software wallet
Blocked 2013
James Howells, a UK resident, discarded a hard drive containing an encrypted Bitcoin wallet during a routine office clearance in 2013. The device was disposed o
Australian Miner Loses Early Bitcoin When Sole USB Backup Drive Fails Irrecoverably
Software wallet
Blocked 2013
Alex, an Australian Bitcoin miner based in Melbourne, mined Bitcoin around 2010 when mining was still a hobbyist activity with negligible monetary value. Unlike
Maxime: Hard Drive Corruption Destroyed Only Copy of Seed Phrase
Software wallet
Blocked 2013
Maxime, a Canadian journalist, began mining Bitcoin during the 2012–2013 period when the technology represented an emerging alternative financial system. He suc
Multibit Wallet Recovered From Formatted Hard Drive After 5 Years
Software wallet
Survived 2013
In 2013, a Bitcoin holder stored funds in a Multibit wallet on a work desktop computer. The hard drive was subsequently formatted, and the user assumed the Bitc
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.
Private Key Accessible but Wallet Balance Unrecoverable: bread45's 2011 Mt.Gox Withdrawal
Software wallet
Indeterminate 2012
In June 2011, bread45 purchased Bitcoin on Mt.Gox and transferred coins to Bitcoin-QT desktop wallet software for self-custody. In 2012, the user accidentally d
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
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
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
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
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
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
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
← PreviousNext →
Browse by trigger 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