CustodyStress
Archive › More 2017 cases › 2017 — Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
2017Seed phrase unavailable

2017 — Seed phrase unavailable

Seed phrase unavailability cases from 2017. The mass adoption of hardware wallets during the 2017 cycle created a cohort of holders who had seed phrases but failed to store them independently of their devices.

Archive analysis — 13 cases
Documentation coverage
69% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
77% of cases involved software wallet, followed by exchange custody at 15%.
Recovery path
Technical Recovery is the most documented recovery path (3 cases, 23% of subset).
Documentation
77% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
92% of cases carry a single-person knowledge dependency tag — the most common structural factor in this subset.
13 observed cases
Blocked
3 (23%)
Survived
1 (8%)
Indeterminate
9 (69%)
Mycelium Bitcoin Access Loss: PIN Change and Seed Phrase Recovery Confusion
Software wallet
Indeterminate 2017
In November 2017, a Mycelium wallet user (AdunToridas) encountered a critical access loss incident after routine account maintenance. The user had created a Myc
Armory Paper Backup Recovery Displays Zero Balance Despite Correct Restoration
Software wallet
Indeterminate 2017
In November 2017, user xTwin25 initiated recovery of Bitcoin holdings stored in Armory, a desktop software wallet. The user possessed a paper backup containing
Lost Android Wallet.dat After Device Wipe and Lending — No Backup
Software wallet
Indeterminate 2017
In December 2017, a BitcoinTalk user identified as dandyret described losing access to a Bitcoin wallet stored on an Android phone. The user had wiped the devic
Mark Frauenfelder's 7.4 BTC: Seed Phrase Discarded by Housecleaner, Recovered via Hardware Vulnerability
Hardware wallet (single key)
Survived 2017
Mark Frauenfelder, editor-in-chief of Boing Boing and Wired contributor, purchased 7.4 Bitcoin in January 2016 for approximately $3,000 and transferred it to a
25 Bitcoin Lost After Computer Crash: Wallet Identity Unknown
Software wallet
Indeterminate 2017
In November 2017, a Bitcoin Stack Exchange user disclosed that they had purchased 25 bitcoins years prior and deposited them into a wallet on a personal compute
Blockchain.info Watch-Only Import Without Private Key Retention
Exchange custody
Blocked 2017
In June 2017, a Bitcoin Talk forum user (amirheavy666) discovered that approximately 0.00027375 BTC accumulated on a Blockchain.info wallet created around 2014
Bitcoin Lost After Hard Drive Format: wallet.dat Unrecovered, Private Key Missing
Software wallet
Blocked 2017
A Bitcoin holder received cryptocurrency in 2013 via Bitcoin Core but did not understand the critical role of the wallet.dat file in securing access to funds. I
Hive Wallet Litecoin Loss: 12-Word Seed Phrase Never Documented
Software wallet
Indeterminate 2017
PentagonPinnacle purchased litecoins several years before May 2017 and installed them in a Hive Wallet application on an iPad. At the time of wallet creation, t
Blockchain.info Legacy Wallet Upgrade Failure: Lost Access Without Seed Phrase
Exchange custody
Indeterminate 2017
In November 2017, a Blockchain.info user (jameslewis123) discovered that wallets created in 2014–2015 could no longer be accessed after an extended dormancy per
Bitcoin-qt wallet.dat Corruption: Passphrase Known, File Unrecoverable
Software wallet
Indeterminate 2017
A BitcoinTalk user identified as 'lolika' posted a recovery request on December 1, 2017, describing a corrupted Bitcoin Core wallet.dat file created between 201
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
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
More 2017 cases
Related pages
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