CustodyStress
Archive › Browse by halving cycle and custody type › Halving Cycle 3 (2017–2020) — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Cycle 3Software wallet

Halving Cycle 3 (2017–2020) — Software wallet

Software wallet failures from Halving Cycle 3 (2017–2020). The largest cohort of new Bitcoin holders yet encountered passphrase and seed phrase failures after acquiring via mobile wallets during the 2017 cycle.

97 cases in this intersection. 70% of determinate cases resulted in a blocked outcome and 30% in access survived. The most common recovery path is no path available.

26
Blocked
0
Constrained
11
Survived
60
Indeterminate

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

97 observed cases
Blocked
26 (27%)
Survived
11 (11%)
Indeterminate
60 (62%)
Jaxx Mobile Wallet — Permanent Loss After Android Factory Reset Without Seed Backup
Software wallet
Blocked 2017
In September 2017, a BitcoinTalk user (Mikekom) reported installing the Jaxx wallet application on an Android smartphone to hold Bitcoin earned by their 13-year
JAXX Multi-Platform Wallet Sync Failure: 1+ BTC Access Loss
Software wallet
Indeterminate 2017
On September 29, 2017, a BitcoinTalk user (93Vette) discovered a critical design flaw in the JAXX multi-platform wallet. The user had maintained two separate JA
Homeland Security Bitcoin Seizure: Unencrypted Seed Phrase Discovered During Search
Software wallet
Blocked 2017
BurtW, a BitcoinTalk forum user, revealed in April 2017 that he had been arrested and that Homeland Security conducted searches of both his home and office. Dur
Corrupted Bitcoin QT wallet.dat: Undelete and Hex Editor Recovery Attempt
Software wallet
Indeterminate 2017
In March 2017, a Bitcoin user identified as Sammo619 described a custody failure involving a Bitcoin QT Core wallet created in 2014. All backups of the wallet.d
20+ Bitcoin Lost to Double Hard Drive Format; Renamed Wallet File Unrecoverable
Software wallet
Indeterminate 2017
Speed1987 (David) acquired at least 20 BTC in 2010 and stored the wallet file on his personal computer's hard drive. To obscure the wallet from potential attack
Anonymous College Student: 40 BTC Locked Behind Forgotten Wallet Password (2017)
Software wallet
Indeterminate 2017
In late 2017, during Bitcoin's historic rally to $15,000–$19,000, an anonymous college student posted on Reddit describing a custody catastrophe rooted in 2013
MultiBit Wallet Password Forgotten: Encrypted Backup Available but Inaccessible
Software wallet
Indeterminate 2017
On December 30, 2017, a Bitcoin holder posted to Stack Exchange describing a custody failure involving MultiBit, a desktop software wallet popular during the mi
Electrum Wallet Loss: Seed Phrase and Password Both Forgotten
Software wallet
Indeterminate 2017
In November 2024, a BitcoinTalk user identified as supersayajin8 sought help recovering an Electrum wallet created in 2017. The user had lost two critical piece
Hidden Line Feed Character Blocks Bitcoin Core Wallet Access
Software wallet
Survived 2017
In February 2017, scutzi128 documented a Bitcoin Core wallet access failure on the Bitcoin Technical Support forum. The user had encrypted their wallet with a 2
1,000 BTC Lost to Repeated Hard Drive Formats: 2009 Wallet Recovery Attempt
Software wallet
Indeterminate 2017
In January 2017, a BitcoinTalk forum user identified as myBitcoin2009 disclosed a custody failure spanning eight years. The user claimed to have received over 1
Corrupted 2013 wallet.dat Recovery via Community-Guided Disk Scanning
Software wallet
Survived 2017
In December 2017, a macOS Bitcoin Core user attempted to restore access to two wallet.dat files created in late 2013. The user had downloaded a contemporary ver
Bitcoin Core Wallet Password Not Recognized After Encryption and Crash
Software wallet
Indeterminate 2017
In February 2017, a Bitcoin Core user encrypted their wallet using a 5-digit password they used on another application. During the encryption process, the softw
Bitcoin Core Wallet Lost When Computer Discarded Without Backup
Software wallet
Blocked 2017
In November 2017, a Bitcoin holder posted to Bitcoin Stack Exchange seeking recovery options after a critical custody failure. The user had purchased Bitcoin se
Bitcoin Core Passphrase Lost After 7-Year Hiatus — Forgotten 2011 Wallet
Software wallet
Indeterminate 2017
In August 2017, a Bitcoin Core user reported regaining access to a wallet installed on macOS that had remained untouched since 2011. Upon opening the wallet for
Bitcoin Core wallet.dat Corruption: Encrypted Wallet Unlock Failure
Software wallet
Indeterminate 2017
On July 27, 2017, forum user Houdini7 reported that their Bitcoin Core wallet, which had been active for approximately two days, began displaying a critical err
Lost Bitcoin on Offline IDE Drive: 2010 Purchase, 7-Year Gap, Unknown Recovery
Software wallet
Indeterminate 2017
Sara Smit posted to a Bitcoin forum on December 17, 2017, describing a custody failure spanning approximately seven years. She reported purchasing Bitcoin in 20
MultiBit 0.5.1 macOS: Password Recovery Hung, Seed Words Portable
Software wallet
Indeterminate 2017
In June 2017, a BitcoinTalk forum user identified as tomfoolery40 reported a custody access failure involving MultiBit version 0.5.1 on macOS 10.12.2. The user
Wallet File Corruption After Windows Reinstall: Litecoin Locked Despite Correct Passphrase
Software wallet
Blocked 2017
SnowRoll purchased Litecoin on a Windows 10 desktop in April 2017, encrypting the wallet with a self-selected passphrase. After two transactions, the user encou
Mycelium Mobile Wallet Balance Access Failure — December 2017
Software wallet
Indeterminate 2017
In mid-December 2017, a Bitcoin user (Myrr) discovered a critical custody access failure in the Mycelium mobile wallet on their iPhone. The user had purchased B
Accidental Wallet.dat Deletion on Mac SSD — Unrecoverable Bitcoin Loss
Software wallet
Indeterminate 2017
On November 2, 2017, a Bitcoin user identified as chrisf199 posted on BitcoinTalk seeking professional help to recover a wallet.dat file they had accidentally d
BIP38 Paper Wallet Passphrase Lost — 0.7 BTC Inaccessible (2020)
Software wallet
Indeterminate 2017
A BitcoinTalk user (arkaraj) purchased approximately 0.7 BTC in 2017 and generated a paper wallet using bitaddress.org with BIP38 passphrase encryption. The use
33.54 BTC Corrupted in Wallet.dat: Binary File Opened in Text Editor
Software wallet
Blocked 2017
In July 2016 or earlier, ketubi saved a wallet.dat file from Bitcoin Core to a USB drive, intending to create an offline backup. Years later, in December 2017,
← PreviousNext →
Browse by halving cycle 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