Part of the CustodyStress archive of observed Bitcoin custody incidents

Bitcoin Recovery Path Success Rates

Which recovery approaches — seed phrase located, exchange account recovery, professional services, legal proceedings — produce access survived outcomes in documented Bitcoin custody failures? This comparison shows survival and blocked rates by recovery path across cases in the archive.

Recovery path describes what was attempted or used in the documented case — it does not describe all available options at the time. A case may have a recovery path of "professional recovery service attempted" while still producing a blocked outcome if the attempt was unsuccessful. Success rates here reflect the documented outcome of the recorded recovery approach, not the theoretical success rate of the method in general.

Survived % is calculated from determinate cases only. Cases are sorted by survived rate descending — highest survival rate first. A case is classified by its primary recovery path.

Recovery paths ranked by survival rate

Recovery path	Cases	Survived %	Blocked %
Alternate access route Alternative path found (different wallet, key, or credential).	4	100%	0%
Technical recovery Recovery through software tools or forensic methods.	40	91%	9%
Seed phrase located Holder or heir located a recorded seed phrase backup.	17	83%	8%
Derivation path correction Incorrect derivation path identified and corrected.	18	75%	25%
Password or PIN bruteforce Systematic attempts to recover a credential.	113	68%	16%
Vendor or platform support Manufacturer or platform support engaged.	4	50%	25%
Software downgrade / rollback Older version of software restored access.	5	50%	50%
Estate process Formal estate administration used to access Bitcoin.	26	40%	40%
Exchange account recovery Platform support or account recovery process succeeded.	74	12%	20%
Bankruptcy claims process Claims filed through formal insolvency proceedings.	12	0%	42%
Legal proceedings Court orders, probate, or regulatory processes used.	24	0%	71%
Partial recovery only Some Bitcoin recovered; full access could not be restored.	7	0%	0%

Sorted by survived % descending. Distribution bar shows blocked (dark red) / constrained (amber) / survived (green). Indeterminate cases excluded.

What the data shows about recovery

Alternate access route has the highest survived rate in the archive at 100% — 4 cases. This reflects the fundamental structure of Bitcoin self-custody recovery: when the seed phrase was recorded and can be located, recovery is structurally complete. The seed phrase restores full access on any compatible wallet regardless of what happened to the original device or software.

The contrast between seed-phrase recovery and credential-based recovery methods (password bruteforce, technical recovery) reflects the architecture of Bitcoin custody. Seed phrase recovery restores access at the root — the full wallet. Credential recovery attempts work around a specific barrier. When the barrier is a forgotten passphrase on a hardware wallet, bruteforce is computationally feasible only under limited conditions (short passphrases, known character sets). When the barrier is a lost seed phrase with no backup, no recovery method can substitute for the missing material.

Bankruptcy claims process cases show a distinctive pattern: low survived rates but high constrained rates — reflecting the partial and delayed nature of exchange insolvency proceedings. Creditors in exchange bankruptcies (FTX, Mt. Gox, Celsius, QuadrigaCX) receive distributions that represent a fraction of their holdings, often after years of proceedings. Access is not permanently blocked but it is severely constrained in value and timing.

Legal proceedings and estate process paths produce high blocked rates in the archive because these processes are typically initiated after other recovery methods have failed — they represent the residual cases where legal authority was established but technical access could not be achieved. An executor with letters testamentary and no seed phrase has legal authority and no technical path forward. The law closed; the access problem did not.

Professional recovery services appear with mixed outcomes reflecting the diversity of what they address: derivation path problems, passphrase variation searches, hardware wallet firmware issues, and corrupted wallet files are more recoverable than missing seed phrases, which are not recoverable by any external service. The outcome depends entirely on the nature of the barrier, not on the quality of the service.

Recovery paths and the assessment model

The CustodyStress assessment models which recovery paths are available for a declared custody arrangement — not which will succeed. A setup that has a seed phrase stored in a separate location from the device has a seed-phrase recovery path available. A setup where the passphrase exists only in memory has a credential-dependent recovery path that closes when memory fails. The archive outcome data here shows how those path types performed in documented cases.

Seed phrase recovery cases Bankruptcy claims cases Professional recovery cases Outcome by stress condition Blocked rate by dependency Archive statistics

Figures describe observed outcome distributions within documented cases in this archive only. Recovery path success rates reflect documented outcomes, not general method efficacy. Bitcoin Custody Incident Archive — CustodyStress · custodystress.com/cases · 895 documented incidents

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:

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.
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.
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.