CustodyStress
Archive › Browse by outcome and custody type › Indeterminate — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
IndeterminateSoftware wallet

Indeterminate — Software wallet

Cases where a software wallet access failure has an unknown or unresolved outcome. These cases represent custody situations where the structural failure is documented but whether recovery was ultimately achieved is not recorded in available sources.

Archive analysis — 253 cases
Documentation coverage
100% of cases have indeterminate outcomes — higher than the archive average of 43%.
Primary stress condition
43% of cases involve passphrase unavailable. Seed phrase unavailable accounts for a further 23%.
Recovery path
Password Bruteforce is the most documented recovery path (65 cases, 26% of subset).
Documentation
90% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
88% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
253 observed cases
Indeterminate
253 (100%)
Forgotten wallet.dat Password Blocks Access to Early Bitcoin Holdings
Software wallet
Indeterminate 2026
In February 2026, forum user lacuanto reported a custody access failure involving Bitcoin purchased during 2010–2011. The user had located an encrypted wallet.d
Incomplete Seed Backup + Device Loss: ipsbruno3's GPU-Powered Recovery Attempt
Software wallet
Indeterminate 2026
ipsbruno3 has held Bitcoin since 2013 and stored the majority in a wallet protected by a 12-word BIP39 seed phrase. The holder implemented a four-layer backup s
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
Armory Wallet Passphrase Loss: 2 BTC, Recovery Script Dependencies Unresolved
Software wallet
Indeterminate 2025
In January 2025, a BitcoinTalk forum user identified as Ronnie666 disclosed possession of an encrypted Armory .wallet file containing 2 BTC, estimated then at $
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
Electrum Seed Phrase Verified but Funds Inaccessible: Derivation Path Recovery Failure
Software wallet
Indeterminate 2025
In July 2025, the user 'nodc3' created a Bitcoin wallet using Electrum on macOS and deposited a small amount. Initial backup verification succeeded: the wallet
Forgotten Passphrase on Legacy wallet.dat: 1 BTC Recovery Attempt via Brute Force
Software wallet
Indeterminate 2025
In July 2025, a BitcoinTalk user identified as Maidak discovered an old wallet.dat file from years prior containing approximately 1 BTC. The wallet had been enc
Pre-HD Bitcoin Core Wallet Lost in OS Upgrade: Backup Strategy Failure
Software wallet
Indeterminate 2025
In June 2025, a Bitcoin forum user reported a custody failure involving a Bitcoin Core wallet created circa 2014, during the era before hierarchical determinist
Recovering Bitcoin from Encrypted 2013 Mt. Gox-Era Wallet.dat Without Passphrase
Software wallet
Indeterminate 2025
In early January 2025, a BitcoinTalk forum user ('thowed-away-agin') disclosed possession of an encrypted wallet.dat file originating from the Mt. Gox era (2013
External Hard Drive Theft with Private Key Recovery Attempt
Software wallet
Indeterminate 2024
On May 26, 2024, a BitcoinTalk user (Niandertal@2024) reported the theft of an external hard drive containing a Bitcoin wallet file. The user had retained posse
Encrypted Wallet.dat Lost After Father's Sudden Death—No Recovery Path
Software wallet
Indeterminate 2024
In February 2024, floki5444 posted on BitcoinTalk describing the loss of access to a Bitcoin wallet belonging to their deceased father. The father died unexpect
Sudden Death, Lost Passphrase: Bitcoin Core Wallet.dat Inaccessible to Heirs
Software wallet
Indeterminate 2024
A Bitcoin holder died suddenly and unexpectedly after an apparent recovery from illness, leaving behind a Bitcoin Core wallet.dat file with no disclosed passphr
Three Recovered wallet.dat Files (2009–2013): Corruption, Incompatibility, and Unknown Passphrase
Software wallet
Indeterminate 2024
Jay, an early Bitcoin participant who mined from 2009 onwards, stored wallet.dat files with minimal backup discipline—copying them to memory sticks as was custo
Forgotten BIP39 Passphrase: BTCRecover Brute-Force Fails to Recover Access
Software wallet
Indeterminate 2024
JMASTERJ, a BitcoinTalk forum user, discovered a critical access failure in a self-custody wallet setup using a 12-word BIP39 seed phrase combined with an addit
Early Bitcoin Miner Seeks File Signature Recovery After Hard Drive Deletion
Software wallet
Indeterminate 2024
DVCMI776 mined a significant quantity of Bitcoin during the early Bitcoin era and stored the wallet files on a hard drive. The drive subsequently failed, initia
Samsung Phone Mining Wallet: 0.7 BTC Inaccessible After Device Wipe
Software wallet
Indeterminate 2024
In February 2024, a BitcoinTalk user (onisuk20) rediscovered a Samsung phone containing Bitcoin holdings generated during the early mining period around August
Deceased Partner's Encrypted wallet.dat: Password Confirmed but Holdings Unverifiable
Software wallet
Indeterminate 2024
In May 2024, a non-technical forum user discovered a wallet.dat file on an SD card containing personal photos belonging to their deceased partner, described as
Forgotten Bitcoin Core Passphrase: Family Lifesavings Locked After Home Invasion
Software wallet
Indeterminate 2024
SpaceMarine770 moved Bitcoin from Blockchain.com to Bitcoin Core (Version 25) in August 2024, approximately one to two weeks before reporting a home invasion an
Deleted wallet.dat Recovery Attempt: Corruption Barrier (Tigerbill, May 2023)
Software wallet
Indeterminate 2023
In May 2023, Tigerbill, a junior member of the BitcoinTalk forum, permanently deleted their wallet.dat file containing an unspecified quantity of Bitcoin. The u
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
Electrum Wallet Password Lost With Corrupted SSD Backup
Software wallet
Indeterminate 2023
On November 15, 2023, a BitcoinTalk user reported being unable to access an Electrum wallet after losing the 8–9 character password derived from a longer 15-cha
Scrambled Seed Phrase: 2500 BTC Unrecoverable Without Word Order
Software wallet
Indeterminate 2023
In December 2023, a recovery specialist designated iconbtcx was engaged to restore access to 2500 BTC held in a BIP39-compliant software wallet. The client poss
Lost Electrum Wallet: Encrypted Backup Without Password or Seed Phrase
Software wallet
Indeterminate 2023
On March 17, 2023, a BitcoinTalk forum user (Lavey666) posted to the Electrum wallet software section describing a complete loss of access to their self-custodi
Recovering Lost Armory Wallet from Overwritten 2009-2010 Laptop Disk
Software wallet
Indeterminate 2023
In June 2023, a Bitcoin holder initiated a public recovery effort for an Armory wallet created in 2009–2010 on a personal laptop. The original device remained i
Electrum Wallet Password Loss: 0.5 BTC Inaccessible After Partner's Accidental Send
Software wallet
Indeterminate 2023
In April 2023, a BitcoinTalk user (mrleaker) reported losing access to an Electrum wallet containing 0.5 BTC. The wallet had been created years prior as a refer
← PreviousNext →
Browse by outcome and custody type
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