CustodyStress
Archive › Browse by halving cycle and stress › Halving Cycle 4 (2021–2024) — Vendor lockout
Part of the CustodyStress archive of observed Bitcoin custody incidents
Cycle 4Vendor lockout

Halving Cycle 4 (2021–2024) — Vendor lockout

Exchange failures from Halving Cycle 4 (2021–2024). The collapse of FTX, Celsius, Voyager, and Terra/Luna in 2022 produced the largest cluster of institutional custody failures in the archive's history within a single halving cycle.

34 cases in this intersection. 37% of determinate cases resulted in a blocked outcome and 5% in access survived. The most common recovery path is exchange support.

7
Blocked
11
Constrained
1
Survived
15
Indeterminate

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

34 observed cases
Blocked
7 (21%)
Constrained
11 (32%)
Survived
1 (3%)
Indeterminate
15 (44%)
Valid Seed Phrase, Inaccessible Address: Coinbase Derivation Path Incompatibility
Exchange custody
Indeterminate 2021
In January 2021, forum user Folio sought help accessing Bitcoin held in a friend's Coinbase wallet. The friend had provided the seed phrase, but Folio could not
Blockchain.info Wallet Access Blocked by Lost Email Authentication
Exchange custody
Indeterminate 2021
In May 2021, user Gy.sahani located a text file backup created in 2015 containing full credentials for a Blockchain.info hosted wallet: a 20-word mnemonic phras
Blockchain.info Legacy Wallet Access Loss: Password Forgotten, Recovery Phrase Format Incompatible
Exchange custody
Indeterminate 2021
In April 2021, a Bitcoin holder discovered they could no longer access a Blockchain.info wallet opened in 2014 after forgetting the account password. The platfo
Ninki Wallet Recovery Failure: Seed Phrase Insufficient Without Derivation Path Documentation
Exchange custody
Indeterminate 2021
Ninki was an online wallet service that ceased operation, trapping user funds behind a discontinued platform. The user Sycorax21 held the theoretically complete
BitMart Exchange Security Breach: $196M Stolen from Unprotected Hot Wallets
Exchange custody
Constrained 2021
BitMart, a cryptocurrency exchange, suffered a major security breach on December 4–5, 2021, when attackers obtained private keys controlling two internet-connec
BCH Sent to CashApp Bitcoin Wallet: Funds Locked to Platform Control
Exchange custody
Indeterminate 2021
In March 2021, a user initiated a Bitcoin Cash withdrawal from a forex broker but selected the wrong asset type, causing approximately $1,600 BCH to be sent to
Blockchain.com KYC Re-Verification Lockout: 30-Day Withdrawal Freeze
Exchange custody
Survived 2021
In October 2021, a Blockchain.com user encountered a mandatory identity verification step during login—a process previously completed without friction. The veri
Liquid Exchange $80M Hack (August 2021): Withdrawal Freeze, FTX Bailout, Full Acquisition
Exchange custody
Constrained 2021
On August 19, 2021, Japanese cryptocurrency exchange Liquid discovered that hackers had compromised its warm wallet infrastructure and transferred approximately
AscendEX Exchange $78M Hot Wallet Breach — December 2021
Exchange custody
Constrained 2021
On December 11, 2021, AscendEX (formerly BitMax) disclosed a significant security breach affecting its hot wallet infrastructure. Approximately $78 million in c
← PreviousNext →
Browse by halving cycle and stress
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