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

United States — Software wallet

Cases from the United States involving software wallet custody failures. The US software wallet subset is the largest country-specific custody category in the archive, spanning passphrase loss, seed unavailability, and device loss patterns.

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

Archive analysis — 39 cases
Outcomes
82% of determinate cases resulted in blocked access — 13 percentage points above the archive-wide average of 69%.
Documentation coverage
44% of cases have indeterminate outcomes — higher than the archive average of 43%.
Documentation
36% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Geographic distribution
United States accounts for 100% of cases in this subset (39 of 39).
Structural dependency
82% of cases carry a undocumented recovery procedure dependency tag — the most common structural factor in this subset.
18
Blocked
0
Constrained
4
Survived
17
Indeterminate

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

39 observed cases
Blocked
18 (46%)
Survived
4 (10%)
Indeterminate
17 (44%)
Bitcoin Kidnapping: Italian National Tortured 17 Days for $28M Wallet Access
Software wallet
Indeterminate 2025
In May 2025, Nicola Carturan, an Italian national, was abducted and held captive for approximately 17 days in a luxury townhouse in Manhattan's SoHo district by
Los Angeles Wildfire Destroys Only Seed Phrase Backup — Total Loss
Software wallet
Blocked 2025
In January 2025, a Reddit user reported that their 70-year-old aunt had lost her entire cryptocurrency savings during the Los Angeles wildfires. The aunt had st
Armed Home Invasion: Family Forced to Complete $36K Crypto Transfer Under Duress
Software wallet
Blocked 2025
In September 2025, two armed brothers from Texas invaded a home in Grant, Minnesota and held the occupants hostage at gunpoint for approximately nine hours. The
Chicago Kidnapping and $15 Million Forced Crypto Transfer
Software wallet
Blocked 2024
In October 2024, six men executed a violent kidnapping at a Chicago townhouse, taking three family members and their nanny hostage. The attackers forced the vic
Bitcoin Core Wallet Encryption Generated New Seed: Lost Access to Funded Addresses
Software wallet
Blocked 2024
In June 2024, a Bitcoin Core user deleted their server and all associated data, but retained a backup copy of wallet.dat on their computer. The user encrypted t
Bitcoin Core Wallet Destroyed in Fire: Passphrase and Address Insufficient for Recovery
Software wallet
Indeterminate 2021
In February 2021, a Bitcoin Core user reported catastrophic loss of their wallet following a house fire. The hard drive containing the wallet was physically des
Coinbase Wallet $15,000 Loss: Deferred Seed Phrase, iPhone Update, No Recovery
Software wallet
Indeterminate 2021
A long-term Coinbase customer transferred approximately $15,000 USD to a newly created Coinbase Wallet in February 2021, intending to access Uniswap for decentr
Bitcoin-Qt Wallet Recovery: Encrypted Password, Formatted Hard Drive
Software wallet
Indeterminate 2021
In February 2021, a Bitcoin Stack Exchange user reported possessing an encrypted password and the associated address for a Bitcoin-Qt wallet created in 2011–201
Bitcoin Core 0.21 Wallet Rejects Passphrase During Spend Attempt
Software wallet
Indeterminate 2021
In April 2021, a Bitcoin Core 0.21 user encountered a critical custody failure when attempting to send coins from an encrypted wallet. The wallet prompted for a
Son Drugs Father and Steals $400,000 in Bitcoin in Bethesda, Maryland
Software wallet
Blocked 2021
In May 2021, a Bethesda, Maryland resident was incapacitated after his son spiked his tea with drugs, enabling the son to access and transfer approximately $400
Wallet.dat Corruption and Salvage Failure After Bitcoin.org Wallet Import
Software wallet
Blocked 2020
An individual who ran Bitcoin software during 2009 and 2010 located an old data file (renamed to xxxx.dat) years later and attempted to recover it. In July 2020
Peter Schiff Lost Access to Gifted Bitcoin After App Update, Never Recorded Seed Phrase
Software wallet
Blocked 2020
On January 19, 2020, Peter Schiff, an economist and well-known Bitcoin critic, announced on Twitter that he had lost access to all his Bitcoin. The funds—approx
Widow Inherits Crypto Apps and Recovery Codes After Husband's Death—PIN Unknown
Software wallet
Indeterminate 2019
In August 2019, a widow posted on Bitcoin Stack Exchange seeking help accessing her deceased husband's cryptocurrency holdings. Her 43-year-old husband, in appa
Bitcoin Core Wallet Deleted During Hard Drive Format — No Backup
Software wallet
Blocked 2019
In April 2019, a Bitcoin Core user downloaded the full-node software but encountered synchronization delays due to insufficient storage space. The installation
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
Bitcoin Knots Wallet Access Lost After SSD Migration: wallet.dat Location Mismatch
Software wallet
Indeterminate 2018
In May 2018, an inexperienced Bitcoin user (mortamuerte) initiated blockchain synchronization using Bitcoin Knots, a Bitcoin Core fork, on a laptop SSD. Partway
Alexander Halavais: Forgotten Password on 2010 Experimental Bitcoin Purchase
Software wallet
Blocked 2017
Alexander Halavais, an Associate Professor in the School of Social and Behavioral Sciences at Arizona State University, purchased a small quantity of Bitcoin ar
25 Bitcoin Lost After Computer Crash: Wallet Identity Unknown
Software wallet
Indeterminate 2017
In November 2017, a Bitcoin Stack Exchange user disclosed that they had purchased 25 bitcoins years prior and deposited them into a wallet on a personal compute
Bitcoin Lost After Hard Drive Format: wallet.dat Unrecovered, Private Key Missing
Software wallet
Blocked 2017
A Bitcoin holder received cryptocurrency in 2013 via Bitcoin Core but did not understand the critical role of the wallet.dat file in securing access to funds. I
Homeland Security Bitcoin Seizure: Unencrypted Seed Phrase Discovered During Search
Software wallet
Blocked 2017
BurtW, a BitcoinTalk forum user, revealed in April 2017 that he had been arrested and that Homeland Security conducted searches of both his home and office. Dur
Anonymous College Student: 40 BTC Locked Behind Forgotten Wallet Password (2017)
Software wallet
Indeterminate 2017
In late 2017, during Bitcoin's historic rally to $15,000–$19,000, an anonymous college student posted on Reddit describing a custody catastrophe rooted in 2013
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
Armory Desktop Wallet: 2 BTC Inaccessible Despite Paper and Encrypted Backups
Software wallet
Indeterminate 2016
A user purchased 2 BTC via Coinbase approximately 2013–2014 and transferred them to a self-hosted Armory wallet running on a personal server. The transfer compl
Zombie Paintball Incident: Written Password Loss Blocks Access to $20K Bitcoin
Software wallet
Blocked 2015
Luke purchased his first Bitcoin around 2013 for approximately $200 and continued accumulating holdings over roughly two years, investing between $15,000 and $2
Armory Wallet Lost via VirtualBox Snapshot Rollback—Binary Recovery Attempt
Software wallet
Indeterminate 2013
In October 2013, a BitcoinTalk user known as HowlingMad lost access to 6.59159344 BTC stored in Armory, a then-leading Bitcoin wallet application running on Win
← PreviousNext →
More United States 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.