CustodyStress
Archive › Browse by halving cycle and stress › Halving Cycle 2 (2013–2016) — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Cycle 2Seed phrase unavailable

Halving Cycle 2 (2013–2016) — Seed phrase unavailable

Seed phrase unavailability from Halving Cycle 2 (2013–2016). Growing hardware wallet adoption created new holders who failed to record their seed phrases at setup.

33 cases in this intersection. 75% of determinate cases resulted in a blocked outcome and 25% in access survived. The most common recovery path is no path available.

Archive analysis — 33 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
64% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
82% of cases involved software wallet, followed by exchange custody at 18%.
Documentation
67% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
94% of cases carry a undocumented recovery procedure dependency tag — the most common structural factor in this subset.
9
Blocked
0
Constrained
3
Survived
21
Indeterminate

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

33 observed cases
Blocked
9 (27%)
Survived
3 (9%)
Indeterminate
21 (64%)
Armory Desktop Wallet: 2 BTC Inaccessible Despite Paper and Encrypted Backups
Software wallet
Indeterminate 2016
A user purchased 2 BTC via Coinbase approximately 2013–2014 and transferred them to a self-hosted Armory wallet running on a personal server. The transfer compl
75 BTC Access Loss: Bitcoin Core Wallet Reset Without Backup (2016)
Software wallet
Indeterminate 2016
In 2016, forum user bridget1 installed Bitcoin Core v0.13.0 and deposited 75 BTC into the newly created wallet. At the time, 75 BTC had a market value of approx
Rafel Marcel: Bitcoin Acquired via BitX in 2016, Seed Phrase Never Recorded
Software wallet
Indeterminate 2016
Rafel Marcel purchased Bitcoin approximately ten years prior to March 2026—around late 2016—through an exchange called BitX (later rebranded as Luno). A friend
Block.io Permanent Loss: Forgotten PIN and Missing Secret Mnemonic Backup
Exchange custody
Blocked 2016
In February 2016, a BitcoinTalk user identifying as CaRLoSXXX posted a distress message after losing access to their Block.io wallet. Block.io is a non-custodia
Blockchain.com Wallet (2016): Partial Password Recovery Attempt, Seed Phrase Absent
Exchange custody
Blocked 2016
The subject created a Blockchain.com account in 2016 and deposited approximately 0.03 BTC (valued at roughly $20 at 2016 exchange rates of $600/BTC). Immediatel
Watching-Only Wallet With Lost Seed Phrase: Password Insufficient for Recovery
Software wallet
Indeterminate 2016
In June 2016, a BitcoinTalk user identified as Tully96 posted in the Wallet Software forum seeking help after discovering they had lost access to Bitcoin stored
Electrum Wallet Loss After Hard Disk Failure: No Seed Phrase or Backup
Software wallet
Indeterminate 2016
In March 2016, a BitcoinTalk user operating under the handle 'knowhow' experienced total loss of access to an Electrum Bitcoin wallet after their hard drive fai
Deleted Temporary Wallet Recovery via Private Key Forensic Extraction
Software wallet
Survived 2015
In September 2015, a Bitcoin user known as dooglus encountered a self-imposed custody failure during a transaction resend operation. After noticing an unconfirm
Blockchain.info Account Lockout: Forgotten Password, Missing Seed Phrase, $3,800 USD Inaccessible
Exchange custody
Indeterminate 2015
TheLoser created a hosted wallet on Blockchain.info via the Apple mobile application in late September 2015. The wallet creation process did not present or prov
0.22 BTC Inaccessible in Electrum Watch-Only Wallet After Bitcoin Core Import Error
Software wallet
Indeterminate 2015
In October 2015, a macOS user (ginko3000) discovered they could not spend 0.22 BTC held in an Electrum wallet despite the balance being visible on screen. The w
Blockchain.info iOS Wallet: $3,600 Lost to Missing Mnemonic and Unresettable Password
Exchange custody
Blocked 2015
In September 2015, TheLoser created a Bitcoin wallet on Blockchain.info using an iOS mobile device. Unlike documented Blockchain.info workflows, the wallet crea
Ruairi's Lost Paper Backup: €80 Bitcoin, Both Credentials on One Document
Software wallet
Blocked 2015
Ruairi purchased approximately €80 worth of Bitcoin in late 2015, driven by curiosity about the emerging technology and its associations with dark web markets.
Recovery of Dormant Blockchain.info Wallet via Legacy 20-Word Mnemonic (2017)
Exchange custody
Survived 2014
Roland808, a BitcoinTalk user, discovered a text file on their computer in March 2017 dated from 2014 containing a label 'bitcoin nmemonic' followed by 20 rando
Bitcoin-Qt Wallet Shows Zero Balance After Windows Installation on SSD
Software wallet
Indeterminate 2014
In January 2014, a Bitcoin holder experienced a system failure (repeated Blue Screen of Death) on their PC. Rather than repair the existing installation, they p
Electrum Seed Phrase Lost to Accidental File Deletion — Windows Recovery Attempt
Software wallet
Indeterminate 2014
In mid-2014, a user identified as Evolution created an Electrum Bitcoin wallet using Tails live operating system running inside VMware on Windows 7. The user ge
Electrum Wallet Access Failure: Lost Printed Seed and Empty CSV Export
Software wallet
Indeterminate 2014
In February 2014, a BitcoinTalk forum user identified as 'Howinthe?' reported the loss of access to 2 BTC acquired years earlier when the asset traded at approx
MultiBit 16-Word Seed Recovery Failure: Non-Standard Implementation
Software wallet
Indeterminate 2014
In 2014, NickyGH attended a Bitcoin wallet setup workshop in Shoreditch, London organized through a community meetup. A technician guided attendees through Mult
10,000 DOGE from Bittylicious (2014): Device Loss, No Backup, SSD Wiped
Software wallet
Blocked 2014
In December 2014, a UK-based BitcoinTalk user (apda) received 10,000 DOGE from Bittylicious, a London-regulated cryptocurrency exchange (BIOM Ltd), and directed
Accidental Deletion and Overwriting of 2011 Mining wallet.dat Files
Software wallet
Indeterminate 2014
Japanese2212, a BitcoinTalk forum user, posted in July 2021 describing a custody failure stemming from accidental file deletion and data overwriting. The user c
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
0.5 BTC Lost in Blockchain.info Encrypted Wallet (2014)
Exchange custody
Indeterminate 2014
In January 2014, an early Bitcoin adopter purchased BTC on LocalBitcoins and transferred 0.5 BTC to a public address in August of that year. The user recorded o
Bitcoin-Qt Wallet Corruption After Power Loss — Salvage Command Failed to Recover
Software wallet
Blocked 2014
In 2014, a Bitcoin holder stored their funds in a wallet.dat file managed by Bitcoin-Qt on a Windows machine with an SSD. The wallet had been dormant for approx
Electrum Wallet Recovery After Seed Backup Loss: electrum.dat File Decryption
Software wallet
Survived 2014
In April 2014, a BitcoinTalk forum user (DarkHyudrA) experienced custody access failure after formatting their personal computer without preserving a backup cop
0.3 BTC Lost When Android Bitcoin Wallets Factory Reset Without Backup
Software wallet
Indeterminate 2014
In July 2014, a BitcoinTalk forum user (ejinte) reported transferring 0.3 BTC to family members—his mother and sister—by helping them download and set up an And
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
← PreviousNext →
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