CustodyStress
Archive › More United Kingdom cases › United Kingdom — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
United KingdomSoftware wallet

United Kingdom — Software wallet

Cases from the United Kingdom involving software wallet custody failures.

100% of determinate cases in this country with this custody type resulted in a blocked outcome — 28 points above the global rate of 72% for this custody type. This country accounts for 3% of all archive cases with this custody type. The most common recovery path is coerced transfer.

Archive analysis — 12 cases
Outcomes
100% of determinate cases resulted in blocked access — 31 percentage points above the archive-wide average of 69%. Only 0% resulted in recovered access — one of the lower survival rates in the archive.
Recovery path
Coerced Transfer is the most documented recovery path (4 cases, 33% of subset).
Documentation
67% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
25% of cases involved large or very large holdings (10+ BTC).
Geographic distribution
United Kingdom accounts for 100% of cases in this subset (12 of 12).
Structural dependency
100% of cases carry a single-person knowledge dependency tag — the most common structural factor in this subset.
10
Blocked
0
Constrained
0
Survived
2
Indeterminate

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

12 observed cases
Blocked
10 (83%)
Indeterminate
2 (17%)
Oxford Armed Robbery: £1.1 Million Cryptocurrency Transferred Under Physical Duress
Software wallet
Blocked 2025
In November 2025, four armed men robbed a vehicle containing five occupants near Oxford, England. During the incident, one occupant was subjected to physical co
Jacob Irwin-Cline Drugged in London, $123K in Bitcoin and XRP Stolen
Software wallet
Blocked 2025
In May 2025, Jacob Irwin-Cline, an American tourist visiting London, was targeted by an attacker who posed as an Uber driver. The assailant drugged Irwin-Cline
London Home Invasion: 1,000+ ETH Transferred Under Machete Coercion
Software wallet
Blocked 2024
In June 2024, three men armed with machetes forced entry into the home of Ramesh Nair in London, England. The attackers coerced Nair to transfer more than 1,000
London Teenage Gang: £115,000 Cryptocurrency Robbery by Knifepoint 2021–2022
Software wallet
Blocked 2021
Between 2021 and 2022, a group of teenagers executed a systematic campaign of armed home invasions targeting cryptocurrency holders in London. The gang, numberi
Multibit Wallet Recovery Failure: Invalid 16-Word Seed Phrase After 7 Years
Software wallet
Indeterminate 2021
NickyGH established a Multibit wallet in 2014 at a Bitcoin education event held in Shoreditch, London. A technician guided the setup and instructed the user to
James Howell Bitcoin Hard Drive: Decade-Long Landfill Recovery Attempt Denied
Software wallet
Blocked 2015
James Howell, a Bitcoin holder from the 2014–2015 era when Bitcoin traded below $1,000, discarded a hard drive containing his private keys while cleaning his of
MultiBit 16-Word Seed Recovery Failure: Non-Standard Implementation
Software wallet
Indeterminate 2014
In 2014, NickyGH attended a Bitcoin wallet setup workshop in Shoreditch, London organized through a community meetup. A technician guided attendees through Mult
10,000 DOGE from Bittylicious (2014): Device Loss, No Backup, SSD Wiped
Software wallet
Blocked 2014
In December 2014, a UK-based BitcoinTalk user (apda) received 10,000 DOGE from Bittylicious, a London-regulated cryptocurrency exchange (BIOM Ltd), and directed
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Software wallet
Blocked 2013
James Howells, a UK resident, discarded a hard drive containing an encrypted Bitcoin wallet during a routine office clearance in 2013. The device was disposed o
Desktop Software Wallet Erased During PC Reset — Seed Phrase Never Recorded
Software wallet
Blocked
A Bitcoin holder maintained their first cryptocurrency wallet as a hot wallet on a personal computer, following a common early-adoption pattern of minimal secur
James Howells' 7,500 Bitcoin: Hard Drive Lost in Newport Landfill
Software wallet
Blocked
James Howells, a software engineer in Newport, South Wales, accidentally discarded a hard drive containing approximately 7,500 to 8,000 Bitcoin in the early 201
More United Kingdom cases
Related pages
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