Printable templates
Ten blank templates to print and fill in by hand, for beginners through to experts. Each one says what it is for, what you must never write on it, where to keep it, the common pitfalls and what experienced people advise, with sources. There is nothing to type on this page: it has no forms or input fields and it never asks for, stores or generates a seed or key.
[EXAMPLE] or [8 characters]. They are not real wallets, people or companies. Templates are educational, not legal documents; see the note at the end.At a glance Beginner
- Print blank, write by hand, in pen. Blank templates contain nothing sensitive, so any printer will do. Once filled in, they are private papers: do not scan, photocopy or photograph them (see printing).
- Start with three: the letter of instruction, the backup inventory and the recovery drill log. Add the others as your setup grows (see which template for whom).
- Describe, never copy. "Steel plate, share 1 of 3, home safe" is fine. Any part of the words, the passphrase or a PIN is not (see safe to write vs never write).
- Keep the map apart from the treasure. An inventory or letter tells a reader where your backups are. Store it away from the backups it describes.
- Review on a schedule. Glacier Protocol suggests a maintenance check six months after setting up cold storage and then once a year (Glacier). Fidelity suggests updating a letter of instruction "even as often as annually" (Fidelity). Use the review log.
- Not legally binding. A letter of instruction or letter of wishes guides your executors but does not override your will (The Gazette, Fidelity). Ask a solicitor or attorney how to refer to it.
Safe to write vs never write Beginner
| Information | On these templates? | Why |
|---|---|---|
| Seed words, SLIP-39 shares, Seed XOR parts, codex32 shares | Never | Anyone who reads them can take the funds. In England & Wales anyone can order a copy of a will once probate is granted (UK guide). |
| Part of a seed: first letters, "every other word", hints | Never | Partial words leak most of the secret. See naive seed splitting. |
| BIP39 passphrase | Never | Write only that a passphrase exists and where its own backup is kept (setup checklist). |
| PINs, device passwords, exchange passwords, 2FA backup codes | Never | Investor.gov suggests keeping passwords and PINs on a separate list in a safe place (Investor.gov). For crypto, keep them off these sheets entirely. |
| Private keys, xprv, WIF keys | Never | Each one can spend funds on its own. |
| Dice-roll values used to create a wallet | Never | Roll sheets are as sensitive as the seed (entropy guide). The dice worksheet records only practice tallies and roll counts. |
| Wallet nicknames, device model, standard (BIP39 / SLIP-39), threshold (m-of-n) | Yes | Your executor needs these to choose the right recovery tool. |
| Master key fingerprint (8 characters) | Yes | Cannot spend. It lets you match a backup to a device or a multisig key. |
| xpubs, descriptors, first receive address | Yes, with care | Cannot spend, but reveal your addresses and balance (Multisig Setup). Keep them on the configuration record only. |
| Locations, described ("home safe, top shelf") | Yes, with care | Together they form a map. Store the inventory away from the backups. |
| Approximate value bands | Optional | Helps executors plan tax and urgency, but advertises a target. See coercion. |
| Names and contact details of your solicitor, attorney, helpers | Yes | The most useful thing for an executor. Say what each person holds or knows. |
Printing on A4 or US Letter Beginner
- Paper size: the layout has no fixed page size and uses margins of about 14–16 mm, so it fits both A4 (210 × 297 mm, the ISO 216 A series: ISO 216) and US Letter (8.5 × 11 in). Choose your paper in the print dialogue and keep the scale at 100% or "fit to page width".
- Two buttons on each template: "Print with guidance" prints the notes and the blank form; "Print blank form only" prints just the form. Each template starts on a new page when you print the whole page, and table headers repeat if a table runs over.
- Colours: dark mode is ignored when printing; everything prints black on white, and web addresses are printed after links so the paper copy still works.
- Printers keep copies. The US Federal Trade Commission warns that networked "digital copiers" have hard drives that store data about the documents they copy, print, scan, fax or email (FTC). Printing a blank template anywhere is fine. Never scan, copy or photograph a filled-in one on a shared machine, and never print a seed or wallet backup from a computer (setup checklist).
- Paper and ink: one community multisig guide prefers a laser printer for descriptor printouts that must last (Multisig Setup). Write with a pen, not pencil, and date every version.
Which template for which reader Beginner Intermediate Expert
| Template | Beginner | Intermediate | Expert | Pairs with |
|---|---|---|---|---|
| 1. Letter of instruction | Yes | Yes | Yes | Estate planning |
| 2. UK supplement | If in the UK | If in the UK | If in the UK | UK estate guide |
| 3. US supplement | If in the US | If in the US | If in the US | US estate guide |
| 4. Backup inventory & location map | Yes | Yes | Yes | Locations |
| 5. Recovery drill log | Yes | Yes | Yes | Annual review |
| 6. Hardware wallet setup log | Recommended | Yes | Yes | Setup checklist |
| 7. Multisig configuration record | — | If using multisig | Yes | Descriptors |
| 8. Periodic review log | Recommended | Yes | Yes | After an advisory |
| 9. Dice entropy worksheet | — | Optional | If using dice | Dice methods |
| 10. Executor guide | Yes | Yes | Yes | Estate planning |
1. Letter of instruction (no secrets) Beginner Intermediate
A letter of instruction is an informal document, kept with or referred to by your will, that tells your executor what digital assets exist and how the recovery plan works. It is not a legal document in itself — ask your solicitor or attorney how to reference it in your will (in the UK, ask about a "letter of wishes"; in the US, a "letter of instruction" or a memorandum referenced by your trust). Add the UK or US supplement for country-specific details.
What it is for
- Tells your executor what exists, how recovery works and who can help, in plain words
- Fidelity describes a letter of instruction as an informal letter that supplements a will or revocable trust; it is not legally binding but can make administration "much easier" (Fidelity)
- Covers the gap that law cannot fill: no court can recreate a key that nobody has (UK guide)
Never write on it
- Seed words, shares, passphrases, PINs, passwords or 2FA codes
- Anything that changes your will: Fidelity warns informal changes are not binding and may lead to disputes
- Exact balances or addresses (use bands; addresses belong on the configuration record)
Where to store it
- With your will, or where your executor will look first; The Gazette advises keeping a letter of wishes and the will together
- A copy with your solicitor or attorney (Fidelity suggests this)
- Not in the same box as the backups it describes, so one burglary or fire does not take both
Pitfalls
- Written once and never updated: devices, people and addresses change
- Too technical for the reader: test it on someone non-technical
- Contradicting the will (The Gazette: the letter must support the will)
- Relying on one person who "knows the passphrase" and may die in the same accident
Community advice
- Unchained publishes a free "Inheritance Protocol" set of documents designed so an executor can recover funds without prior technical expertise (Unchained)
- Pamela Morgan's book Cryptoasset Inheritance Planning (2018) is a widely cited plain-English guide for owners (Google Books)
- Rehearse with your executor using the drill log — without revealing any secret
Sources: Fidelity: letter of instruction · The Gazette: a letter of wishes explained · Unchained: inheritance · Morgan, Cryptoasset Inheritance Planning (2018)
Letter of instruction (no secrets) · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#letter · not legal advice.
To: ____________________ (my executor / trustee / attorney) Date: ____ / ____ / ________
From: ____________________ Will dated: ____ / ____ / ________ Held by: ____________________
This letter replaces any earlier version. ☐ UK supplement attached ☐ US supplement attached ☐ Backup inventory exists (see Part C)
Part A — What exists
| # | Asset / wallet (nickname) | Type | Approx. value band | Where the device is |
|---|---|---|---|---|
| e.g. | "Savings vault" [EXAMPLE] | Bitcoin 2-of-3 multisig | Over £50k | Home safe (device A), see inventory |
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 |
Part B — Exchange and custodial accounts
| Company | Account email / username hint | Death-claim process known? | 2FA device location |
|---|---|---|---|
| [Example Exchange Ltd] | j.smith@… (no passwords here) | Yes: bereavement form on their help site | Old phone in desk drawer |
Part C — How recovery works (in plain words)
Standard used (tick): ☐ BIP39 12/24 words ☐ BIP39 + passphrase ☐ SLIP-39 Shamir (___ of ___) ☐ Multisig (___ of ___) ☐ Seed XOR (___ parts) ☐ Collaborative custody with ____________________ ☐ Other ____________________
Where the backups are kept is described in my backup inventory, which is kept at: ______________________________________________
The passphrase (if any) is: ☐ stored separately at ____________________ ☐ known to ____________________ ☐ held by my solicitor in a sealed envelope
Wallet configuration / descriptor backup (for multisig) is kept at: ______________________________________________
Software to use for recovery: ____________________ (download only from the official site: ____________________)
Part D — People who can help
| Name | Role | Contact | What they hold / know |
|---|---|---|---|
| [A. Example] | Technically minded friend | Phone | Knows the setup; holds nothing |
Part E — My wishes and warnings
_______________________________________________________________________________________
_______________________________________________________________________________________
Warnings for my executor: Nobody legitimate will ever ask you for the recovery words. Do not type them into any website, app, email or chat. Do not let anyone "recover" funds for a percentage. Read the executor guide first.
Part F — Where my other papers are
Will / trust: ____________________ Power of attorney: ____________________ Tax and cost-basis records: ____________________ Recovery drill and review logs: ____________________
Signed: ____________________ Next review date: ____ / ____ / ________
2. UK supplement to the letter of instruction Beginner Intermediate
Adds the UK-specific facts your executor and attorneys need: which of the three UK legal systems applies, where the will and power of attorney are, and pointers for Inheritance Tax. Read the UK estate guide first; every point below is explained and sourced there.
What it is for
- Links your crypto plan to your UK legal documents: will, letter of wishes and power of attorney
- Reminds executors that HMRC asks about cryptoassets on the IHT400 and wants sterling values at the date of death (HMRC's view)
- Gives attorneys guidance outside the LPA: MoneyHelper says you can write a letter of wishes to give attorneys extra instructions; it is not legally binding (MoneyHelper)
Never write on it
Where to store it
- With your letter of instruction and letter of wishes
- In England & Wales the original will can be lodged with HMCTS for a one-off £24 fee; you receive a lodgement certificate after about two weeks (GOV.UK)
- MoneyHelper suggests keeping the power of attorney at home, with someone you trust or with your solicitor, and telling attorneys where it is
Pitfalls
- Using an England & Wales template in Scotland: wills, powers of attorney and "confirmation" differ (three systems)
- Forgetting to review after marriage, civil partnership, divorce or a move (UK checklist)
- No record of lifetime gifts, so executors cannot apply the 7-year rule (7-year rule)
Community advice
- Age UK notes a letter of wishes can be lost or separated from the will; name it in the will and keep them together (Age UK)
- The Gazette suggests reviewing a letter of wishes and will regularly, for example every two years
- MoneyHelper suggests checking a power of attorney every few years or after big life changes
Sources: The Gazette · MoneyHelper: power of attorney · Age UK: making a will (PDF) · GOV.UK: store a will with HMCTS · GOV.UK: power of attorney · GOV.UK: IHT400 · HMRC CRYPTO25000
UK supplement to the letter of instruction · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#letter-uk · not legal advice.
Attach to my letter of instruction dated ____ / ____ / ________. Jurisdiction of my will: ☐ England & Wales ☐ Scotland ☐ Northern Ireland
Part A — Will and letter of wishes
Will dated ____ / ____ / ________ Original held by: ☐ solicitor ____________________ ☐ HMCTS will storage (England & Wales; lodgement certificate kept at ____________________) ☐ other ____________________
Executors named in the will: ______________________________________________ ☐ Will gives executors power to deal with cryptoassets and hire technical help
Letter of wishes: ☐ yes, kept at ____________________ ☐ no Last reviewed: ____ / ____ / ________ ☐ Reviewed after marriage, civil partnership, divorce or a move
Part B — If I lose capacity
☐ Lasting power of attorney for property and financial affairs (England & Wales), registered with the Office of the Public Guardian on ____ / ____ / ________
☐ Continuing power of attorney (Scotland), registered with the OPG (Scotland) ☐ Enduring power of attorney (Northern Ireland)
Attorneys: ______________________________________________ Original / certified copies kept at: ____________________
☐ Attorneys know this letter exists ☐ Crypto instructions for attorneys are in a separate letter of wishes (not in the LPA wording itself)
Part C — Pointers for executors (tax)
☐ This estate holds cryptoassets: form IHT400 asks about them ☐ Value each token in pounds sterling at the date of death; note the price source and time
Records of acquisition costs and disposals are at: ____________________ Record of lifetime gifts (for the 7-year rule) is at: ____________________
☐ HMRC's CRYPTO25000 checklist for finding crypto has been read ☐ Any crypto that cannot be accessed must still be explained to HMRC
Part D — Professional contacts
| Role | Name / firm | Contact | Knows about crypto plan? |
|---|---|---|---|
| Solicitor (Scottish solicitor in Scotland) | ☐ Yes ☐ No | ||
| Tax adviser / accountant | ☐ Yes ☐ No | ||
| Technical helper | ☐ Yes ☐ No | ||
| Collaborative custody / inheritance provider | ☐ Yes ☐ No |
For executors: exchanges usually ask for a death certificate and the grant of probate (confirmation in Scotland) before releasing an account. See the UK guide's executor timeline. Signed: ____________________
3. US supplement to the letter of instruction Beginner Intermediate
Adds the US-specific facts: state, will and revocable trust, durable power of attorney, RUFADAA designations at exchanges and tax pointers. Read the US estate guide first; every point below is explained and sourced there.
What it is for
- Connects your crypto plan to your will, trust and durable power of attorney
- Reminds the executor about date-of-death values for the step-up in basis and the Form 706 / 1041 points
- Records RUFADAA "online tool" choices, which take priority over your will for custodial accounts (RUFADAA)
- Exchanges typically ask an executor for the death certificate and letters testamentary (US timeline)
Never write on it
- Seed words, passphrases, PINs or exchange passwords
- Changes to who inherits: Fidelity warns a letter of instruction should not contradict or informally change your estate plan
Where to store it
- With your estate planning documents, with a copy for your attorney (Fidelity)
- Investor.gov suggests storing important documents in a safe, easily accessible place and telling trusted people where they are
Pitfalls
- Assuming RUFADAA lets an executor obtain a self-custody seed: it governs custodians only (US guide)
- Relying on a separate list of personal items: Fidelity notes such lists are for tangible personal property, so do not rely on one to pass crypto — ask your attorney
- Forgetting a durable power of attorney: incapacity is often harder than death (US guide)
Community advice
- Give your agent or successor trustee the CFPB's free "Managing someone else's money" guide for their role (CFPB)
- Name a "trusted contact person" at brokerages and other providers where offered; Investor.gov notes trusted contacts cannot access your money
- Check whether your state has enacted RUFADAA (ULC legislative report)
Sources: Fidelity: letter of instruction · Investor.gov / CFPB: planning for diminished capacity · CFPB: managing someone else's money · ULC: RUFADAA by state · IRS: Instructions for Form 706
US supplement to the letter of instruction · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#letter-us · not legal advice.
Attach to my letter of instruction dated ____ / ____ / ________. Signed: ____________________ State of residence: ______________ Other states where I own property: ______________
Part A — Will and trust
Will dated ____ / ____ / ________ Original held by: ____________________ Executor / personal representative: ____________________
☐ Revocable living trust: name ____________________ dated ____ / ____ / ________ Successor trustee: ____________________ ☐ Crypto held in the trust's name
☐ Will / trust includes digital-asset (RUFADAA) authority ☐ Trust gives power to retain crypto without diversifying (ask attorney)
Part B — If I am incapacitated
☐ Durable financial power of attorney dated ____ / ____ / ________ Agent: ____________________ ☐ Includes digital-asset authority
☐ Health care power of attorney (separate document) Originals kept at: ____________________
Part C — Custodial accounts
| Exchange / custodian | Online-tool designation made? (RUFADAA tier 1) | Beneficiary feature offered? | Trusted contact named? |
|---|---|---|---|
| [Example Exchange Inc.] | ☐ Yes ☐ Not offered | ☐ Yes ☐ No | ☐ Yes ☐ No |
Part D — Pointers for the executor (tax)
☐ Record each asset's fair market value at the date of death, with source and time stamp (stepped-up basis) ☐ Form 706 may be needed; digital assets go on Schedule F
☐ Estate files Form 1041 if gross income is $600 or more ☐ State estate / inheritance tax checked ☐ Community property state: ☐ yes ☐ no
Cost-basis records and exchange exports are at: ______________________________________________
Part E — Professional contacts
| Role | Name / firm | Contact | Knows about crypto plan? |
|---|---|---|---|
| Estate attorney | ☐ Yes ☐ No | ||
| CPA / tax preparer | ☐ Yes ☐ No | ||
| Technical helper, trust company or custody provider | ☐ Yes ☐ No |
4. Backup inventory and location map Beginner Intermediate
Lists every physical item in your setup and where it lives, so you can check nothing has gone missing and your executor can find everything. Part B maps sites to items, so you can see at a glance whether one fire or one burglary could defeat the plan. Describe items; never copy their contents.
What it is for
- Spot a missing or tampered backup early (Glacier's maintenance step checks each packet is where expected, in good condition, with seals intact)
- Show that no single site can recover the funds alone, and that one disaster cannot destroy everything
- Tell your executor what to collect
Never write on it
- What is written on any plate, card or share
- Safe combinations, PINs, alarm codes or key-safe numbers
- Which word positions are on which share or plate
Where to store it
- Away from the backups it describes: it is a treasure map
- A copy with your letter of instruction, or with your solicitor or attorney in a sealed envelope
- Glacier advises not to keep more than one key packet in long-term storage in the same building
Pitfalls
- Out of date after a move, a new safe or a new wallet
- Vague descriptions ("the usual place") that only you understand
- Keeping the inventory in the same safe as the backups, so a thief gets the map and the treasure together
Community advice
- Seal each backup in a numbered tamper-evident bag and record the serial; Lopp also suggests signing the bag (maintenance)
- Glacier's protocol uses tamper-resistant seals on each envelope and inspects them during maintenance
- Use item IDs (B1, D1, S1) everywhere else so other papers never need to describe the backups again
Sources: Glacier Protocol document (PDF) · Glacier: maintenance · Lopp: how to back up a seed phrase · Physical storage: locations
Backup inventory and location map · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#inventory · not legal advice.
Part A — Items
| Item ID | What it is | Wallet it belongs to | Location (described) | Tamper-bag serial | Last checked |
|---|---|---|---|---|---|
| B1 | Steel plate, SLIP-39 share 1 of 3 | "Savings vault" [EXAMPLE] | Home safe, top shelf | EX-000001 | 01/2026 |
| B2 | Steel plate, share 2 of 3 | "Savings vault" [EXAMPLE] | Relative's house (sealed bag) | EX-000002 | 01/2026 |
| D1 | Hardware wallet (PIN known to me only) | "Savings vault" [EXAMPLE] | Desk drawer | — | 01/2026 |
Part B — Location map
| Site | Described location | Who can get in | Item IDs held | Enough to recover alone? | Fire / flood notes |
|---|---|---|---|---|---|
| S1 | Home safe [EXAMPLE] | Me, spouse | B1, D1 | No (1 of 3 shares) | Fire-rated safe, upstairs |
| S2 | Relative's house, other town [EXAMPLE] | Relative | B2 | No | Different postcode |
Check: ☐ No single site holds enough items to recover alone (unless intended) ☐ Passphrase stored apart from seed ☐ Descriptor copies stored with each multisig key ☐ Two sites are not in the same building ☐ Inventory itself stored apart from the backups ☐ Old versions destroyed
5. Recovery drill and test-restore log Beginner Intermediate Expert
A backup you have never restored is a hope, not a backup. Test when you first set up, after any change, before firmware updates and about once a year. The safest beginner test is the device's own "check backup" mode; a stronger test restores onto a wiped or spare device and checks the wallet fingerprint or first receive address against your records. Part C lets your executor rehearse finding things without seeing any secret.
What it is for
- Proves each backup is complete, legible and in the right order
- Trezor recommends checking the backup before wiping the device and before every firmware update; the device compares the words you enter with its stored backup without remembering them (Trezor)
- Ledger's Recovery Check app does the same for Ledger devices (Ledger)
Never write on it
- Any word, even one you got wrong — fix the backup instead
- The passphrase or PIN
- Photos or notes made "to help next time"
Where to store it
- With the inventory, apart from the backups
- A copy for your executor shows that the plan has been tested
Pitfalls
- Ledger's Recovery Check cannot verify a passphrase; test passphrase wallets with a full restore (Ledger)
- If a Trezor check fails and you cannot enter the correct backup, Trezor says to move funds to a new wallet with a new backup as soon as possible (Trezor troubleshooting)
- Typing words into a computer "just to check" — never do this
- Testing the device but never the multisig descriptor
Community advice
- On a Trezor Safe 7 you can take the device to each share's location and check a multi-share backup in stages, without a computer (Trezor Safe 7)
- Glacier includes a small test withdrawal in its annual maintenance (Glacier)
- Rehearse the human side too: can your executor find the letter, the inventory and the helper?
Sources: Trezor: check backup (Safe 3) · Trezor: check backup (Safe 7) · Trezor: troubleshooting backups · Ledger: Recovery Check · Glacier: maintenance
Recovery drill and test-restore log · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#testlog · not legal advice.
Part A — Drill steps (tick as you go)
☐ Private room; phones, cameras and smart speakers away ☐ Method: ☐ device "check backup" (dry run) ☐ full restore on a wiped spare device ☐ multisig rebuild from descriptor + quorum
☐ Words entered only on the hardware device, never on a computer or phone ☐ Fingerprint or first receive address matches my records ☐ Passphrase tested separately (if used)
☐ Spare device wiped afterwards ☐ Backups re-sealed; new bag serials copied to the inventory ☐ Next drill booked for ____ / ____ / ________
Part B — Log
| Date | Wallet | Type of check | Backup items used | Device used | Fingerprint / first address matched? | Passphrase tested? | Issues found / fixed | Initials |
|---|---|---|---|---|---|---|---|---|
| 01/2026 | "Savings vault" [EXAMPLE] | Full restore | B1 + B2 | Spare device, wiped after | ☑ Yes (fingerprint [8 characters]) | n/a | Plate B2 hard to read; re-punched | JS |
Part C — Executor or heir rehearsal (no secret revealed)
| Date | Who | What they practised | Gaps found | Fixed by (date) |
|---|---|---|---|---|
| 03/2026 | Executor [EXAMPLE] | Found the letter and inventory; phoned the helper; read the executor guide | Did not know where the safe key is | Letter Part F updated, 04/2026 |
6. Hardware wallet setup and verification log Beginner Intermediate
One sheet per device. It records where the device came from, which checks it passed, which firmware it ran and when, so that when an advisory is published you can tell in minutes whether you are affected. It follows the site's setup and verification checklist.
What it is for
- Evidence that the device was genuine and set up safely
- A firmware history to compare against advisories
- Lets an executor know which device belongs to which wallet (by fingerprint)
Never write on it
- PIN, passphrase, seed words or "PIN hints"
- Account passwords for the maker's shop or app
Where to store it
- With the inventory, not in the device box: a thief who takes the device should not also learn that a passphrase exists or where its backup is
Pitfalls
- Ticking "seed created on device" for a device that arrived with words already printed — that device must not be used (supply chain)
- Not recording firmware updates, so an advisory cannot be checked quickly
- Updating firmware without first checking the backup
Community advice
- Buy from the maker or a listed reseller, and run the authenticity check in the official app (Trezor; Ledger)
- Trezor says to check the backup before every firmware update (Trezor)
- Read the release notes before updating; keep the backup to hand but never type it into the computer (setup checklist)
Sources: Trezor: where to buy · Trezor: firmware authenticity check · Ledger: genuine check · Trezor: download and verify Suite · Trezor: check backup
Hardware wallet setup and verification log · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#hwlog · not legal advice.
Part A — The device
Item ID (from inventory): ______ Make and model: ____________________ Nickname / label on device: ____________________
Bought from: ☐ maker's own shop ☐ authorised reseller ____________________ Order date: ____ / ____ / ________ Order reference: ____________________
☐ Packaging inspected (but not relied on) ☐ No pre-printed or pre-filled recovery card in the box ☐ Device was not already set up
Part B — Verification at setup
☐ Companion app downloaded from the maker's official site and verified where the maker explains how ☐ Authenticity / genuine check passed on ____ / ____ / ________
Firmware version at setup: __________ Seed created: ☐ on the device ☐ with dice on the device (see dice worksheet) ☐ Entropy check shown by the app (where offered)
Backup type: ☐ BIP39 12 ☐ BIP39 24 ☐ SLIP-39 single share ☐ SLIP-39 ___ of ___ Backup item IDs: ____________________
☐ Word confirmation on the device passed ☐ "Check backup" passed on ____ / ____ / ________ ☐ Passphrase in use (the passphrase itself is not recorded here; its backup is item ______)
Master key fingerprint: [ __ __ __ __ __ __ __ __ ] (8 characters, public) ☐ First receive address checked on the device screen
☐ Small test deposit received ☐ Restore test done (see drill log) ☐ PIN set and remembered (never written here) ☐ I know how many wrong PINs wipe the device
Part C — Firmware and advisory history
| Date | Firmware / app version | Installed via official app? | Backup checked before update? | Advisory reference (if any) | Initials |
|---|---|---|---|---|---|
| 02/2026 | [x.y.z] [EXAMPLE] | ☑ Yes | ☑ Yes | — | JS |
7. Multisig and wallet configuration record Intermediate Expert
In multisig, the seeds alone are not enough: you also need the wallet's configuration (the output descriptor), which lists every public key, derivation path and the script. This record lists the keys by fingerprint and where each piece lives, and is designed to have the printed descriptor attached rather than copied by hand. See descriptors and single points of failure.
What it is for
- Rebuild the wallet when a key is lost — the very case multisig is for. Without the descriptor, two seeds may not be enough to find your coins (Multisig Setup)
- Lets each signing device verify it is part of the right wallet (BIP-129 records include the first address for checking; BIP-388 wallet policies can be registered on devices)
Never write on it
- Seed words, xprv / private keys or passphrases
- Hand-copied xpubs: attach the printed descriptor instead, because one wrong character breaks it
Where to store it
- A copy with every key backup, so any quorum of sites can recover (Multisig Setup; descriptors)
- It cannot spend, but it reveals your addresses and balances — treat it as private, not secret
Pitfalls
- Keeping the only copy in the wallet file on a laptop; hiding a single copy "very well"; not updating backups after creating a second wallet (all listed as common mistakes by Multisig Setup)
- Using one device maker for every key, so one flaw affects all (multisig across vendors)
Community advice
- Sparrow can save the descriptor as a PDF with text and QR code; print one per location (Multisig Setup)
- Write on each printout which device letter matches which master fingerprint (Multisig Setup)
- For collaborative custody, keep your own copy of the configuration even if the provider holds one (collaborative custody)
Sources: Multisig Setup: back up the wallet configuration · BIP-129 (BSMS) · BIP-380 descriptors · BIP-388 wallet policies
Multisig and wallet configuration record · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#msconfig · not legal advice.
Part A — The wallet
Wallet nickname: ____________________ Quorum: ___ of ___ Created: ____ / ____ / ________ Coordinator software and version: ____________________
Script type: ☐ native SegWit multisig (P2WSH) ☐ nested SegWit (P2SH-P2WSH) ☐ Taproot / miniscript policy ☐ other ____________ ☐ Timelock / decaying quorum? Details on the attached printout
☐ Descriptor printed (text and QR) and attached to this sheet ☐ BSMS record (BIP-129) kept ☐ Wallet policy registered on each signing device (BIP-388, where supported)
Part B — Keys
| Key | Device make / model | Master fingerprint | Derivation path | Seed backup item ID | Descriptor copy with it? | Site | Held by |
|---|---|---|---|---|---|---|---|
| A | [Maker 1] [EXAMPLE] | [8 characters] | m/48'/0'/0'/2' | B1 | ☑ Yes | S1 | Me |
| B | [Maker 2] [EXAMPLE] | [8 characters] | m/48'/0'/0'/2' | B2 | ☑ Yes | S2 | Relative |
Part C — Checks
☐ First receive address shown identically on every signing device and the coordinator (date ____ / ____ / ________) ☐ Recovery tested from descriptor + quorum of seeds (see drill log)
Number of descriptor copies: ___ Stored at sites: ____________________ ☐ Provider recovery path documented (collaborative custody: which keys I hold, how to recover without the provider)
8. Periodic review log Beginner Intermediate Expert
Plans decay quietly: people move, devices age, advisories appear and laws change. This log turns the annual review checklist into a written record, with a separate table for security advisories (see after an advisory).
What it is for
- A routine: Glacier suggests maintenance six months after the first deposit and then annually — checking balances, security updates, the condition and seals of each packet, and a small test withdrawal (Glacier)
- A record that executors and auditors can follow
Never write on it
- Secrets of any kind
- Details of which word on which plate was damaged
Where to store it
- With the inventory and the drill log
Pitfalls
- Reviewing the paperwork but never inspecting the backups
- Missing an advisory because nobody checks the maker's security page
- Letting the will or power of attorney fall out of step with the crypto plan
Community advice
- Fidelity suggests updating a letter of instruction even as often as annually; The Gazette suggests reviewing a letter of wishes and will about every two years; MoneyHelper suggests checking a power of attorney every few years or after big life changes
- Set a reminder you trust; Glacier ends its maintenance protocol by creating a reminder for the next one
Sources: Glacier: maintenance · Fidelity · The Gazette · MoneyHelper
Periodic review log · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#reviewlog · not legal advice.
Part A — Schedule and triggers
Next routine review: ____ / ____ / ________ Reminder set in: ____________________
Review early if: ☐ moving house ☐ marriage, civil partnership or divorce ☐ birth or death in the family ☐ new wallet or device ☐ security advisory ☐ executor, attorney or helper changes ☐ change in the law ☐ large change in value
Part B — Review log
| Date | Trigger | Items inspected; seals intact? | Drill done? | Firmware / advisories checked? | Letter and inventory updated? | Will / POA still current? | Actions and due date | Initials |
|---|---|---|---|---|---|---|---|---|
| 01/2026 | Annual [EXAMPLE] | B1, B2 ☑ intact | ☑ | ☑ | ☑ | ☑ | Replace S2 bag by 02/2026 | JS |
Part C — Advisory record
| Date read | Maker and advisory reference | Affects my model / firmware? | Action taken (update, move funds, none needed) | Date done |
|---|---|---|---|---|
9. Dice entropy worksheet (offline, paper only) Intermediate Expert
For people who add their own dice entropy on an offline signing device ("dice in, device computes"). It helps you test a die's fairness with a practice session, count rolls without writing them down and follow a safe session routine. Read dice methods, dice quality and bias and verifying a device first.
What it is for
- Plan and run a dice session without ever writing the rolls down
- Test a die with the chi-squared goodness-of-fit method described in the NIST/SEMATECH e-Handbook
- Confirm you rolled at least the documented minimum: 50 d6 rolls for 12 words and 99 for 24 words (COLDCARD and SeedSigner, which hash the rolls)
Never write on it
- The value of any roll used for a real wallet, or the resulting words or hash
- Anything typed from this sheet into a computer
Where to store it
- Part A (practice tallies) is not sensitive
- Parts B and C hold only counts and ticks; destroy the sheet if anything else was written on it by mistake
Pitfalls
- Reusing practice rolls for a real seed
- Writing rolls down "to check later" — the sheet becomes as sensitive as the seed (entropy guide)
- Reading dice in a convenient order: Glacier warns people may subconsciously record lower numbers first, which can drastically reduce randomness (Glacier)
- Too few rolls with a biased die
Community advice
- Roll more than the minimum, for example 99 rolls even for 12 words (entropy guide)
- Casino dice are a common recommendation, but technique matters as much
- Prove the device's maths only with throwaway rolls, then start again with fresh, unrecorded rolls (COLDCARD; SeedSigner; Krux)
Sources: NIST/SEMATECH: chi-square goodness-of-fit · NIST: chi-square critical values · COLDCARD: verifying dice roll math · SeedSigner: dice verification · Krux: entropy · Keystone: dice roll · Glacier: generating entropy
Dice entropy worksheet (offline, paper only) · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#dice · not legal advice.
Part A — Dice fairness practice (separate session; never reuse these rolls)
Die description: ____________________ ☐ casino / precision ☐ ordinary Number of practice rolls N = ________ Expected count per face E = N ÷ 6 = ________
| Face | Tally marks | Count O | O − E | (O − E)² ÷ E |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 | ||||
| 6 | ||||
| Chi-squared total (add the last column) | ||||
With 6 faces there are 5 degrees of freedom. A total above 11.07 would be flagged as uneven at the 5% level (NIST table). A pass shows only that the faces look even in this sample; a short test proves little, and it says nothing about whether a sequence is unpredictable.
Part B — Real generation session (counts only)
Signing device: ☐ COLDCARD ☐ SeedSigner ☐ Krux ☐ Keystone ☐ other ____________ Target: ☐ 12 words (at least 50 d6 rolls) ☐ 24 words (at least 99 d6 rolls) I plan to roll: ______
Tick one box for every 10 rolls entered on the device: ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ (12 boxes = 120 rolls)
Part C — Session checks
☐ Device offline / air-gapped ☐ No phones, cameras or smart speakers in the room ☐ Dice shaken in a cup and thrown against a backstop ☐ Read in a fixed order (for example left to right) ☐ Rule for cocked dice decided in advance
☐ Rolls entered directly on the device; no scratch paper ☐ If any scratch paper was used, destroyed by burning or cross-cut shredding after the backup was checked ☐ Any verification of the device's maths done earlier with throwaway rolls, and that wallet never funded
☐ Backup written, confirmed on the device and checked (see drill log) Date: ____ / ____ / ________ Device item ID: ______
10. Explain-to-your-executor guide Beginner
Print this for the person who will deal with your estate. It is written for someone with no crypto knowledge and contains no blanks for anything secret.
What it is for
- A plain-English briefing an executor can read in five minutes
- Explains the two rules that prevent most losses: secure everything, and never type or share the words
Never write on it
- Nothing secret: the only blanks are contact names
Where to store it
- With the letter of instruction, and a copy given to the executor now
Pitfalls
- Executors acting alone and in a hurry; scammers often contact bereaved families (scams)
- Moving funds before having legal authority (US timeline; UK timeline)
Community advice
- In the US, the CFPB publishes free guides for people acting under a power of attorney or as trustees (CFPB)
- Unchained's Inheritance Protocol is designed so executors can act without prior bitcoin expertise (Unchained)
Sources: CFPB: managing someone else's money · Unchained: inheritance · Estate planning overview
Explain-to-your-executor guide · Version date: ____ / ____ / ________ · Never write seed words, shares, passphrases, PINs, passwords or private keys on this sheet. Seed Phrase Field Guide, templates.html#executor · not legal advice.
What you are dealing with
Cryptocurrency is not held by a bank. It is controlled by secret information — usually a list of 12 to 24 words (a "recovery phrase") or several separate parts. Whoever has that information can move the money, permanently, with no way to reverse it. Your job is to keep that information safe and use it only in the way described in the letter of instruction.
Do
- Secure everything first. Collect the devices, papers and metal plates listed in the inventory and lock them away. Do not show them to anyone.
- Read the letter of instruction and find out which method was used (single phrase, passphrase, Shamir shares, multisig or a company service).
- Get professional help from the solicitor/attorney handling the estate. If the plan names a technical helper or a company (e.g. a collaborative-custody provider), contact them through their official website, not through links in emails.
- Value the holdings at the date of death for tax purposes. A helper can do this from public addresses without moving anything; keep screenshots and dates.
- Recover only on a proper device, following the plan, ideally with a second trusted person present. Move funds to accounts in the beneficiaries' or estate's name as advised by the professional.
- Keep a written record of every step for the estate accounts.
Never
- Never type the recovery words into a website, an app on a phone or computer, an email or a chat.
- Never photograph or scan them.
- Never give them to anyone who contacts you offering help — including people claiming to be from a wallet company, an exchange, the police or a "recovery service". These are scams.
- Never pay anyone a percentage to "unlock" or "recover" funds.
- Never rush. Nothing expires quickly, except certain timelock plans, which the letter will mention.
Where it differs by country
Probate, tax and who may act differ by country — see the UK guide, the US guide and other countries. In the UK, HMRC treats crypto as property for inheritance tax; in the US, inherited crypto usually gets a stepped-up basis. Your professional adviser will confirm; any attached UK or US supplement lists documents and contacts.
Helpful contacts: Solicitor/attorney _______________ Technical helper _______________ Provider _______________
Checklists by level Beginner Intermediate Expert
The templates record your setup; the checklist page walks you through building and maintaining it. Each list prints cleanly and its ticks are kept only in your own browser.
| Checklist | Level | Pairs with template |
|---|---|---|
| Beginner checklist | Beginner | Letter, inventory, drill log |
| Intermediate checklist | Intermediate | Setup log, review log, UK / US supplement |
| Expert checklist | Expert | Configuration record, dice worksheet |
| New device setup | Beginner Intermediate | Setup log |
| Annual review | All levels | Review log, drill log |
| After a security advisory | All levels | Advisory record, firmware history |
| Inheritance and incapacity | All levels | Letter, executor guide |
Pitfalls that apply to every template Beginner Intermediate
| Pitfall | What goes wrong | What to do instead |
|---|---|---|
| A "secret" sneaks on to the page | The page becomes a backup that is less protected than your real backups | Re-read the never-write list before you sign each sheet; if in doubt, leave it out |
| Filling in on a computer | Copies end up in files, cloud sync, print queues or copier hard drives (FTC) | Print blank, fill in by hand |
| Map stored with the treasure | One burglary yields both the inventory and the backups | Keep the inventory and letter at a different site |
| Old versions in circulation | Executors follow out-of-date instructions | Date every version, say "replaces earlier versions", and destroy old copies |
| Contradicting the will | Disputes; the letter is not legally binding (The Gazette; Fidelity) | Ask your solicitor or attorney to check the letter against the will |
| Written for yourself, not the reader | Your executor cannot follow abbreviations and in-jokes | Test it on someone non-technical (Part C of the drill log) |
| Never reviewed | Devices, people and law change; Glacier's maintenance protocol exists because keys get lost and tools go obsolete | Use the review log and a reminder |
Sources: FTC: digital copier data security · The Gazette · Fidelity · Glacier: maintenance
What experienced people agree and disagree on Intermediate Expert
| Question | Broad agreement | Where views differ |
|---|---|---|
| Should family know the plan exists? | Yes: an unknown plan is no plan (principles) | How much detail to share while you are alive; some providers now let heirs be involved in advance (Unchained) |
| Should the letter name exact locations? | It must be enough for the executor to find everything | Options include keeping exact locations only in the inventory and the letter general, or lodging the whole pack sealed with a solicitor; each trades privacy against ease of finding |
| Should the descriptor be treated as secret? | It cannot spend funds | Multisig Setup encourages many copies, including encrypted digital ones; Unchained does not recommend that most of its clients keep the configuration file long term, although it is needed to recover without Unchained (collaborative custody) |
| How often to test? | At setup, before firmware updates (Trezor) and after any change | A small test withdrawal every year (Glacier) versus lighter device checks in between; how often to do a full restore |
| Add dice to device entropy? | Only offline, entered directly on the device | Whether the extra steps are worth it for beginners (methods compared) |
Sources: Unchained · Multisig Setup · Trezor · Glacier
Sources for this page
- Letters of instruction and wishes: Fidelity: letter of instruction · The Gazette: a letter of wishes explained · Age UK: making a will (PDF) · MoneyHelper: power of attorney · Morgan, Cryptoasset Inheritance Planning · Unchained: inheritance
- UK and US documents: GOV.UK: store a will with HMCTS · GOV.UK: power of attorney · GOV.UK: IHT400 · HMRC CRYPTO25000 · Investor.gov / CFPB: planning for diminished capacity · CFPB: managing someone else's money · ULC: RUFADAA by state · IRS: Form 706 instructions
- Testing and maintenance: Trezor: check backup (Safe 3) · Trezor: check backup (Safe 7) · Trezor: troubleshooting backups · Ledger: Recovery Check · Glacier: maintenance · Glacier Protocol (PDF)
- Devices and multisig: Trezor: where to buy · Trezor: authenticity check · Ledger: genuine check · Multisig Setup: wallet configuration · BIP-129 · BIP-380 · BIP-388
- Dice and statistics: NIST: chi-square test · NIST: chi-square critical values · COLDCARD: dice maths · SeedSigner: dice verification · Krux: entropy · Glacier: entropy
- Printing: FTC: digital copier data security · ISO 216 paper sizes · Lopp: how to back up a seed phrase
Last reviewed: · Educational information only — verify current details with official sources.