Back to Blog
crypto after deathlost cryptocurrencybitcoin lost forevercrypto estate planningdigital asset loss

5 Ways People Lose Access to Crypto After a Death

AK
Abel Kuruvilla
15 min read
Share on X
5 Ways People Lose Access to Crypto After a Death

5 Ways People Lose Access to Crypto After a Death

Cryptocurrency worth tens of billions of dollars has been permanently lost because the private keys died with their owners. Unlike bank accounts, brokerage accounts, or real estate, crypto cannot be recovered through legal processes, court orders, or institutional intervention once the keys are gone. These are the five most common failure modes, each illustrated with real cases, and the specific measures that prevent each one.

1. Lost Private Keys with No Backup

The most straightforward and most common way crypto is lost after death is the simplest: the owner held their private keys (or seed phrase) in their memory, on a single device, or in a single physical location, and that information died with them or became inaccessible.

The Scale

Chainalysis estimates that approximately 3.7 million Bitcoin (roughly 17.6% of the total mined supply) have not moved since 2010 and are likely permanently inaccessible. While not all of this is due to death, a significant portion belongs to early adopters who have since passed away without leaving key access instructions. At current prices, this represents hundreds of billions of dollars in frozen wealth.

A Real Case: Matthew Mellon

Matthew Mellon, a banking heir and early cryptocurrency investor, held approximately $500 million in XRP at the time of his death in 2018. He had stored his private keys across multiple cold storage devices distributed in different locations, reportedly under other people's names for security. But he did not leave a clear map of where these devices were or how to access them. His family spent years attempting to locate and recover the holdings. The complexity of his security measures, intended to protect the assets during his life, became the obstacle that prevented recovery after his death.

The Root Cause

Private key management is a single-point-of-failure problem. A key stored in one place (a hardware wallet, a piece of paper, a digital file) has one failure mode: that place becomes inaccessible. The owner's death is the most absolute form of inaccessibility.

Many crypto holders compound this by treating security and inheritance as opposing goals. They make their keys harder to access (air-gapped devices, encrypted drives, memorized passphrases) without creating any recovery path that survives their own incapacitation.

The Solution

Shamir's Secret Sharing splits the key (or the key to an encrypted document containing the key) into multiple shares with a threshold for reconstruction. A 3-of-5 split means any 3 of 5 designated people can reconstruct the key, but no individual or pair can. This eliminates the single point of failure without creating a single point of compromise.

Combined with a dead man's switch that automatically notifies share holders when the owner stops responding to liveness checks, this ensures that the recovery process initiates without anyone needing to make a judgment call about whether the owner is dead.

For seed phrase backups specifically, SLIP-39 provides a standardized Shamir backup format supported by hardware wallets like Trezor, allowing shares to be recorded on durable physical media (steel plates) and distributed geographically.

2. Exchange-Only Holdings with No Succession Plan

The second most common loss scenario involves cryptocurrency held entirely on exchanges. The owner may have account credentials, but those credentials are not accessible to heirs, and the exchange's succession process is slow, limited, and not guaranteed to succeed.

The Scale

A 2024 survey by Coinbase found that only 20% of crypto holders have included their exchange accounts in any form of estate plan. The remaining 80% hold exchange-based crypto with no documented recovery path for their heirs.

A Real Case: Gerald Cotten and QuadrigaCX

The most extreme example is QuadrigaCX, a Canadian exchange whose founder, Gerald Cotten, died in December 2018 while traveling in India. Cotten was the sole custodian of the exchange's cold storage wallets, holding approximately $190 million in customer funds. His laptop was encrypted. No one else had access to the private keys. The exchange collapsed, customers lost their funds, and a subsequent investigation revealed that some of the wallets may have been depleted before his death (raising questions about fraud), but the core inheritance failure is clear: one person held the keys, and when that person became unavailable, the funds became inaccessible.

While this is an extreme case involving an exchange operator rather than an individual holder, the pattern is identical for anyone who holds significant crypto on an exchange with no plan for credential transfer.

The Root Cause

Exchange accounts are protected by email/password authentication, two-factor authentication (2FA), and often additional identity verification. When the account holder dies:

  • The email account may become inaccessible (see platform death policies).
  • 2FA devices (phone, authenticator app, hardware key) may be locked.
  • The exchange's identity verification system was designed for the account holder, not their heirs.

Exchange succession processes typically require a death certificate, proof of relationship, and legal authority (executor or administrator of the estate). Processing times range from weeks to months. Some exchanges have been known to deny access or require specific legal documentation that varies by jurisdiction. During this time, the crypto is frozen, and if the market moves adversely, the heirs have no ability to act.

The Solution

The first step is to move significant holdings to self-custody where possible. Exchange accounts are custodial: the exchange holds your keys, and you hold a claim. Self-custody gives you direct control and makes inheritance planning straightforward.

For holdings that must remain on exchanges (regulatory requirements, active trading, staking programs), include complete exchange account credentials in an encrypted inheritance document: email, password, 2FA recovery codes, answers to security questions, and the specific exchange's succession contact information.

Store this document in a system with threshold encryption and dead man's switch triggering. Tools like Burning Ash Protocol encrypt the document with AES-256-GCM, split the encryption key among designated survivors using Shamir's Secret Sharing, and automatically initiate the transfer when liveness checks fail.

3. Multisig Wallets Without Succession Planning

Multisig wallets require multiple signatures to authorize transactions. This is excellent operational security, but it creates a specific inheritance failure mode: if the required number of signers becomes unavailable and no succession plan exists for the signing keys, the funds are locked.

The Scale

Multisig adoption has grown significantly in institutional and high-net-worth crypto custody. Gnosis Safe (now Safe) alone secures over $100 billion in assets. The percentage of these wallets with documented succession plans for their signers is unknown but almost certainly low.

A Real Case: The DAO Multisig Freeze

While not a death-related case, the broader category of multisig key loss has multiple documented instances. In 2017, a vulnerability in Parity Technologies' multisig wallet library led to the permanent freezing of approximately 513,000 ETH (worth roughly $150 million at the time) when a user accidentally destroyed the library contract that the wallets depended on. No death was involved, but the outcome is identical: funds locked because the required signing capability was lost.

In the inheritance context, a 2-of-3 multisig where the deceased held 2 of the 3 keys becomes a 0-of-1 from the heirs' perspective if those 2 keys are lost. Even a 2-of-3 where the deceased held only 1 key becomes a 2-of-2 for the remaining signers, eliminating the fault tolerance that the multisig was designed to provide.

The Root Cause

Multisig security assumes that signers remain available. The configuration is designed for operational security (preventing theft by any single key compromise), not for succession. When a signer dies:

  • Their signing key may be inaccessible (hardware wallet locked, software wallet on encrypted device).
  • The remaining signers may not have enough signatures to meet the threshold.
  • There is no mechanism to replace a dead signer without a transaction signed by the existing threshold.

The Solution

Document the multisig configuration in the inheritance plan: which addresses are multisig, what the threshold is, who the other signers are, and where the deceased's signing keys are stored.

Include the signing key or its recovery method in the encrypted inheritance document. If the signing key is on a hardware wallet, include the device PIN and the seed phrase backup.

Coordinate with co-signers. Ensure that co-signers know about the inheritance plan and understand that they may need to participate in asset recovery. If the multisig is 2-of-3 and the deceased held 1 key, the co-signers need to know they should cooperate with the heir.

Consider a time-locked recovery path. Some multisig implementations support adding a recovery address that can move funds after a time delay. This can serve as a dead man's switch at the blockchain level.

4. Hardware Wallets Without Accessible Backup

Hardware wallets (Ledger, Trezor, Coldcard) are the gold standard for Bitcoin security. They keep private keys on a dedicated device that never exposes them to a networked computer. But a hardware wallet is a physical object, and physical objects can be lost, damaged, or locked behind a PIN that dies with its owner.

The Scale

Ledger has sold over 6 million hardware wallets. Trezor has sold over 2 million. The percentage of users who have a documented, accessible seed phrase backup is unknown, but hardware wallet manufacturers consistently report that a significant portion of support tickets involve users who have lost access to their device and do not have their seed phrase.

A Real Case: Stefan Thomas and the IronKey

Stefan Thomas, a programmer, stored 7,002 Bitcoin (worth over $200 million at peak prices) on an IronKey encrypted USB drive. He lost the paper where he wrote the password. The IronKey allows 10 password attempts before permanently encrypting the drive's contents. As of the last public report, Thomas had used 8 of his 10 attempts. While Thomas is alive and this is a "lost password" story rather than a death story, it illustrates the identical failure mode: a hardware device secures the keys, the access credential is lost, and the device's security features prevent brute-force recovery.

For inheritance, the scenario is even worse. The device owner dies. The family finds the hardware wallet but doesn't know the PIN. They don't know if a seed phrase backup exists or where to find it. The device's security features (limited PIN attempts, wipe after failed attempts) make experimentation dangerous.

The Root Cause

Hardware wallet security is designed around the assumption that the device owner is the only person who should access it. The PIN, the passphrase, and the physical device itself are all barriers optimized for preventing unauthorized access. After the owner's death, the authorized user is absent and the security barriers remain.

The seed phrase (the 12 or 24 words generated when the device was initialized) is the canonical backup. But seed phrases are often stored poorly: on a piece of paper in a drawer, in a digital file on a computer, or in the owner's memory. These storage methods fail in the inheritance context for obvious reasons.

The Solution

Never rely on the hardware device itself for inheritance. The device is a convenience for daily use, not a long-term backup. The seed phrase backup is the real backup.

Store the seed phrase using Shamir's Secret Sharing. Generate SLIP-39 shares (if supported by your hardware wallet) or use an application-layer Shamir system to split the seed phrase among multiple trustees.

Include the device PIN and passphrase (if a BIP-39 passphrase is used) in the encrypted inheritance document. Even if the seed phrase is the primary recovery method, having the device PIN allows immediate access without the reconstruction step.

Use durable media for seed phrase backups. Steel or titanium backup plates resist fire, flood, and corrosion. Paper degrades.

Document the hardware wallet model and firmware version. Recovery procedures differ across devices and firmware versions. A note saying "Trezor Model T, firmware 2.6.x, SLIP-39 backup with 3-of-5 threshold" saves the heirs significant confusion.

5. Custodial Service Shutdown

The fifth failure mode is external: the service holding or managing the crypto ceases to exist. This includes exchanges that go bankrupt, DeFi protocols that get exploited, lending platforms that become insolvent, and custodial wallet services that shut down.

The Scale

The crypto industry has experienced a series of high-profile custodial failures:

  • Mt. Gox (2014): 850,000 BTC lost or stolen. Creditors waited over a decade for partial repayment.
  • FTX (2022): $8 billion in customer funds missing. Bankruptcy proceedings ongoing.
  • Celsius Network (2022): $4.7 billion in customer deposits frozen, then partially distributed through bankruptcy.
  • BlockFi (2022): Declared bankruptcy following FTX collapse. Customer funds tied up in proceedings.
  • Voyager Digital (2022): $1.3 billion in customer assets frozen.

These are not inheritance failures per se, but they illustrate a risk that compounds with death: if the platform holding your crypto fails while you're alive, you can participate in legal proceedings, file claims, and manage the recovery process. If the platform fails after you die and your heirs don't know the account exists, the claim is never filed.

A Real Case: Cryptopia

Cryptopia, a New Zealand cryptocurrency exchange, was hacked in January 2019, losing approximately $16 million in customer funds. The exchange went into liquidation. Customers had to file claims with the liquidator to recover their funds. The process took years. Customers who had died between the hack and the claims deadline (or whose heirs didn't know about the Cryptopia account) had their claims go unfiled.

This is the compounding risk: custodial failure plus death equals permanent total loss, because the legal recovery process requires active participation that a dead person (and their uninformed heirs) cannot provide.

The Root Cause

Custodial services hold your crypto on your behalf. You don't hold the private keys; the service does. This means you are exposed to the service's operational risks: hacks, fraud, mismanagement, insolvency, and regulatory action. You are also exposed to the service's communication channels: if the service sends a "file your claim within 90 days" email to the deceased's email account, and no one is monitoring that email, the deadline passes.

The Solution

Self-custody for long-term holdings. The saying "not your keys, not your coins" is directly relevant to inheritance. Assets in self-custody cannot be lost to custodial failure.

Document all custodial relationships. The inheritance plan should list every exchange, lending platform, staking service, and DeFi protocol where assets are held. Include account credentials and the approximate value held.

Monitor for custodial events. This is where a dead man's switch adds value beyond just inheritance. If you die and your BAP instance triggers, your survivors receive not just the crypto recovery information but also the complete list of custodial services. They can check each one for the current status and file any necessary claims before deadlines expire.

Diversify custody. Don't hold all assets on a single platform. Spread across self-custody and, if necessary, multiple regulated custodians in different jurisdictions.

The Common Thread

All five failure modes share a root cause: the information required to access the crypto was concentrated in the hands of one person, and that person became unavailable. The specific form of concentration varies (a private key, a device PIN, an exchange password, a multisig signing key, knowledge that an account exists), but the structural problem is identical.

The solution is also structurally identical across all five scenarios: distribute the recovery information among multiple trusted people, encrypt it so no individual can access it alone, and automate the trigger so no one needs to make a judgment call about when to act.

This is exactly what threshold cryptography combined with a dead man's switch provides:

  • Shamir's Secret Sharing distributes trust across multiple survivors with a configurable threshold.
  • AES-256-GCM encryption ensures the inheritance document is inaccessible to any party that hasn't met the threshold.
  • Automated liveness checks detect the owner's absence and initiate the transfer without human judgment.
  • Multi-channel notifications ensure survivors are reached through email, SMS, WhatsApp, or Telegram.

Whether you implement this with SLIP-39 physical shares, a self-hosted tool like Burning Ash Protocol, a commercial service, or a combination of these, the principle is the same: eliminate single points of failure before they become single points of permanent loss.

What to Do This Week

If you hold any amount of cryptocurrency, take these actions within the next seven days:

  1. List every place you hold crypto. Exchanges, wallets, DeFi positions, staking, everything. Write it down.

  2. Verify your seed phrase backups. If you use self-custody, confirm that your seed phrase is recorded correctly and stored in a location that survives your death. Test recovery on a secondary device if you haven't done so recently.

  3. Tell one person. You don't need to share your private keys today. You need to tell one trusted person that you hold cryptocurrency and that they should look for inheritance instructions in a specific place. Even this minimal step prevents the "no one knew the account existed" failure mode.

  4. Set up threshold protection. Whether through SLIP-39 physical shares, an encrypted digital will, or a purpose-built tool like BAP, split your recovery information among multiple people with a threshold for reconstruction.

  5. Configure automated detection. Set up a dead man's switch so the transfer triggers automatically. Don't rely on someone noticing you're gone and deciding it's time to act.

The crypto you hold today could be worth significantly more in 10, 20, or 30 years. The inheritance plan you skip today has an identical chance of being needed in 10, 20, or 30 years. The asymmetry is clear: the cost of setting up a plan is a few hours. The cost of not having one is everything.

Related Articles