Part of the CustodyStress archive of observed Bitcoin custody incidents

Bitcoin Custody Outcomes by Documentation Status

How documentation completeness relates to outcome in documented Bitcoin custody failures. Cases are classified by whether written documentation about the custody arrangement — seed phrase locations, wallet instructions, account credentials, or recovery procedures — was present at the time of the failure.

Documentation is not sufficient on its own for recovery — it must be findable, interpretable, and complete. Cases with documentation present but ambiguous produce outcomes closer to absent documentation than to present and interpretable documentation. The quality and accessibility of documentation matters as much as its existence.

These figures describe observed outcome distributions within documented cases in this archive only. The archive is not exhaustive. Inclusion requires sufficient public documentation to classify the case — which means cases with no documentation may be under-represented relative to their true frequency.

Outcome distributions by documentation status

Blocked Constrained Survived

Documentation present and interpretable

299 cases · 279 determinate

62% blocked 19% constrained 18% survived

Partial documentation

555 cases · 209 determinate

77% blocked 7% constrained 16% survived

Documentation present but ambiguous

34 cases · 12 determinate

58% blocked 8% constrained 33% survived

No documentation known

7 cases · 6 determinate

100% blocked 0% constrained 0% survived

What the data shows

Cases with no documentation known have a blocked rate 38 percentage points higher than cases with present and interpretable documentation (62% vs 100%). This is the most direct quantification in the archive of documentation's relationship to outcome.

Even cases with present and interpretable documentation produce blocked outcomes at a significant rate (62%). This reflects exchange collapses — where documentation of account credentials does not help when the institution has failed — and coercion cases, where documentation is structurally irrelevant. Documentation prevents some failures but not all.

Partial documentation produces outcomes between fully documented and undocumented cases, but closer to the absent end. Partial documentation — a seed phrase without a passphrase, wallet instructions without account credentials, a will that mentions Bitcoin without access details — often creates the expectation of recovery without providing the means to complete it. Heirs and executors may spend significant effort searching for documentation they believe exists before accepting that what they have is insufficient.

Documentation status at time of failure is distinct from documentation quality during the holder's lifetime. Many cases in the none-known category involved holders who had note-keeping practices but whose records were not found by heirs — either because they were stored separately from the Bitcoin assets, destroyed, or never communicated to anyone who would look for them.

Documentation and custody type

Documentation absence is not uniformly distributed across custody types. Self-custody arrangements — particularly hardware wallets and software wallets — are far more likely to have no documentation than exchange custody, where account credentials at minimum provide a starting point for heirs. Among self-custody cases in the archive, the most common documentation pattern is a wallet device that heirs can locate but cannot access, with no seed phrase backup.

Multisig custody has a distinct documentation failure mode: the quorum setup and the roles of each signing participant may be undocumented even when individual key material is accessible. Heirs locate hardware wallets but cannot determine the threshold, the other participants, or the software required to construct a transaction.

No documentation cases Partial documentation cases Fully documented cases Archive statistics Dependencies

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.