CustodyStress
Archive › Seed phrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00148

Seed phrase unavailable — software wallet 2014

Blocked
Case description
A forum post documents a user who had split their 24-word Electrum seed into two 12-word halves stored in separate locations, following informal security advice. When retrieving the seed, they discovered one of the halves had been mixed up with another document and lost. Neither half alone was sufficient to reconstruct the wallet.
Custody context
Stress conditionSeed phrase unavailable
Custody systemMobile or software wallet
OutcomeBlocked
DocumentationUnknown
Year observed2014
CountryUnknown
Structural dependencies observed
Single point of failure
What this illustrates
There was only one way in. When that path was gone, so was access. Access was not recoverable.
Outcome interpretation
Access was not possible under the reported conditions.
Source
Publicly Reported
Evidence type
Forum post
Related cases involving seed phrase unavailable
146 cases involve seed phrase unavailable 572 cases involve mobile or software wallet View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
Terms guide
Survives
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.
Single-person knowledge
Recovery depended on information or capability held by one individual who was unavailable.
Institutional dependence
Recovery depended on a third-party institution or service that was inaccessible or uncooperative.
Documentation gap
Recovery depended on instructions that were missing, incomplete, or unclear.
Authority mismatch
The person with legal authority to act did not have operational access, or vice versa.
Original text
Rate this translation
Your feedback will be used to help improve Google Translate