CustodyStress
Archive › Browse by era and stress › Maturation Period (2020–2022) — Coercion
Part of the CustodyStress archive of observed Bitcoin custody incidents
MaturationCoercion

Maturation Period (2020–2022) — Coercion

Coercion cases from the Maturation Period (2020–2022). Coercion emerged as a significant stress condition for the first time as Bitcoin's price reached new highs and self-custody adoption grew.

32 cases from this period are included in this archive. Coercion accounts for 100% of cases — the dominant stress pattern. 92% of determinate cases resulted in a blocked outcome.

24
Blocked
0
Constrained
2
Survived
6
Indeterminate

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

32 observed cases
Blocked
24 (75%)
Survived
2 (6%)
Indeterminate
6 (19%)
Blantyre Home Invasion: Victim Coerced to Transfer $200,000 Bitcoin
Unknown custody system
Blocked 2020
In March 2020, a home invasion occurred in Blantyre, Scotland, during which a woman occupant was assaulted with a Toblerone bar and forced under duress to trans
Vietnamese Police Officers Charged in $1.6 Million Bitcoin Robbery
Software wallet
Blocked 2020
In May 2020, Le Duc Nguyen, a Bitcoin holder in Ho Chi Minh City, Vietnam, became the victim of a coordinated robbery by police officers. The officers seized ap
Armed Home Invasion and Forced Cryptocurrency Transfer in Carlisle
Exchange custody
Blocked 2020
In February 2020, armed intruders broke into a residential property in Carlisle, England. The attackers, wielding a gun and knife, forced the occupants—a couple
Kidnapping and Torture for Bitcoin in Ternopil, Ukraine (December 2020)
Software wallet
Blocked 2020
In December 2020, a man was kidnapped and held in Ternopil, Ukraine by a criminal group that demanded $800,000 in compensation. The victim was tortured during c
Iroro Wisdom Ovie Killed in Bitcoin-Motivated Home Invasion, Nigeria 2020
Software wallet
Blocked 2020
In January 2020, Iroro Wisdom Ovie was killed during a home invasion in Abraka, Delta State, Nigeria. The attackers were motivated specifically by knowledge tha
Mark Cheng Jin Quan Kidnapped and Extorted for Bitcoin in Bangkok
Software wallet
Blocked 2020
Mark Cheng Jin Quan, a Singapore-based blockchain advisor, was kidnapped in Bangkok, Thailand in January 2020 and held at gunpoint by his captors. Under physica
SBU Officers Kidnap and Torture Businessman for 7 Bitcoin Transfer
Unknown custody system
Blocked 2020
In October 2020, officers from Ukraine's cyber department of the Security Service of Ukraine (SBU) kidnapped a Kyiv-based businessman, drove him to a forest loc
← PreviousNext →
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