Practical self-custody and sovereignty
Holding your own keys — threat models, hardware, multisig, inheritance.
The operational and procedural dimensions of holding Bitcoin without trusted intermediaries. Where the Economics and Culture-philosophy sections argue why sound money matters, this section answers how to actually hold it — across the full range of threat models, holding sizes, and life stages. The animating principle:…
Foundational framing
These three notes establish the lenses. Read them before the rest of the section — they make the trade-offs in every subsequent note legible
The opposing-risks rule of thumb; the historical record of lost-vs-stolen Bitcoin; the principle that good design is articulated trade-offs
The six adversary categories; the "name your top three" exercise; the structural reason why different holders should adopt different setups
The seven canonical configurations from single-sig to 3-of-5 to BIP-85-orthogonal, with combined setups (helpful, questionable, actively harmful) called out separately. The synthesizing…
Storage and key concepts
The cryptographic primitives and operational vocabulary. These notes describe what you are protecting, in the precise terms the rest of the section uses
The dimension that organizes everything else. The tiered-wallet approach (hot for transactions, cold for reserves, deep-cold for savings) and why mixing them is the principal pattern across…
The BIP-39 standard, the 12/24-word convention, what a seed phrase is and is not (a seed phrase is not a password — anyone who sees it has everything forever)
The optional BIP-39 passphrase, plausible deniability, the passphrase-backup problem (the most common documented inheritance failure mode in the synthesis)
Deterministic derivation of child seeds from a master; orthogonal to custody schemes; reduces backup count but concentrates failure on the master
Mathematical M-of-N splits; the critical recovery-time caveat (the seed is reconstructed singularly on one device at restore); how it differs from multisig
The unglamorous infrastructure: Partially Signed Bitcoin Transactions and wallet descriptors. The descriptor as first-class backup artifact for multisig
Hardware wallets
The comparative landscape and per-device assessments. The overview note establishes the framework (air-gap, open-source firmware, multisig support quality, PSBT/descriptor support, vendor track record, progress indicators); the product…
The 2026 device table; what to actually look for; vendor diversity as cheap insurance in multisig
The power-user device; Coldcard Q with QWERTY and QR/NFC; strong BIP-85 and multisig support
Trezor Safe 5; native SLIP-39; colour touchscreen
BitBox02 BTC-only; Swiss engineering; open-source; pairs well in multi-vendor multisig
Honest assessment including the 2023 Recover controversy; framing for the holders who already own one
Strict QR air-gap; pleasant UX; removable battery
Budget-conscious; good multisig support; 2026 Unchained integration
Non-technical, mobile-first; no screen; higher app reliance
Custody configurations
Three operational configurations spanning the simplicity-to-complexity range, from baseline single-sig (with the optional passphrase variant as a layered modification) through engineered multi-key answers to the trade-off problem. The…
the baseline configuration: standard single-sig spending, the passphrase variation that protects against seed exposure at the cost of new loss risk, and common operational patterns (decoy…
DIY 2-of-3 sovereign multisig: vendor diversity, geographic distribution, the six-items-to-manage problem, re-keying mechanics, why 3-of-5 is the right answer only for a small minority
2-of-3 with a partner key: Unchained (white-glove, inheritance-focused), Casa (multi-key architecture), Nunchuk (sovereignty-minimized), The Bitcoin Adviser (estate-planning bent).…
Backup, recovery, and rehearsal
The discipline that turns a setup into a tested setup. The synthesis's strongest claim: a backup that has not been tested is not a backup; it is a hope
Paper, metal, geographic distribution, the wallet descriptor as a first-class artifact, what to do with the passphrase backup
Specific metal products, Lopp's four rounds of stress tests, the failure rate of products marketed as indestructible, what actually survives heat/corrosion/deformation
The first rehearsal (wipe and restore with small amounts before funding the wallet); periodic rehearsals; signed-challenge-message lightweight rehearsals; what to actually test
Operational security
The behavioural layer. The synthesis is direct: technical security is a ceiling, not a foundation; a material fraction of real-world losses are not cryptographic but human
Phishing as the single highest-incidence threat; clipboard malware; address replacement; supply-chain attacks; the KYC-data-to-home-invasion pipeline; the $5 wrench attack
Don't talk about Bitcoin (Lopp's single-most-emphasised point); compartmentalised KYC identity; the cognitive-state rule for transactions; the limits of decoy and duress patterns
The catalogue: the passphrase no one knew about, the forgotten passphrase, the untested metal backup, co-located multisig, the lost wallet descriptor, the seed photo, the phishing…
Privacy practice
The chain-analysis exposure layer. Custody secures your access to your coins; privacy practice secures your linkage to them. The loss-vs-exposure framing extends naturally — privacy practice defends a specific exposure mode: third parties…
The foundational threat. How chain-analysis firms cluster addresses; the common-input-ownership and change-detection heuristics; the practical exposure of address reuse; what hygiene…
The institutional-exposure surface. What KYC records create; how exchange breaches and court orders activate them; the practical defences (compartmentalised identities, withdrawal hygiene…
The principal privacy-enhancing transaction pattern; mechanism with light hand; tool history including the 2024 Samourai indictment and Wasabi voluntary wind-down; the current state of…
BIP-78 cooperative funding; how it breaks the common-input-ownership heuristic without requiring coordination rounds; current adoption
The recipient-side privacy primitive; predecessor stealth-address designs; BIP-352 Silent Payments as the current state of the art; what wallets implement it
What Lightning hides (the transaction graph for routed payments) and what it doesn't (channel open/close on-chain footprints, routing-node observability, receive-side leakage); the…
Inheritance
The failure mode that has quietly consumed a material fraction of all Bitcoin ever mined — and the area where the operational content interfaces most deeply with the broader estate-planning literature
Running your own node
The sovereignty layer beyond the keys. Verifying your own transactions, not trusting third-party explorers, optionally serving as the backend for your own wallet
What a full node does, why you might want one, the IBD experience, ongoing operational considerations
Umbrel, Start9, Raspiblitz, custom builds. Plug-and-play vs DIY
Electrum server, BTCPayServer integration, what it takes to actually consult your node rather than a third-party explorer