CustodyStress
ArchiveDevice loss › Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00488

29 BTC Lost in Corrupted MultiBit Classic Wallet After Hard Drive Format

Blocked

Hardware device was lost or destroyed, and no independent seed phrase backup existed.

Case description

In 2014, JAMBO2014 acquired Bitcoin and stored it in MultiBit Classic 0.5.17, a desktop software wallet, without separately recording or backing up the private keys. The wallet file resided only on the user's personal computer with no external copies.

When the user formatted the hard drive and reinstalled the operating system, the wallet file was overwritten. Upon discovering the loss, JAMBO2014 pursued multiple recovery strategies over several years. Initial attempts involved using HxD, a hex editor, to search for the 32-byte private key signature pattern within recoverable disk sectors. The user also tested recovered hexadecimal strings against bitaddress.

org to validate potential keys. GitHub-hosted Python scripts designed specifically for MultiBit wallet recovery were tested, but yielded no usable results. Recognizing the severity of the situation, JAMBO2014 engaged a professional forensic recovery company to perform sector-by-sector scanning of the entire hard drive. Despite this expert intervention, the critical hexadecimal marker 0201010420 that precedes private key data in MultiBit wallet files was not found in any recoverable sectors.

The wallet file corruption was judged to be irreversible. By November 2020, with Bitcoin trading near $15,000 per coin, the 29 BTC holding was valued at approximately $435,000 USD. The case remained documented in the Bitcoin Technical Support forum, where community members provided guidance on avoiding recovery scams—warning against paying third parties claiming miraculous recovery capability—and emphasized proper backup procedures for future holders. No final resolution or recovery was reported.

Custody context
Stress conditionDevice loss
Custody systemSoftware wallet
OutcomeBlocked
DocumentationPartial
Year observed2020
Countryunknown
Structural dependencies observed
Device Specific AccessUndocumented procedurePassphrase Dependency
What this illustrates
There was no documentation of how access worked. Without it, there was no path back in. A software wallet stores keys on the device — whether a phone or computer. When the device is lost or the application is uninstalled, access depends entirely on whether a seed phrase was recorded and stored independently. Device loss is recoverable if and only if an independent seed phrase backup exists. The device itself is not the wallet — the seed phrase is. Cases without a separate backup typically end in permanent loss. The wallet needed a passphrase that nobody could produce. A blocked outcome in this archive means that no path to authorized access was found under the conditions documented.
Why this matters

What determines whether device loss is permanent

Device loss is one of the most documented stress conditions in the Bitcoin custody archive, and it is also one of the most preventable. The outcome is determined almost entirely by a single factor: whether an independent seed phrase backup existed at the time of loss, stored somewhere separate from the device itself.

When a device fails, burns, floods, or disappears, the Bitcoin remains on the blockchain, unchanged. What changes is whether any path to authorized access still exists. A seed phrase stored separately from the device preserves that path. A seed phrase stored with the device — or never recorded at all — eliminates it permanently.

The pattern observed across cases in this archive is consistent: recovery is possible when the seed phrase survived the event that took the device. It is not possible when it did not. The type of device, its cost, its brand, its security features — none of these factors determine the outcome. The seed phrase backup does.

Most device loss cases that result in permanent loss involve one of three failure modes: the seed phrase was never recorded at setup, the seed phrase was stored physically alongside the device and lost with it, or the seed phrase was stored in a location that became inaccessible during the same event (flood, fire, relocation). All three are detectable in advance. A backup test — confirming that the seed phrase can restore the wallet on a separate device — would have revealed the gap before the loss event.

How this category of failure is typically preventable

A device loss case becomes unrecoverable the moment the backup path is also broken. The preventive action is simple in concept: record the seed phrase at setup, store it independently from the device, and test that it works. Most cases in this archive involved none of these three steps.

Read more: Bitcoin Estate Administration →
Does losing a hardware wallet mean losing the Bitcoin?
Not necessarily. Bitcoin does not live inside the device — it exists on the blockchain. What the device held was the ability to sign transactions. If an independent seed phrase backup was created and stored separately from the device, that backup can restore full access to the same Bitcoin on any compatible wallet. Device loss only becomes permanent Bitcoin loss when no independent recovery path — seed phrase or wallet backup — exists.
Can a hardware wallet be replaced after it is lost or damaged?
Yes, the device itself can be replaced. Any compatible hardware wallet can restore the same wallet from the original seed phrase. The device is not the wallet — the seed phrase is. The critical question is whether the seed phrase was recorded and stored somewhere separate from the device that was lost.
What happens if a hardware wallet is lost with no seed phrase backup?
Without an independent seed phrase backup, loss of the device means permanent loss of access. There is no technical recovery path, no authority that can restore access, and no process that substitutes for the missing seed phrase. This is the most common cause of permanent Bitcoin loss in observed custody incidents.
Source
Publicly Reported
Most structurally similar case
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Device loss · Software wallet · 2013 Blocked
Related cases
Structural patterns in this case
Device discardedRecovery attempted, access still blocked
107 cases involve device loss 455 cases involve 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
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