Somewhere in Bitcoin's ledger sit millions of coins that will never move again — not burned, not lost in hacks, but stranded: their holders died, and the keys died with them. Every estimate of permanently inaccessible bitcoin includes this quiet category, and it grows every year, because the asset's defining property — no keys, no coins, no exceptions, no appeals — makes no exception for grief. A bank account has probate processes, heir claims, institutional memory; a hardware wallet has a PIN and a silence. For holders, this converts inheritance from a legal formality into an engineering problem: how do you guarantee your heirs can access the coins after you're gone, without weakening your security while you're alive? The problem is genuinely solvable — with paper, structure, and an annual habit — and solving it is arguably the most loving thing a holder ever does with their stack. This is the complete plan.
The core tension: security versus succession
Every inheritance design negotiates one trade-off: information sufficient for heirs to recover the coins is information sufficient for anyone who obtains it to steal them. The two naive extremes both fail: total secrecy (nobody knows anything — maximum security, guaranteed stranding) and total disclosure (the seed phrase in the will or told to the family — succession solved, security demolished, and doubly wrong because wills become public documents in probate in many jurisdictions: a seed phrase in a will is a seed phrase published). Every serious plan lives between the extremes on one principle: separate the knowledge — heirs learn that coins exist and how to begin; the keys themselves stay protected behind physical security, legal structure, or cryptography until the moment of legitimate need. The designs below are all implementations of that separation, at increasing sophistication.
Design 1: The letter of instruction — the 80% solution
For most holders, the complete workable plan is a sealed letter plus secured keys plus a knowledgeable pointer, assembled in an evening: The letter (sealed, stored with your important documents or lawyer, referenced in — but never contained in — your will) says what exists and how to proceed, without containing keys: that bitcoin holdings exist and roughly their nature; where the hardware wallet and seed backup physically are (the safe, the box, the location — this is the letter's crown jewel, because heirs can't recover what they can't find); which exchanges hold accounts (platform names — heirs with a death certificate can invoke exchange inheritance processes, which exist at every major platform and work at bureaucratic speed); the identity of the technical executor (below); and the explicit instruction not to type the seed into any website or share it with any "support" — the scam-inoculation your grieving family will critically need, because inheritance scams target exactly them. The keys stay exactly as secure as your custody articles already made them — the letter changed nothing about your living security; it only made the existing security findable. The pointer — one trusted, moderately technical person (family member, friend, professional) named in the letter as the guide: not a keyholder, just the person who knows how hardware wallets work and can shepherd the recovery, chosen now and told now ("if anything happens to me, you're the person who helps my family with the technical part — here's nothing secret, just be findable"). This design's beauty is its honesty about failure modes: it protects against the dominant one (heirs unaware or unable to begin) while adding almost zero new attack surface.
Design 2: Splitting and structure — for meaningful holdings
Where the stack's size justifies engineering, the intermediate tools: geographic splitting of the seed backup — the classic 2-of-2 split (half the words in each of two locations) is fragile (lose either half, lose everything) and generally discouraged; the robust version is Shamir-style or multisig-based splitting where any 2 of 3 shares recover — tolerating the loss of one location, one person, or one disaster, and turning "the house fire" from a stranding event into an inconvenience; passphrase separation — a seed in one secured location plus its passphrase held separately (with the lawyer, in the letter's sealed companion) means neither discovery alone spends the coins: a clean knowledge-separation with one hard requirement — the passphrase must be findable by heirs, because a forgotten or over-hidden passphrase is self-stranding with extra steps; and the inheritance-specific multisig — a 2-of-3 wallet where you hold two keys in life (full control) and the third sits with a lawyer, institution, or heir: at death, your two keys (recovered via the letter's locations) plus documentation — or emerging timelock/recovery constructions that let a designated key claim funds only after a long inactivity period — provide cryptographic succession without any single point of trust. The honest note on sophistication: every added mechanism adds a way for the plan itself to fail (shares lost, passphrases forgotten, collaborating parties unavailable), which is why each design must pass the same test — could your actual heirs, with your actual letter, actually execute it? — and why the letter-of-instruction layer remains mandatory underneath every clever construction.
The legal layer: will, executor, and the tax file
The cryptography needs its paperwork: the will mentions the category, never the keys — bitcoin holdings referenced as assets with distribution wishes, the sealed letter cited as the operational guide (keeping key material out of the probate-public document); jurisdictional reality checked once — inheritance law, estate/inheritance taxes on crypto, and heirs' reporting duties vary widely (the tax article's professional hour extends naturally to one succession question: "what do my heirs owe and file when they inherit this?"), and the answer shapes whether coins are best held, gifted progressively in life (some systems tax lifetime gifts differently), or structured; the records travel with the plan — the purchase log (cost basis) filed alongside the letter, because heirs in many systems inherit basis questions along with coins, and a documented history converts their tax filing from forensic archaeology into arithmetic; and exchange accounts enumerated — with the note that custodial holdings pass through each platform's inheritance process (death certificate, probate documents, patience), a genuinely functional route that argues for keeping some holdings custodial purely for succession simplicity in households with no technical heir at all — a legitimate, conscious trade of custody principle for succession certainty.
The living plan: testing, updating, and the annual drill
Inheritance plans fail in the gap between writing and reality, and three habits close it: the dry run — once, while alive: hand the sealed letter's copy to your technical executor and ask them to narrate (not execute) the recovery — where they'd go, what they'd do, what confuses them: every confusion found now is a stranding prevented later, and the exercise takes an hour; the update trigger — the letter goes stale the day you change wallets, move the safe, switch exchanges, or restructure holdings: the rule is mechanical — any custody change updates the letter the same week, tracked as the recurring commitment it is; and the annual review — one scheduled hour: letter accurate? Locations current? Executor still willing, able, alive? Backup verified (the test-restore habit from the custody articles, now serving two masters)? Holdings' value still matching the plan's sophistication (the stack that grew tenfold may have outgrown Design 1)? Households that run the drill describe the same shift: succession stops being the morbid topic avoided at dinner and becomes one more maintained system — which is precisely the emotional victory, because plans maintained calmly are the only kind that work when calm is gone.
Frequently asked questions
My family is completely non-technical. Is there any realistic plan?
Three honest routes, combinable: the technical executor carries the entire operational burden (the family's job reduces to "open the letter, call this person" — which is why choosing and dry-running that person is the plan's heart); a deliberate custodial allocation passes through exchange inheritance processes with zero technical demands; and emerging regulated inheritance services (institutional key-holding with succession triggers) trade fees and counterparty trust for turnkey succession — evaluated with the custody articles' full skepticism, they suit exactly this household. The wrong answer is the common one: full self-custody plus no executor plus hope.
Should I just teach my spouse/children the whole setup now?
The best version of the plan, where trust and capability allow: a household member who genuinely understands the custody is a living succession plan, and the teaching process (a joint test-restore, a walked-through letter) doubles as the dry run. The cautions are the honest ones — shared knowledge is shared attack surface (the discretion rules now bind two people), and capability fades without practice (the annual drill becomes a two-person ritual). Teach where you can; letter and executor regardless, because plans that depend on one relationship share that relationship's fragility.
What about my other crypto — exchange tokens, DeFi positions, NFTs?
The same architecture with an honesty pass first: the letter should enumerate what exists and what it's worth bothering with — heirs shouldn't spend probate energy recovering dust. Complex positions (DeFi, staking, obscure chains) deserve either simplification in life (the annual review's question: "could my executor realistically recover this?") or explicit written walkthroughs, because every layer of exotic complexity multiplies stranding probability. Many holders' succession plans quietly drive a portfolio simplification — which the holders themselves usually then appreciate while alive.
Isn't all this overkill for my modest stack?
Scale the plan, never skip it: the modest stack's version is Design 1 at its lightest — one letter, one findable backup, one named helper, one yearly glance — an evening's work protecting whatever the stack becomes. The sizing logic mirrors insurance: the plan costs nearly nothing, the failure mode is total, and stacks have a documented habit of being worth more at inheritance time than at planning time. The coins that stranded weren't all fortunes when their holders last updated nothing.
Key takeaways
- Bitcoin inheritance is an engineering problem: no keys, no coins applies to heirs too, and the graveyard of stranded coins is the price of unplanned custody.
- Every plan implements one principle — separate knowledge from keys: heirs learn what exists and where to begin; seeds never enter wills (probate publishes them) or casual conversation.
- The letter of instruction is the 80% solution: existence, locations, platforms, the named technical executor, and the scam warning — sealed, referenced by the will, updated with every custody change.
- Scale the engineering to the stack — robust splitting, passphrase separation, inheritance multisig or timelocks — with every design passing one test: could your actual heirs execute it with your actual letter?
- Keep the plan alive: the executor dry run, the same-week update rule, the annual review hour with backup verification — succession as a maintained system, not a morbid someday.
The closing thought: everything this blog teaches about custody — the seeds, the steel, the discipline — protects your coins from everyone else. The inheritance plan is the one document that protects them from your own absence, and it costs an evening, a letter, and a yearly hour. The holders who write it aren't planning to die; they're refusing to let the best-secured savings of their life become the ledger's next quiet monument. Write the letter this weekend. Then go back to living — properly backed up.
How Wajib AI helps
Succession is a maintenance schedule wearing a solemn face — and maintenance is what Wajib AI automates: the annual plan-review reminder, the backup-verification check on your timeline, the letter's update flagged after every wallet change, and the holdings' value visible on the live chart so the plan's stakes stay current. The keys are cryptography; keeping the plan alive is just tracked habit.
Download Wajib AI free and keep every commitment, price, and payment in one place.