CustodyStress
Archive › Country and outcome › United States — Survived
Part of the CustodyStress archive of observed Bitcoin custody incidents
United StatesSurvives

United States — Survived

Bitcoin custody cases from United States with a survived outcome. 13 documented cases in the archive.

Archive analysis — 13 cases
Outcomes
0% of determinate cases resulted in blocked access — 69 percentage points below the archive-wide average of 69%. 100% resulted in recovered access — above the archive average.
Primary stress condition
38% of cases involve coercion. Seed phrase unavailable accounts for a further 15%.
Recovery path
Coerced Transfer is the most documented recovery path (4 cases, 31% of subset).
Documentation
77% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
38% of cases involved large or very large holdings (10+ BTC).
Geographic distribution
United States accounts for 100% of cases in this subset (13 of 13).
0
Blocked
0
Constrained
13
Survived
0
Indeterminate

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

13 observed cases
Survived
13 (100%)
Amouranth's $20M Bitcoin Wallet Posted Publicly; Armed Home Invasion Followed
Unknown custody system
Survived 2025
Kaitlyn Siragusa, a prominent streaming and content creator known online as Amouranth, posted a screenshot displaying what appeared to be a $20 million Bitcoin
Italian Crypto Entrepreneur Survives Torture Ordeal in Manhattan, Keeps Bitcoin
Unknown custody system
Survived 2025
In May 2025, a 28-year-old Italian cryptocurrency entrepreneur based in New York City was abducted and held captive in a luxury Manhattan apartment for several
Irvine Home Invasion Targeting $3.8 Million in Cryptocurrency — Seven Arrested
Unknown custody system
Survived 2025
In September 2025, seven suspects forced entry into a residential property in Irvine, California. Operating under the belief that occupants possessed approximat
Little Elm, Texas Home Invasion: $1.4M Hardware Wallet Sought but Not Found
Hardware wallet (single key)
Survived 2022
In December 2022, armed home invaders broke into a residential property in Little Elm, Texas, and subjected the occupants to approximately three hours of tortur
Computer Crash with wallet.dat Backup: Bitcoin Core Recovery Without Private Key Export
Software wallet
Survived 2018
In February 2018, a Bitcoin Core user experienced a total computer crash requiring complete system reinstallation. The user had previously used an Armory wallet
Mark Frauenfelder's 7.4 BTC: Seed Phrase Discarded by Housecleaner, Recovered via Hardware Vulnerability
Hardware wallet (single key)
Survived 2017
Mark Frauenfelder, editor-in-chief of Boing Boing and Wired contributor, purchased 7.4 Bitcoin in January 2016 for approximately $3,000 and transferred it to a
Armed Kidnapping for Hardware Wallet Access: $1.8M Ether Theft — New York 2017
Hardware wallet with passphrase
Survived 2017
On November 4, 2017, Louis Meza, 35, of Jersey City, New Jersey, orchestrated a sophisticated attack against a personal acquaintance in New York City. Meza arra
Colorado Bitcoin Investor Death: Family Discovery and Coinbase Estate Transfer 2017
Exchange custody
Survived 2017
A Colorado-based Bitcoin investor died suddenly in 2017 without informing his family of his cryptocurrency holdings. The family had no initial awareness that he
Corrupted 2013 wallet.dat Recovery via Community-Guided Disk Scanning
Software wallet
Survived 2017
In December 2017, a macOS Bitcoin Core user attempted to restore access to two wallet.dat files created in late 2013. The user had downloaded a contemporary ver
Colorado Estate: Bitcoin Recovered via Coinbase After Sudden Death (2017)
Exchange custody
Survived 2017
A Colorado resident in his twenties died unexpectedly in 2017, leaving his family to navigate an unanticipated cryptocurrency holding. The discovery came only a
Encrypted wallet.dat passphrase mismatch: offline wallet creation to recovery (2013)
Software wallet
Survived 2013
In July 2013, a user created an encrypted wallet on an Ubuntu live CD and stored the wallet.dat file offline. Several months later, in December 2013, he importe
Formatted Computer, Lost Wallet.dat Access—Recovered via Time Machine Backup
Software wallet
Survived 2011
On July 3, 2011, forum user Omega0255 reported a critical custody error with a 1 BTC mining pool payment. The user had formatted their SSD drive using a secure
Mark Frauenfelder's 7 Bitcoin: Household Cleaner Discards Written Seed Phrase
Hardware wallet (single key)
Survived
Mark Frauenfelder, a US journalist, purchased approximately 7 Bitcoin in early 2016 at roughly $3,000 total investment. As the asset price appreciated significa
Country and outcome
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