What Is a Bitcoin Inheritance Test

The Gap Between Legal Transfer and Technical Access

This memo is published by CustodyStress, an independent Bitcoin custody stress test that produces reference documents for individuals, families, and professionals.

Legal Documents Say Who Inherits. Access Is a Different Question.

People searching for information about bitcoin inheritance tests are often arriving from a specific kind of uncertainty. The will names a beneficiary. The estate plan includes bitcoin. The holder told someone where the documentation is kept. What remains unclear is whether any of that is enough — whether the person named can actually reach the bitcoin, or whether the plan describes an outcome that the technical reality of the custody arrangement doesn't actually produce.

A bitcoin inheritance test asks that second question. Not whether the legal documents are correctly drafted or whether the named recipient has authority under the law, but whether that person can complete the access sequence using what the holder left behind. The plan can be valid and still fail this test. Legal transfer and technical access are different events, and an inheritance test is the only evaluation that asks about both together.

---

Why Legal Authority and Technical Access Diverge

Bitcoin custody operates through cryptographic keys. Whoever controls the keys controls the bitcoin, independent of what any document says about ownership. Probate courts grant authority over estates. That authority does not unlock a hardware wallet. A will correctly names a beneficiary. The will cannot supply the seed phrase.

This divergence is structural, not a planning failure. Legal systems transfer title and authority. Technical systems respond only to the correct credentials presented in the correct sequence. An executor with full legal authority over an estate and no access to the hardware wallet PIN occupies a position most legal frameworks weren't designed to address. The authority is real. The access is absent. Both things are true simultaneously.

The divergence surfaces most acutely in time-sensitive situations. Estate tax filings operate on legal deadlines. Bitcoin access depends on technical conditions. A CPA needs to know the value of bitcoin holdings for Form 706 before the deadline arrives. Whether the executor has been able to access those holdings, verify balances, or even confirm what platforms are involved depends on technical access that proceeds on its own timeline, unaffected by filing calendars.

---

What an Inheritance Test Examines

An inheritance test asks whether the sequence described in an inheritance plan can be completed by the people it names, using the access they actually have, under the conditions that follow a death. An estate attorney might call this a bitcoin inheritance evaluation. A financial advisor might frame it as an inheritance check. The label varies by profession, but the examination is the same: it traces four distinct layers.

The first is whether the heir can locate everything the plan describes. Documentation references hardware devices, seed phrase backups, passphrase notations, and platform account credentials. Each reference assumes the item is where the documentation says it is, in the condition it was in when the note was written. Physical items move. Paper degrades. Devices get replaced and the documentation doesn't always follow.

The second layer is whether what the heir locates is sufficient to complete access. A seed phrase alone may not restore a wallet if a passphrase was applied and not recorded. A hardware device alone does nothing without a PIN. Platform account credentials without access to two-factor authentication create a barrier that the credential list cannot resolve. The question isn't whether individual items exist — it's whether the combination present is complete.

Third is whether the heir can operate what they've been given. Technical familiarity varies sharply. An heir who has never held a hardware wallet encounters a device interface, a PIN entry mechanism, and a restoration process that may feel entirely opaque. The documentation may describe steps correctly and still be unnavigable to someone who has no reference frame for what the steps mean in practice.

Fourth is whether the platforms and systems involved still function as the documentation describes. Wallet software updates. Exchange interfaces change. Hardware manufacturer support ends for older devices. Documentation written in 2020 may describe procedures that a 2025 system no longer presents in the same way, or at all.

---

Where the Gap Between a Valid Plan and a Functional One Surfaces

The most common gap location isn't a missing document. It's an undocumented assumption the holder made when writing the plan — something so familiar to them that recording it didn't seem necessary.

Passphrases represent one of the most frequent examples of this pattern. A holder uses a passphrase on their wallet. They consider it memorable and obvious. The seed phrase backup exists and is correctly recorded. The passphrase is not written down anywhere because the holder didn't think of it as a separate piece of information that would need to be conveyed. An heir who restores from the seed phrase reaches a wallet with a different address derivation than the one the holder used. The bitcoin appears absent. The plan was complete in every other respect.

Platform-specific account recovery creates a different version of the same gap. An heir has the username and password for an exchange account. Two-factor authentication was enabled on the holder's phone. That phone is locked, or the number is no longer active, or the authentication app's codes are tied to a device the heir cannot access. The credentials are present. The authentication layer blocks the access they describe.

A third gap location is the organization of the documentation itself. Holdings distributed across multiple wallets, exchanges, and custody types require a coherent map for an heir to follow. Without that map, correctly documented individual items don't connect into a traversable whole. An attorney representing an estate discovers hardware wallets, exchange account records, and a note referencing a multisignature arrangement — but no document explains how the pieces relate or which of them hold meaningful balances.

---

How Inheritance Testing Differs from Plan Review

Plan reviews examine whether an inheritance arrangement is correctly structured — whether the legal documents name the right people, whether the executor has authority, whether the documentation is present and organized. A plan can pass this review completely and still fail to produce accessible bitcoin for the heir it names.

Inheritance testing asks the next question: does the arrangement actually work under real conditions? That means tracing the access sequence the plan describes, from the heir's starting position — no existing knowledge of the custody arrangement, no ability to ask the original holder for clarification — through each layer to confirmed access. Where that trace breaks, the gap becomes visible.

The two evaluations are not redundant. Plan review and inheritance testing address different failure modes. A plan with missing documents fails review. A plan with present documents that assume knowledge the heir doesn't have passes review and fails testing. Both types of failure result in the same outcome for the heir: no access to bitcoin they were supposed to receive.

---

What the Holder's Knowledge Supplies That the Plan Does Not

Inheritance plans are written by people who already understand their own custody arrangement. That understanding shapes the documentation in ways the holder typically doesn't notice — the notes assume the reader can identify which wallet software was used, which derivation path is standard, what a passphrase field looks like in the device interface, and how to interpret a seed phrase written in a specific word order.

Holders often conduct informal tests of their own documentation and find it complete. They read the notes and can follow them easily. The test is not useful because the holder supplies all the missing information from memory while reading, without noticing they're doing it. An heir reading the same notes arrives at the same gaps without the same knowledge to fill them.

This dynamic is why documentation written for a technically familiar audience fails when the actual heir is a spouse who has heard the word "wallet" but never interacted with one, or an attorney who understands the legal dimension of the estate but has no reference point for what a hardware device recovery process involves. The gap isn't negligence in the documentation. It's a mismatch between the audience the holder imagined when writing and the person who actually shows up to use it.

---

Inheritance Testing as a Concept

Bitcoin inheritance testing names a specific evaluation: does the arrangement produce accessible bitcoin for the named recipient under conditions that follow a death? That question sits after everything else — after the plan is drafted, the documents are organized, the legal authority is established. It asks whether all of that produces the outcome it describes.

The evaluation is distinct from security review, which asks whether unauthorized access is blocked. It's distinct from plan review, which asks whether documents are present and correctly structured. Both of those matter; neither of them asks whether the heir can complete the access sequence. That is what inheritance testing examines.

The failure the test exposes is consistent across custody types: the holder's knowledge, present throughout the setup and planning process and invisible in every document, quietly supplies what the documentation omits. When that knowledge is gone, what remains is the documentation as written — and whether it's enough for someone who wasn't there when it was created.

---

Summary

A bitcoin inheritance test asks whether the person named to receive bitcoin can actually access it. Legal documents establish authority; technical access depends on whether the heir can complete the custody arrangement's access sequence without assistance from the original holder. These two conditions are independent, and an inheritance plan can satisfy the first while failing the second.

The gap between a valid plan and a functional one most often surfaces at the layer the holder didn't think to document — a passphrase treated as obvious, a two-factor authentication dependency tied to an inaccessible device, an assumption about technical familiarity the heir doesn't share. Plan reviews examine whether documentation is present. Inheritance testing asks whether what's present actually works for the heir who arrives to use it.

The failure mechanics are consistent. The holder's knowledge fills documentation gaps invisibly throughout the planning process. When that knowledge is absent, those gaps become the thing that determines whether the inheritance the plan describes is the inheritance the heir receives.

System Context

Authority–Access Gap

Spouse Avoids Touching Bitcoin After Death

Cross-Domain Intersection Index

← Return to CustodyStress