CustodyStress
ArchiveLegal or authority constraint › Hardware wallet (single key)
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00765

UK Court Blocks Landfill Excavation for Lost Bitcoin Hard Drive

Blocked

Legal or institutional constraint prevented access — the authorized party could not move the funds.

Case description

A Bitcoin holder in the United Kingdom accidentally discarded a hard drive containing an unknown quantity of Bitcoin among household waste. The device was transported to a landfill site. Unlike some high-profile recovery cases where archaeological excavation has been pursued, this holder faced an institutional barrier: the UK court system declined to authorize landfill excavation to recover the hardware.

The custody failure itself was straightforward — the sole copy of wallet data stored on a single device without backup documentation or redundancy. However, the case's distinguishing feature lay not in the technical failure but in the legal and municipal constraints that prevented recovery despite the asset's known location.

The holder initiated legal proceedings to authorize excavation. The court determination weighed multiple factors: the cost of large-scale landfill recovery operations, environmental impact, and potential legal precedent concerns regarding private financial claims against municipal waste infrastructure. The court concluded that these considerations outweighed the private financial benefit to the individual claimant.

Observers noted the psychological and financial strain on the holder, compounded by Bitcoin price appreciation since the discard date. The case illustrates a custody failure mode that transcends technical or human error alone — it demonstrates how institutional systems (legal, regulatory, municipal) can create an absolute, irreversible barrier to asset recovery even when the physical device remains accessible and the recovery path is technically feasible. The finality of the court's decision left the holder with no practical recourse.

Custody context
Stress conditionLegal or authority constraint
Custody systemHardware wallet (single key)
OutcomeBlocked
DocumentationPresent and interpretable
CountryUnited Kingdom
Structural dependencies observed
Single Person KnowledgeDevice Specific AccessUndocumented procedureLegal Authority Required
What this illustrates
Only one person knew how the setup worked — and that person wasn't available. A single-key hardware wallet concentrates access in one device and one seed phrase. Either alone is insufficient — both are required. Legal authority and operational access are separate problems. Having the legal right to Bitcoin does not automatically provide the technical means to move it. There was no documentation of how access worked. Without it, there was no path back in. A blocked outcome in this archive means that no path to authorized access was found under the conditions documented.
Why this matters

When legal authority exists but operational access does not

Legal authority constraint cases document a gap that is unique to self-custody Bitcoin and has no precise equivalent in traditional finance. An executor has letters testamentary. A trustee has trust documents. A power of attorney holder has a valid, signed, notarized document. All of this legal apparatus exists, is valid, and is enforceable — against institutions. It is unenforceable against a blockchain.

Traditional financial institutions bridge the legal system and the operational system. A bank transfers funds when presented with a probate order because the bank is regulated, operates within the legal system, and has processes for accepting legal authority. A Bitcoin blockchain has none of these properties. It validates cryptographic signatures. That is the entirety of its access model.

Cases in this archive involving legal authority constraints fall into two main categories: cases where the legally authorized party lacks the credentials to exercise authority (the executor has the court order but not the seed phrase), and cases where legal or regulatory structures have blocked access to an exchange or custodial platform (sanctions, court-ordered freezes, regulatory seizures). The first category often has no technical resolution. The second depends on the legal process that imposed the constraint.

The gap is most pronounced in estate and inheritance contexts, where the deceased owner's legal authority transferred to an executor who was not given — and could not compel — the operational credentials.

How this category of failure is typically preventable

Legal authority constraint cases are resolved before the stress event, not during it. The resolution is ensuring that legal authority and operational access are aligned: the executor knows where the credentials are, or has been designated as a trusted holder of credentials, or is working with a professional who was given access in advance. Legal documents alone do not bridge the gap — only pre-arranged operational access does.

Read more: The Authority-Access Gap in Bitcoin Custody →
Why can't an executor use a court order to access Bitcoin?
Bitcoin held in self-custody has no institution that recognizes or responds to court orders. A bank honors a probate order because the bank is regulated and operates within the legal system. A Bitcoin blockchain does not. The network validates cryptographic signatures, not legal authority. An executor with a court order and no credentials faces the same barrier as anyone without credentials.
Can a legal freeze or seizure order apply to self-custody Bitcoin?
A legal order can prohibit the holder from moving Bitcoin and can threaten consequences for non-compliance. It cannot technically prevent transactions if the holder has the credentials and chooses to move funds. In practice, most holders comply with legal orders. But in cases where the holder cannot comply — because they are incapacitated or deceased — the order has no mechanism for enforcement against a wallet that responds only to cryptographic keys.
What is the gap between legal authority and Bitcoin access?
Legal authority operates through documents, institutions, and courts. Bitcoin access operates through cryptographic possession. Traditional assets have institutions that bridge these systems — banks accept court orders, brokerages transfer shares on direction. Self-custody Bitcoin has no such bridge. An authorized party must also have — or be able to obtain — the technical credentials. Legal authority alone is insufficient.
Source
Publicly Reported
Most structurally similar case
Tax Conviction Forces $124M Bitcoin Disclosure Order, But Keys Remain Inaccessible
Legal or authority constraint · Hardware wallet (single key) Blocked
Related cases
Structural patterns in this case
Device discardedLegal proceedingsRecovery attempted, access still blocked
23 cases involve legal or authority constraint 70 cases involve hardware wallet (single key) View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
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