Actuator
← Back to Guides

Crypto Inheritance — a Plan Your Heirs Can Execute

beginner~4 min read

Self-custody’s greatest strength is its estate-planning nightmare: no company can recover your keys — including for your family, after you’re gone. Exchanges have death-certificate processes; wallets have mathematics. Every year, real fortunes are permanently lost not to thieves but to grief plus a missing plan. This guide is the plan — and it’s universal: nothing here depends on any particular token, chain, or protocol.

What Never to Do

  • Never put a seed phrase in a will. In many jurisdictions a will becomes a public court record during probate — and even where it doesn’t, it passes through hands you don’t control. Either way, you’d be writing your master key into a document built to be read by others.
  • Never pre-share the seed with heirs “just in case.” Now their security is your security: their phone photos, their cloud notes, their password habits. A seed known by two people has double the attack surface and none of the accountability.
  • Never rely on “they’ll figure it out.” They won’t. A hardware wallet in a drawer is a riddle; grieving people don’t solve riddles — they hire “recovery services,” half of which are scams aimed exactly at them.

The Letter-of-Instruction Pattern

The core design: instructions that are worthless to a thief but sufficient for an heir.

  1. Write a sealed letter that explains — in plain language for a non-crypto reader — what exists (types of assets, not amounts), where the metal backup lives (location description, not the words on it), what device is involved, and who to ask for competent help (a named, vetted person or firm — not “Google it”).
  2. The letter contains no secrets. Anyone reading it learns there is a backup and where to look with lawful access — which an executor has and a burglar doesn’t. The seed itself never appears in any document.
  3. Store it with your estate documents — the lawyer’s copy, the safe copy. Update it when locations change; date every revision.

Stronger: Shamir Shares Across Heirs

If your hardware wallet supports Shamir backup (SLIP-39), split the recovery into shares — say 2-of-3: one to the heir, one to the lawyer or executor, one in the safe. No single person or burglary can reconstruct the wallet, and no single loss destroys it. Two shares only ever meet at the moment of legitimate recovery. Keep the scheme executable: the letter of instruction explains which shares exist, where, and how many are needed — because a Shamir setup nobody understands is just a more elaborate way to lose everything.

Locked Positions Need Their Own Paragraph

Staked and time-locked assets (HEX stakes, delegated HSIs, HTTs with future maturities, vault deposits) don’t move on demand — they have end dates, grace windows, and penalty rules. The letter should say so in one honest line: “Some assets unlock on future dates; do not rush, do not pay anyone who promises early access, and consult the named helper before touching anything.” Rushed heirs plus lockups is exactly the scenario penalty rules punish.

The Practice Run

A plan that’s never been rehearsed is a hope. Once: walk your intended heir (or the named helper) through recovering a test wallet with a few dollars on it, from a spare seed, start to finish. An hour of mild awkwardness converts your entire plan from theory to muscle memory — and surfaces every wrong assumption while you’re alive to fix it.

Keep It Current

Reread the letter yearly (tax season pairs well — see record-keeping). The letter has a living sibling: the personal runbook you keep for yourself — same no-secrets design, built in the backup guide. Locations change, holdings change, helpers move away, wallets get migrated. An outdated plan can be worse than none — it sends people confidently to the wrong place.


Everything on this page is universal — send anyone the link — pointing people to the source beats forwarding copies (a file passed around is exactly what this site warns about; the address stays canonical and current). For the curious: this site documents Actuator.Finance on PulseChain — the one-page version is How It Works, and Start Here picks your path.

Suggest or Correct

Spotted an error? Have an idea? Found something missing? Let us know — this site is community-built and your input matters.

⚠ Never share your seed phrase or personal information.