CustodyStress
Archive › Structural dependencies › Institutional Cooperation Required
Part of the CustodyStress archive of observed Bitcoin custody incidents

Institutional Cooperation Required

Cases where completing recovery required active cooperation from an exchange, custodian, or institution — and that cooperation was unavailable, delayed, or blocked.

Cases where institutional cooperation was required to complete recovery show a 60% blocked rate among determinate cases — and a 5% survival rate. The institution becomes the structural gatekeeper: when cooperation is withheld, delayed, or becomes impossible through insolvency, the recovery path closes entirely.

96
Blocked
57
Constrained
8
Survived
37
Indeterminate

95% of determinate cases resulted in blocked or constrained access.

198 observed cases
Blocked
96 (48%)
Constrained
57 (29%)
Survived
8 (4%)
Indeterminate
37 (19%)
Inputs.io Security Breach and Platform Collapse — 4,100 BTC Lost
Exchange custody
Blocked
Inputs.io operated as a hosted web wallet service in the early Bitcoin era, when best practices for key management were still crystallizing. The platform genera
Deceased Father's 14 BTC Locked on Blockchain.com: Forgotten Password Blocks Access
Exchange custody
Blocked
A Reddit user reported discovering their deceased or incapacitated father's Blockchain.com wallet containing 14 BTC. While the heir had gained access to the acc
Brazilian Court Orders Banks to Reopen Frozen Cryptocurrency Exchange Accounts
Exchange custody
Constrained
A Brazilian court issued an order requiring banks to reopen cryptocurrency exchange accounts that had been frozen. The incident reflects a custody failure roote
Pheeva Mobile Wallet Collapse: 4 BTC Inaccessible After Passphrase Authentication Failure
Exchange custody
Indeterminate
Between 2014 and 2015, a Bitcoin user deposited approximately 4 BTC into Pheeva, a mobile wallet application developed by Lamar Wilson's Love Will company. The
Blockchain.com Legacy Wallet Inaccessible: Passphrase Format Incompatibility
Exchange custody
Blocked
A user created a wallet on Blockchain.info in 2013, recording both a password and a recovery key-phrase of more than 12 words. The account remained dormant for
Blockchain.com Account Lockup: 8-Month Custody Freeze Despite Verified Funds
Exchange custody
Blocked
In summer 2022, an individual opened a hosted wallet account on Blockchain.com and completed full KYC verification, achieving the platform's highest transaction
Blockchain.com Wallet Recovery Blocked: Known Passwords, Lost Registration Email
Exchange custody
Blocked
During a house cleaning, papers containing three Blockchain.com wallet identifiers and their corresponding passwords surfaced. The wallets held an estimated 0.9
Blockchain.info Account Inaccessible: Valid Credentials Defeated by Email Verification Gate
Exchange custody
Blocked
An early adopter maintained a Blockchain.info wallet account from the platform's initial era, retaining both the wallet ID and a valid password. The account rem
BitGo Wallet Permanently Inaccessible: Lost 2FA Device and Missing Documentation
Exchange custody
Blocked
A long-term Bitcoin holder maintained a BitGo-hosted wallet from 2015 without establishing comprehensive backup procedures or written documentation. The account
Hardware Wallet Backup Complete — Bitcoin Never Left the Exchange
Exchange custody
Survived
An estate executor discovered a Trezor Safe 3 hardware wallet in the deceased's bedside table alongside a 12-word seed phrase and PIN. Bank records showed a $1,
Cavirtex Exchange Shutdown and Withdrawal Lockdown (March 2015)
Exchange custody
Indeterminate
Cavirtex, a Canadian Bitcoin and Litecoin exchange founded in late 2011, discovered a compromise of an older database version on February 15, 2015. The breach e
Bitfinex Account Freeze: 2.1 BTC Trapped After Escalating KYC Demands
Exchange custody
Blocked
A long-standing Bitfinex user with a six-year account history initiated a withdrawal of 2.1 BTC in early 2021, during a period of significant Bitcoin price appr
Blockchain.com Account De-Verification: Funds Inaccessible, No Communication or Recovery Path
Exchange custody
Blocked
A user with an active Blockchain.com account maintained since 2017 experienced sudden account de-verification, rendering all funds held in the platform's reward
Vault of Satoshi Exchange Shutdown: Bitcoin Trapped in 2014 Closure
Exchange custody
Blocked
A Bitcoin holder purchased cryptocurrency on Coinbase in 2014 and transferred it to Vault of Satoshi, a Canadian cryptocurrency exchange, intending to trade the
BTC.com Wallet Closure: Recovery Documents Present but Platform Inaccessible
Exchange custody
Indeterminate
BTC.com, a web-based wallet service, announced cessation of operations effective April 15. The user discovered the service was non-functional upon attempting lo
Blockchain.com Account Frozen After Recovery Phrase Restoration
Exchange custody
Blocked
A user with a valid BIP39 recovery phrase attempted to restore access to their Blockchain.com wallet. Upon successful restoration, the platform automatically de
Blockchain.info Account Locked After 2FA Device Loss—Recovery Process Failed
Exchange custody
Blocked
A Blockchain.info user lost access to their two-factor authentication device (Google Authenticator) and could no longer log into their account. Blockchain.info'
Son Inherits 14 BTC on Blockchain.com After Father's Death — All Access Credentials Lost
Exchange custody
Indeterminate
A son discovered approximately 14 BTC held in a Blockchain.com custodial wallet following his father's death. The father had secured the account with a password
LUNO Exchange Account Access Failure: Email Identifier Lockout
Exchange custody
Constrained
In 2013, a Bitcoin holder received cryptocurrency from BitX (later rebranded as LUNO) and deposited the funds directly on the exchange platform. For several yea
Kraken Account Lockout: Cryptographic Proof of Ownership Rejected
Exchange custody
Blocked
In September 2020, Kraken implemented device confirmation security requiring verification codes sent to registered email addresses. A user with Bitcoin holdings
Blockchain.com Account Freeze: Verified User Locked Out, Resolution Via CEO Escalation
Exchange custody
Constrained
In October 2025, a user with a Blockchain.com account maintained since 2019 and full verification status experienced an abrupt account freeze. The platform cite
MtGox Exchange Collapse: 850,000 Bitcoin Custody Failure
Exchange custody
Blocked
Mt. Gox, founded in 2006 and operating as a Bitcoin exchange from 2010, accumulated custody of approximately 850,000 Bitcoin belonging to its users by early 201
2 Bitcoin Recovered from Deceased Relative's Coinbase Account After Six Years
Exchange custody
Survived
In early 2024, an inheritor searching a deceased relative's email discovered a Coinbase purchase receipt dated three days before the relative's death in 2018. T
← Previous
1678
Next →
Structural dependencies
By stress condition
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