CustodyStress
Archive › Browse by era and stress › Coercion Era (2023–present) — Vendor lockout
Part of the CustodyStress archive of observed Bitcoin custody incidents
Coercion EraVendor lockout

Coercion Era (2023–present) — Vendor lockout

Exchange and platform failures from the Coercion Era (2023–present). Residual exchange failure cases continue as claims processes from prior-era collapses work through the system.

17 cases from this period are included in this archive. Exchange and custodial custody failures account for 71% of cases. 71% of determinate cases resulted in a blocked outcome.

Archive analysis — 17 cases
Outcomes
71% of determinate cases resulted in blocked access, close to the archive-wide average of 69%. 29% resulted in constrained recovery.
Documentation coverage
59% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
71% of cases involved exchange custody, followed by software wallet at 18%.
Recovery path
Derivation Path Correction is the most documented recovery path (5 cases, 29% of subset).
Documentation
76% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
65% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
17 observed cases
Blocked
5 (29%)
Constrained
2 (12%)
Indeterminate
10 (59%)
Freebitco.in Account Lockout: Password Reset Emails Failed During Platform Collapse
Exchange custody
Blocked 2025
In October 2025, a long-term Freebitco.in user identified as Lawliet82 reported sudden account access denial despite knowing the correct password and having suc
Blockchain.info Legacy Wallet Recovery: Partial Success via btcrecover, Platform Access Blocked
Exchange custody
Constrained 2025
Between 2013 and 2015, a user in Taiwan established multiple Blockchain.info wallets and created printed paper backups containing wallet GUIDs, passwords, and 1
Mycelium iOS Wallet: Seed Verification Failure and Transaction Blocking
Software wallet
Indeterminate 2025
On July 14, 2025, BitcoinTalk user Obdmageek reported a six-month custody failure involving a Mycelium iOS wallet. The user retained apparent access to their ac
2 BTC Vanished from Blockchain.com Wallet: Legacy Address Migration Gone Wrong
Exchange custody
Indeterminate 2025
In February 2025, a BitcoinTalk user reported that 2 BTC deposited to a Blockchain.com wallet from a mining computer in 2016 had become inaccessible. The wallet
Bitcoin Sent to Closed Cash App Account: Permanent Loss
Exchange custody
Blocked 2025
A Bitcoin holder attempted to deposit cryptocurrency into a Cash App account, unaware that the account had already been closed by the platform for terms-of-serv
Blockchain.com Email Takeover and Account Lockout: Recovery Phrase Insufficient
Exchange custody
Indeterminate 2024
Osiris100 created a Blockchain wallet in 2014 and retained the welcome email and wallet ID. In 2017, a verification email arrived unsigned, followed by two logi
Blockchain.com Non-HD to HD Wallet Migration: Imported Address Bitcoin Inaccessible
Exchange custody
Blocked 2024
In 2016, user serega634 maintained a Bitcoin wallet on Blockchain.com, then a widely-used custodial online wallet platform. At an unspecified later date, the us
Blockchain.com Imported Address Recovery: Funds Visible but Inaccessible
Exchange custody
Indeterminate 2024
Cryptflower created a Bitcoin wallet on Blockchain.com in 2014 and retained a 12-word BIP39 seed phrase saved in 2018. By January 2024, the user confirmed the o
3,000 BTC Locked on Discontinued Blockchain.com Wallet: Private Key Insufficient
Exchange custody
Indeterminate 2024
Ice22 registered with Blockchain.com (then Blockchain.info) in June 2009 after learning about Bitcoin through newspaper articles. Over a 1.5-hour phone guidance
Blockchain.com Legacy Wallet Lockout: Recovery Phrase Insufficient Without Original Email
Exchange custody
Blocked 2024
In 2014, delfastTions created a wallet on Blockchain.info and retained the 17-word recovery passphrase—the standard recovery mechanism of that era. Years later,
Blockchain.com Account Access Failure: 2014 Wallet, Dormant 10 Years, Support Unresponsive
Exchange custody
Indeterminate 2024
Between 2014 and early 2024, at least three users encountered custody access failures on Blockchain.com (formerly Blockchain.info). Osiris100 created a wallet o
BRD Wallet Derivation Path Incompatibility: Seed Phrase Cannot Recover 2018 Bitcoin
Software wallet
Indeterminate 2023
SimonsLu adopted Bitcoin in 2017 through exchange trading before transitioning to self-custody in 2018. He installed BRD, a mobile wallet recommended on bitcoin
Blockchain.com Account Frozen for Inactivity – User Unable to Recover Forgotten Wallet
Exchange custody
Indeterminate 2023
In February 2023, a user reported being contacted by an entity claiming to represent Blockchain.com. The message stated that the user had created a Bitcoin wall
BTC.com Multi-Sig Wallet Recovery Failure: Non-Standard Derivation Path Lockout
Multisig (self-managed)
Indeterminate 2023
In January 2023, a Bitcoin user rediscovered a dormant BTC.com wallet containing an undisclosed amount of Bitcoin. The user possessed both critical recovery mat
Coldlar Pro3 Hardware Wallet: Valid Seed Phrase Insufficient Without Payment Password
Hardware wallet with passphrase
Blocked 2023
On December 4, 2023, a Bitcoin user identified as zzzccc posted to BitcoinTalk describing a critical custody access failure involving a Coldlar Pro3 hardware wa
GDAC Exchange Security Breach: $13M Cryptocurrency Theft, April 2023
Exchange custody
Constrained 2023
On April 9–10, 2023, GDAC, a South Korean cryptocurrency exchange, discovered a security breach affecting its hot wallet infrastructure. Attackers transferred a
Electrum Wallet Synchronization Failure: Zero Balance Despite Blockchain Confirmation
Software wallet
Indeterminate 2023
On March 20, 2023, a BitcoinTalk user reported complete inability to access Bitcoin holdings in an Electrum wallet following over one year without access. Upon
Browse by era 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