Part of the CustodyStress archive of observed Bitcoin custody incidents
Bitcoin Custody Stress Scenarios
Documented custody incidents organized by the stress condition under which access failed or degraded.
The archive organizes documented custody incidents by stress condition rather than by wallet type alone. This makes it easier to see how access fails when normal assumptions no longer hold: the owner may be unavailable, a device may be gone, a vendor may be unreachable, or recovery may depend on memory, timing, or cooperation that is not present under stress.
The same custody system may produce different outcomes under different stress conditions. A hardware wallet that survives device loss may fail under cognitive failure if no one else can interpret the recovery instructions. An exchange account that survives legal scrutiny may be inaccessible after the account holder dies without leaving credentials.
These scenario pages are editorial and explanatory surfaces — each describes observed failure patterns within the archive for a specific stress condition. They are distinct from archive filter pages, which display raw case counts by taxonomy variable. The archive documents observed incidents; it does not claim to represent all Bitcoin custody failures.
Scenario Overview
Death or Absence
Cases where the original holder is unavailable to explain the custody system or complete recovery steps.
Documented cases 44
Common custody context Software wallet
Observed outcomes 60% blocked, 35% survived (of 20 determinate cases)
View scenario →
Device Loss
Cases where the primary wallet device was lost, destroyed, stolen, or broken, making access dependent on the existence and accessibility of independent backups.
Documented cases 107
Common custody context Software wallet
Observed outcomes 77% blocked, 23% survived (of 47 determinate cases)
View scenario →
Physical Coercion
Cases where the holder was subjected to physical force or threats compelling Bitcoin transfer or disclosure of access credentials.
Documented cases 112
Common custody context Hardware wallet (single key)
Observed outcomes 81% blocked, 18% survived (of 94 determinate cases)
View scenario →
Legal Seizure
Cases where legal or regulatory action — government seizure, court orders, account freezes, or sanctions — constrained or blocked access by an authorized party.
Documented cases 23
Common custody context Exchange custody
Observed outcomes 64% blocked, 0% survived (of 22 determinate cases)
View scenario →
Scenario Comparison Across the Archive
All figures are within documented cases only. Documentation gap rate = share of cases with partial, absent, or ambiguous documentation.
| Scenario |
Cases |
Blocked % |
Common custody |
Top dependency |
Doc gap % |
| Death or Absence |
44 |
60% |
Software wallet |
Single-Person Knowledge |
86% |
| Device Loss |
107 |
77% |
Software wallet |
Device-Dependent Access |
78% |
| Physical Coercion |
112 |
81% |
Hardware wallet (single key) |
Single-Person Knowledge |
37% |
| Legal Seizure |
23 |
64% |
Exchange custody |
Legal Authority Required |
52% |
Blocked % calculated from determinate cases only. Doc gap % = partial + absent + ambiguous documentation, all cases.
Outcome Distribution by Scenario
Blocked
Constrained
Survived
Death or Absence
44 cases · 60% blocked
60%5%35%
Device Loss
107 cases · 77% blocked
77%23%
Physical Coercion
112 cases · 81% blocked
81%1%18%
Legal Seizure
23 cases · 64% blocked
64%36%
Bars show distribution of determinate cases only. Indeterminate cases not shown. Hover a segment for percentage.
How Failure Conditions Differ
Why scenario matters
The same custody arrangement can produce different outcomes under different stress conditions. A setup that reliably survives device loss — because an independent seed phrase backup exists — may fail completely under cognitive failure if the seed phrase location was known only to the holder. A multisig arrangement that protects against coercion — because a single signer cannot complete a transaction alone — may deadlock under death or incapacity if the remaining signers lack the procedural knowledge to coordinate. Scenario classification surfaces these conditional failure modes that are invisible when looking at a custody setup in isolation.
Different scenarios expose different dependencies
Each stress condition tends to expose a distinct class of structural dependency:
Death or absence exposes documentation gaps and role gaps — the absence of written instructions and the absence of a prepared person who can act.
Cognitive failure exposes memory dependencies — passphrases, PIN numbers, and procedural knowledge held only in the owner's recall.
Physical coercion exposes immediate-access design and physical concentration — setups where a single person's cooperation yields full access.
Device loss exposes backup independence — whether an independent seed phrase copy exists and is reachable outside the lost device.
Legal seizure exposes the gap between legal authority and operational access — having the legal right to Bitcoin does not automatically provide the technical means to move it.
Forced relocation exposes jurisdictional and vendor reachability — setups that assumed geographic stability or access to specific platforms from a specific country.
Outcome labels mean different things across scenarios
A "constrained" outcome under forced relocation means something structurally different from a "constrained" outcome under cognitive failure. In relocation, constrained typically means access was eventually possible once geographic barriers were resolved or alternative access paths were found. In cognitive failure, constrained may mean a technical specialist was required to reconstruct partial information — a different kind of dependency failure with a different recovery timeline. The outcome label is the same; the structural cause and recovery path are not.
Observations from the archive
Among scenarios with sufficient cases to measure, Physical Coercion has the highest blocked rate in the archive at 81% of determinate cases — meaning no recovery path was documented under the stated conditions.
Legal Seizure cases most frequently involve external institutional dependency — 74% of cases in this scenario depend on a platform, service, or institution remaining available and cooperative.
Death or Absence cases have the highest documentation gap rate in the archive — 86% of cases involve partial, absent, or ambiguous documentation at the time of the access failure.
Scenario pages describe observed stress conditions in documented incidents. They are organizational views of the archive, not claims about the total distribution of Bitcoin custody failures. The archive is not exhaustive — cases are included where sufficient public documentation exists to classify the failure and outcome.
Outcome terms
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.
Assessment terms
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
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?
Inclusion requirements
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.
In scope
- 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
Out of scope
- 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
Source and verification
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.