What Is a Bitcoin Inheritance Assessment
Evaluating Inheritance Arrangements as Functioning Systems
This memo is published by CustodyStress, an independent Bitcoin custody stress test that produces reference documents for individuals, families, and professionals.
Assessment Asks a Different Question Than Review
Estate attorneys, financial advisors, and fiduciaries working with bitcoin inheritance often arrive at a specific uncertainty: the documents are in order, but whether the arrangement actually works is less clear. The will names beneficiaries correctly. The executor has authority. A binder of custody documentation exists. What remains unresolved is whether those elements, taken together, produce the outcome the arrangement describes — whether the named heir can actually receive the bitcoin the plan assigns to them.
That unresolved question is what a bitcoin inheritance assessment addresses. It differs from a review of whether documentation is present and a review of whether legal authority is correctly established. Both of those evaluations confirm that components exist. Assessment asks whether the components compose a system that functions — whether the sequence from death to heir access can be completed using what the arrangement provides, by the people it names, without relying on knowledge or assistance the holder can no longer supply.
How Assessment Differs from a Checklist
Checklists and assessments operate at different levels of abstraction. A checklist — sometimes called a bitcoin inheritance check — works from a list of items that inheritance arrangements are expected to contain: seed phrase backup, device PIN notation, passphrase record, platform account credentials, executor instructions. Each item is either present or absent. A complete checklist indicates that everything on the list has been accounted for.
Assessment asks what the items that are present compose. Two inheritance arrangements can both complete the same checklist while producing entirely different outcomes under real conditions. One arrangement has a seed phrase backup that restores the correct wallet with the software an heir is likely to encounter. The other has a seed phrase backup that was written before a passphrase was added, restoring a wallet with a different address derivation than the one the holder actually used. Both pass the checklist. The assessment of the second arrangement exposes a system failure the checklist cannot see.
The failure isn't in the checklist item — the seed phrase backup exists. The failure is in the interface between that item and the next layer: the passphrase that the backup alone cannot supply. Checklists evaluate components. Assessment evaluates the interfaces between them. Those interfaces are where bitcoin inheritance most frequently fails.
What an Inheritance Assessment Evaluates
An inheritance assessment traces the access sequence the arrangement describes, from the position of someone who had no involvement in the original setup and cannot ask the holder for clarification. That starting position matters because it determines which assumptions the documentation is allowed to make and which it has to supply explicitly.
The trace covers four dimensions. First: whether the arrangement accounts for all holdings. Bitcoin distributed across hardware wallets, exchange accounts, and multisignature setups requires a map connecting those components. Without it, correctly documented individual items don't add up to a complete picture. An executor who finds three hardware wallets and a note referencing an exchange account doesn't know whether those are all the holdings or whether additional accounts exist that the note doesn't mention.
Second: whether each access path is complete at every layer. A hardware wallet recovery requires the seed phrase, the passphrase if one was applied, knowledge of which wallet software to use, and familiarity with the derivation path. Each layer that is absent or ambiguous in the documentation represents a point where the access sequence can fail. Assessment traces each path to confirm that every layer is accounted for, not just the ones most commonly documented.
Third: whether the people named can operate what they've been given. Technical familiarity across heirs, executors, and attorneys varies widely. An assessment considers whether the documentation is navigable by someone without the holder's background. Instructions that correctly describe a process for a technically fluent reader may present as opaque to an executor encountering hardware wallet interfaces for the first time.
Fourth: whether the arrangement remains accurate as time passes. Documentation describes the custody arrangement as it existed when written. Devices change, platforms update, and the gap between recorded state and current state widens over years. Assessment examines how the arrangement degrades over time, not just whether it was accurate at creation.
Where Document-Level Review and System-Level Assessment Diverge
The divergence appears most clearly at the interfaces between documentation components — the points where one piece of recorded information hands off to the next and the handoff depends on something the documentation doesn't supply.
A seed phrase record hands off to a wallet restoration process. That handoff works when the heir knows which software to use and what derivation path to apply. Neither of those things typically appears in a seed phrase record, because the holder who wrote it already knew them. The record is complete as documentation. The handoff fails because the knowledge it assumed isn't present in the person attempting the next step.
Platform account credentials hand off to account access. That handoff works when two-factor authentication is either absent or accessible to the heir. When authentication requires a device or phone number the heir doesn't control, the credential record is complete and the account is unreachable. Document review finds the credentials present. System assessment finds the authentication dependency that the credential record didn't capture.
The divergence isn't a failure of documentation quality. It's a structural property of how inheritance arrangements are created. Holders document what they consciously decided to document, from a perspective that already holds the knowledge required to complete the handoffs. The assessment frame shifts perspective to the heir's starting position, where those handoffs are not automatic, and traces which ones break from there.
Why Correctly Documented Arrangements Fail System Assessment
Documentation is created at a point in time by someone who understands the arrangement completely. That understanding shapes what gets written — what the holder considers worth recording, what they assume an heir will recognize without instruction, and what they treat as too obvious to mention. The documentation is accurate. It is also incomplete in ways the holder didn't notice were incomplete.
A holder who has used the same wallet software for three years doesn't think to record which software that is, because the choice feels self-evident. The device on the desk, the interface that opens when it's connected, the workflow they've repeated hundreds of times — none of that registers as information that needs to be conveyed. An heir who has never interacted with any wallet software encounters an unnamed device and no guidance about what to connect it to. The documentation covers the seed phrase correctly and omits the context entirely.
Time adds a second layer of correctly-documented failure. An arrangement documented in full accuracy in 2021 encounters a 2026 estate administration where one exchange has changed its account recovery interface, a hardware wallet manufacturer has ended support for the device model involved, and the wallet software the holder used has been superseded by a version with a different interface. The documentation was accurate. None of its accuracy translates to the environment the executor now faces.
The Assessment Frame and Its Professional Register
The word assessment carries a specific implication in professional contexts: evaluation against outcome criteria, not just component presence. An environmental assessment doesn't ask whether a site has been documented — it asks whether the site's documented conditions produce a defined result under specified conditions. A financial assessment doesn't ask whether accounts exist — it asks whether the accounts compose an arrangement that meets a particular standard.
Applied to bitcoin inheritance, the same logic holds. An inheritance assessment asks whether the arrangement produces accessible bitcoin for the named recipient under real conditions. That framing is more useful to attorneys evaluating an estate, fiduciaries considering their exposure, and families trying to understand what their planning actually produced. The checklist framing answers a narrower question — are the components present — that doesn't reach the thing these professionals need to know.
For estate attorneys, this distinction has practical weight. An attorney who reviews the documentation, finds it complete, and advises the family that the arrangement is in order has performed a document review. If the arrangement then fails at system level — if the heir cannot access the bitcoin despite complete documentation — the attorney's review didn't address the question that mattered. Assessment as a frame makes the scope of the evaluation explicit, and the limit of what document review alone can confirm.
What the Assessment Frame Reveals That Other Evaluations Miss
Treating an inheritance arrangement as a system with inputs, dependencies, and a defined output makes visible a category of failure that component-level review cannot reach. That category is interface failure — the breakdown that occurs not within a documented component but between components, at the point where one layer depends on another that the documentation doesn't fully describe.
Interface failures are consistent across custody types. Hardware wallet recovery interfaces with passphrase documentation — or the absence of it. Exchange account access interfaces with two-factor authentication — tied to a device or number that may not be accessible. A multisignature arrangement interfaces with cosigner availability and coordination — a social dependency that no technical documentation captures. In each case, the individual components are present and correctly recorded. The system fails at the boundary between them.
Assessment exposes these boundaries by tracing the full sequence rather than auditing components in isolation. The trace reveals what each step requires from the previous one, and whether that requirement is satisfied by what the documentation provides. Where the trace breaks, the interface failure becomes visible — not as a missing document, but as an assumption the documentation made about what the heir would bring to it.
Summary
A bitcoin inheritance assessment evaluates whether an inheritance arrangement produces the outcome it describes — not whether its documents are present and correctly formed, but whether the sequence those documents define can be completed by the people named under real conditions. Assessment treats the arrangement as a system, tracing the access sequence from heir's starting position through each layer to confirmed access.
The distinction from checklist review is structural. Checklists confirm component presence. Assessment examines the interfaces between components — the points where one layer of the arrangement depends on another and the dependency is either documented or assumed. Correctly documented arrangements fail system assessment when those interfaces depend on knowledge the documentation doesn't supply or conditions that have changed since the documentation was produced.
The assessment frame is useful for the professionals most likely to be present when inheritance arrangements are evaluated: attorneys confirming what an estate plan actually produces, fiduciaries understanding where their exposure begins, and families determining whether the planning they completed translates to the access they intended. In each case, the relevant question is not whether the components exist. It is whether the system they compose functions.
System Context
Walking Through Bitcoin Custody With an Executor
Cross-Domain Intersection Index
For anyone who holds Bitcoin — on an exchange, in a wallet, through a service, or in self-custody — and wants to know what happens to it if something happens to them.
Start Bitcoin Custody Stress Test$179 · 12-month access · Unlimited assessments
A structured, scenario-based diagnostic that produces reference documents for your spouse, executor, or attorney — no accounts connected, no keys shared.
Sample what the assessment produces