Part V · Protecting the Key Chapter 12

The Operational Checklist

▶ The Story

Everything in this book now cashes out into practice. You know what the twelve words are (Chapter 11), what they cost a thief when they are made fairly (Chapter 8), and exactly how they die when they are not (Chapters 9 and 10). What remains is the smallest chapter and the one you will actually use: the checklist. Short, because the principles did the work; absolute, because the case files show what happens to "mostly right."

12.1Generation

Generate on a hardware wallet from a reputable vendor, or with audited open-source software on a machine that is offline. Never on a website. Never in a browser tab.
Let the device draw from the well (Chapter 6). Do not supply your own "random" anything.
The paranoid option, worth it for serious amounts: dice. About a hundred rolls for a full 256-bit draw — fifty suffice for a 12-word phrase (Chapter 6) — entered into open-source tooling, offline. Physics you can watch.
Never generate on a clock: no "quick wallet" made in a hurry on someone else's machine.

12.2Storage

Write the twelve (or twenty-four) words on paper — or better, steel — by hand, in order, numbered. Checksums only work if the order survives (Chapter 11).
No photos. No cloud notes. No password manager, no email, no screenshots. Any networked copy of the phrase is a copy an attacker eventually reads.
Two copies, in two physically separate places, protected from fire and water. One flood should not be able to take your coins.
Never type the phrase into any device except the wallet itself during recovery. No "verification" website, no support agent, no form. Anyone who asks for the words is stealing them.

12.3Testing and Use

Before funding: restore the phrase on a fresh device and confirm the same addresses appear. A phrase you have never restored is a guess, not a backup.
Fund it small first. Move a little, spend a little, learn the motions while the stakes are trivial.
If you use a passphrase (§11.5): generated, not invented; memorized or stored apart from the phrase; and understood — lose it and the phrase alone opens an empty wallet.
Recheck the storage once a year. Paper fades, houses flood, memory edits itself.

12.4Inheritance

Coins that only you can reach are coins that die with you. Decide deliberately who can recover, and how, and test that too: a sealed letter with instructions, a lawyer or trusted kin who knows the plan exists, a recovery drill run while you are watching. The checklist for this is short because the principle covers it: someone you trust should be able to follow your instructions to the coins without you in the room. If they can't, neither can your estate.

12.5The Checklist

The whole chapter, pocket-sized:

Fair generation: hardware wallet or offline audited software; dice for the serious.
Never self-made entropy: no brainwallets, no invented passphrases, no personal rules on the words.
Handwritten, in order, on paper or steel — two copies, two locations.
Nothing networked ever sees the words: no photos, no cloud, no typing except at recovery.
Test the restore before you fund. Fund small first.
Passphrase only if generated, stored apart, and its loss understood as total.
A recovery plan someone else can execute. Tested.

12.6Looking Back

The arc of the book, end to end. Counting told you how many; probability, how likely; expectation, how long the thief waits. Entropy measured the surprise; min-entropy measured his best guess; Chapter 6 found the one true source. Then the key: 256 fair bits, priced in sun-years and thermodynamic floors. The case files showed the price of every shortcut. And the phrase — the card on the table — turned out to be the fairest 128 bits your device can draw, wearing twelve words so a human can hold them.

The vaults of Bitcoin are not guarded by institutions, regulations, or obscurity. They are guarded by counting — by numbers so large the universe itself cannot count to them — and by the discipline to let physics, not habit, choose them. You now own both the arithmetic and the discipline. As always in this book: check it, don't take it.

Key Takeaways

Generate fair: hardware wallet, or offline audited software, or a hundred honest dice. Never a website, never your own invention.
Store analog: hand-written, in order, paper or steel, two copies in two places. Nothing networked ever touches the phrase.
Test before trusting: restore on a fresh device, confirm the addresses, fund small.
Passphrases are generated or absent. Invented ones are Chapter 9; lost ones are final.
Plan for your absence. Someone you trust must be able to recover — with instructions tested while you watch.

Exercises

Exercise 12.1 ★ The audit. Take this chapter's seven-point checklist and audit your own (or a hypothetical) setup against it, item by item. Which items pass? Which fail silently today?

Exercise 12.2 ★ The support call. A friendly "wallet support" agent emails asking you to "verify" your twelve words after a suspicious-login warning. Which rule does this trip, and what is the correct response?

Exercise 12.3 ★★ The dice plan. You decide to generate a 256-bit key by hand for a long-term vault. Using Chapter 6: how many die rolls do you need, about how long will it take at a roll every ten seconds, and why does the process being offline matter? (You should get about \(99\)–\(100\) rolls and about \(17\) minutes of rolling.)

Exercise 12.4 ★★ The two-location rule. Explain why two copies in the same house fail this chapter's standard even though "backups exist." Which Chapter-2 concept makes the reasoning precise?

Exercise 12.5 ★★★ Design the inheritance. Write a one-page recovery plan for a hypothetical holder: what gets stored where, who knows what, what the recovery drill looks like, and how each of this chapter's seven items is satisfied. Then attack your own plan: find the single point of failure, and fix it.

Solution Sketches

Sketches, not model answers — enough to check your reasoning against. The computational exercises embed their expected outputs in the exercise text.

Exercise 12.2. It trips the storage rule: anyone who asks for the words is stealing them — no legitimate support channel ever needs the phrase, because the phrase is the money. The correct response is to not reply, not comply, and report the attempt as the theft attempt it is. The deeper point: possession of the number is ownership (Chapter 7), so handing over the words is not "verification," it is transfer.

Exercise 12.4. Same house means the two copies share fate: one fire, one flood, one burglary takes both. In Chapter 2's language, the two copies are not independent — their losses are the same event, so their protection does not multiply. Two locations make the losses independent, and independence is what turns "one disaster" into "two simultaneous disasters," a chance that multiplies toward zero.