Single-sig — one hardware wallet, one seed phrase, one backup — is the structurally simplest self-custody configuration and the right answer for a meaningful fraction of holders; the passphrase variation layers a BIP-39 passphrase over the same seed to derive a separate, exposure-protected wallet without adding cryptographic primitives. The single-sig baseline is not a deficient configuration to be climbed away from — it is Configuration 1 of the Self-custody configuration ladder and is often the structurally-safest choice when complexity itself is the dominant threat. The passphrase variation (Configuration 2) is a sharp loss-vs-exposure trade: it defends against found-seed attacks but introduces a new artifact whose backup discipline must match the seed's. This note treats the operational configuration — four-artifact base setup, passphrase-as-added-artifact variation, decoy and multi-passphrase patterns, and the conditions under which climbing to multisig is structurally indicated rather than just appealing. Cryptographic mechanism defers to Passphrases and the 25th word and Seed phrases and BIP-39.
Why this note matters
Single-sig is the most-underestimated configuration in the ladder. The literature’s emphasis on multisig as the “serious” answer leaves many holders assuming single-sig is a beginner’s stop on the way up — and adopting higher rungs before they have the operational discipline to sustain them. The note matters because:
- It establishes single-sig as a defensible terminal configuration for the holders it fits — not a transitional one. Climbing the ladder is a measure of fit, not seriousness.
- It treats the passphrase variation as a layered modification of the same configuration rather than a structurally distinct setup — the operational practice is single-sig’s, with one additional artifact under one additional discipline.
- It frames the decoy-wallet pattern honestly — what it defends against, what it does not, and why treating it as the primary value of the passphrase overstates what plausible deniability can do.
The defensible position: a tested single-sig setup with documented inheritance is structurally safer than an untested multisig. The passphrase is the right addition when seed-exposure is the named threat AND the holder will sustain the passphrase backup; otherwise it converts an exposure risk into a self-inflicted loss vector.
What this is
Single-sig is the configuration where a single key signs every transaction. One hardware wallet generates and holds one BIP-39 seed; the wallet derives all spending keys from that seed; signing requires only that device. This is Configuration 1 of the Self-custody configuration ladder.
The passphrase variation adds a BIP-39 passphrase — an arbitrary string combined with the seed during key derivation — to produce a different wallet from the same seed. The seed alone opens one wallet (typically treated as a decoy); the seed plus the passphrase opens the real wallet. This is Configuration 2 of the ladder.
Both configurations sit on the same operational base: one device, one signing surface, one wallet at any given time. The passphrase does not introduce multisig coordination, descriptors, or quorum mechanics — operationally the holder is still running a single-key wallet. What changes is the artifact count and the backup discipline.
The configuration vs. mechanism distinction
This note treats what the configuration looks like in practice — the artifacts, the setup steps, the spending mechanics, the patterns built on top. It does not re-derive how the cryptography works. The mechanism content lives elsewhere:
- BIP-39 seed encoding, derivation paths, the seed-is-not-a-password principle — see Seed phrases and BIP-39
- The PBKDF2 combination, the “25th word” naming critique, fingerprint verification, passphrase-strength entropy — see Passphrases and the 25th word
- The synthesis-level argument for where these configurations sit on the ladder — see Self-custody configuration ladder
- The loss-vs-exposure framing the passphrase trade-off rests on — see Loss vs exposure failure modes
When to use this
Baseline single-sig is appropriate when:
- Holdings are Tier 0 or Tier 1 (under roughly $50K), where complexity itself is often the dominant threat
- The holder is in the first year or two of self-custody and has not yet internalized the discipline higher configurations demand
- The threat model is dominated by yourself-category risks (forgetfulness, novel-scheme self-inflicted loss, inheritance failure) — single-sig’s simplicity is a defence here
- The holder values recovery speed and operational simplicity over the marginal exposure protection higher configurations buy
Single-sig with a passphrase is appropriate when:
- The holder’s threat model ranks seed-phrase exposure as a named, serious concern (a found metal backup, an extracted seed from a compromised device, an opportunistic discovery during a move or burglary)
- The holder has the operational discipline to back up the passphrase with the same rigor as the seed — separate location, durable medium, documented for heirs
- The holder has planned for inheritance of both artifacts and understands the passphrase-only-in-head failure mode catalogued in Common failure modes in self-custody
Climbing past single-sig + passphrase to multisig is structurally indicated when:
- Holdings cross into Tier 2+ AND the holder has the operational capacity for six-items-to-manage (see Multisig setups)
- The threat model includes adversaries the passphrase cannot meaningfully defend against — coercion-at-gunpoint, sophisticated targeted attackers, jurisdictional risk
- Inheritance complexity is high enough that a partnered configuration (see Collaborative custody services) is structurally better than passing on a single-sig + passphrase setup
The choice is not a hierarchy of correctness. A well-managed single-sig + passphrase at Tier 1 is structurally safer than a poorly-managed 2-of-3 at Tier 2.
Standard single-sig configuration
The operational base. Four artifacts; one signing surface.
The four-artifact base
- The hardware wallet — the device that generates the seed, holds the keys in its secure element, and signs transactions. See Hardware wallets overview.
- The seed backup — the BIP-39 mnemonic recorded on durable media (typically metal). The load-bearing artifact; everything else is scaffolding. See Seed phrases and BIP-39 and Steel seed storage.
- The recovery plan — written documentation of what the setup is, where the seed lives, and what an heir (or future-you under stress) needs to do. See Inheritance planning for bitcoin.
- Optionally, a coordinator — Sparrow, Specter, Nunchuk, or a vendor companion app. Many single-sig setups use the vendor app and no separate coordinator. For PSBT-based flows, the coordinator becomes useful. See PSBT and wallet descriptors.
Setup
- Acquire a hardware wallet from the manufacturer or an authorized reseller. Verify tamper-evident packaging. Common choices: Coldcard, BitBox, Foundation Passport, Trezor, Blockstream Jade; see Ledger considerations and tradeoffs for the Ledger case specifically.
- Initialize the device. Generate the seed on-device using the hardware random number generator. Most devices default to 24 words; 12 is also fine cryptographically — see Seed phrases and BIP-39 for the trade.
- Record the seed on metal. Paper as the initial recording is acceptable for transcription; the durable backup is metal. Destroy the paper after the metal backup is verified.
- Verify the backup. Most devices offer a verification flow that asks the holder to confirm specific words at specific positions. Stronger verification: wipe the device, restore from the metal backup, confirm the wallet displays the same addresses as before the wipe. See Recovery rehearsal practice.
- Test with a small transaction. Send a small amount in; verify receipt; send a small amount out; confirm the signing flow works end-to-end. Only then fund the wallet with substantial holdings.
- Store the backup. Geographic distribution at Tier 1+ is recommended — see Backup strategies for seeds for the full discipline.
Spending
The routine spend on a single-sig wallet:
- The wallet software (vendor app or coordinator) constructs the transaction. The holder reviews the destination address and amount.
- The transaction is sent to the device — directly over USB, by QR code, by microSD, or by NFC depending on the device’s air-gap posture.
- The device displays the transaction. The holder verifies the destination address on the device screen — not just in the wallet software, which is the address-replacement attack surface. See Common attack vectors.
- The holder confirms; the device signs and returns the signed transaction.
- The wallet software broadcasts.
For air-gapped devices (Coldcard in air-gap mode, Foundation Passport’s QR-only flow), the PSBT round-trip uses QR codes or microSD rather than USB. The principle is the same; the friction is higher.
Recovery
The single-sig recovery flow:
- Acquire a replacement device — same vendor for the cleanest path; an alternate BIP-39-compatible device for vendor-lock-in resistance.
- Wipe the device (if previously used) and initiate the restore flow.
- Enter the seed phrase. The device computes the master seed and derives the same keys.
- Verify by checking that the device displays the same receive address the original did. The match is the verification that recovery succeeded.
Single-sig recovery is the simplest in the ladder. There is no descriptor to coordinate, no quorum to assemble, no partner to contact — one seed into one device produces the wallet. This recovery-speed property is part of why single-sig is the structurally-safer choice for many holders.
Single-sig + passphrase variation
The passphrase variation changes one element of the setup and adds one artifact. The operational base is otherwise identical.
What changes vs. the base
- One additional artifact. The passphrase is a string the holder chooses (or generates) at wallet creation. It must be backed up with discipline equal to the seed’s, in a separate location, with documentation for heirs.
- A second wallet on the same seed. The seed alone opens one wallet (call it the unpassphrased wallet); the seed plus the passphrase opens a different one. Most hardware wallets allow switching between these by entering or omitting the passphrase at wallet load time.
- A new failure mode. A lost or forgotten passphrase with no backup means the real wallet is permanently inaccessible — the seed alone opens only the unpassphrased wallet. This is the most-cited inheritance failure mode in the synthesis; the cryptographic and operational depth lives in Passphrases and the 25th word.
Setup variation
The setup steps from the base configuration apply unchanged through device initialization and seed backup. Then:
- Choose the passphrase. A six-word Diceware passphrase is sufficient for most holdings; weaker passphrases (single dictionary word, family name) are nearly as bad as no passphrase. The strength selection logic lives in Passphrases and the 25th word.
- Enter the passphrase at wallet creation. The device derives the passphrase-protected wallet and displays its receive addresses.
- Record the wallet fingerprint. Most hardware wallets display a short hexadecimal fingerprint when a passphrase-protected wallet loads. Record this with the passphrase backup. At any future restoration, the same seed + passphrase should produce the same fingerprint — the check that catches passphrase mis-entry before any funds are lost.
- Back up the passphrase separately from the seed. Different location, ideally different medium, documented for heirs. The seed and passphrase together open the wallet; storing them in the same place defeats the exposure protection.
- Verify with a test transaction against the passphrase-protected wallet — fund it with a small amount, restore on a wiped device using both seed and passphrase, confirm the addresses and fingerprint match, sweep back if desired.
- Fund the passphrase-protected wallet with substantial holdings; leave the unpassphrased wallet empty or use it as a decoy (see below).
Spending friction
The passphrase variation adds one friction point: every time the holder loads the wallet on the device, the passphrase must be entered. Hardware-wallet ergonomics vary considerably here — see the Tooling section below. For holders who spend frequently, the friction can become an avoidance pattern that erodes the security; for holders treating the wallet as cold storage, the friction is rare.
Some devices cache the passphrase across a session; others require entry at every device unlock. The trade-off between convenience and exposure (the cached passphrase is in device memory and could in principle be extracted by a sufficiently sophisticated attacker) is device-specific.
Recovery variation
The recovery flow adds two steps: enter the passphrase alongside the seed, and verify the fingerprint matches the recorded value. A passphrase that “almost matches” the original — a different character, a missing space, different case — produces a different wallet, not an error. The fingerprint verification catches the mismatch before the holder makes irrevocable decisions. The mechanism detail is in Passphrases and the 25th word.
Common operational patterns
Two patterns are common enough to warrant treatment. Both are layered on top of single-sig + passphrase rather than separate configurations.
Decoy wallets
The structural pattern: the unpassphrased wallet (seed alone, no passphrase) is funded with a small balance and treated as the visible “this is everything I have” wallet. The real holdings are in the passphrase-protected wallet. An attacker who obtains the seed and loads it sees the decoy balance, ideally believing they have found the full set.
The decoy pattern’s effectiveness is psychological, not cryptographic. It depends entirely on the attacker’s beliefs about whether more exists. The pattern works reasonably well against:
- Passive search-of-premises — a burglar who finds a metal backup, loads the seed, sees a balance, takes it, and moves on
- Opportunistic seed-find — a roommate, house-sitter, or family member who discovers the seed and acts on it without expert support
- Forensic acquisition of a single device — an attacker who acquires the device but lacks the passphrase
The pattern fails or partially fails against:
- Coercion-at-gunpoint — Lopp documents cases catalogued in Common attack vectors where holders handed over decoys and were tortured for hours on the assumption of hidden reserves; the attacker who assumes more exists is not deterred by a small balance
- Sophisticated targeted attackers who have done research on the holder’s likely net worth and treat the decoy balance as obviously incomplete
- Coordinated coercion of multiple family members where the attacker can cross-check
The honest framing: the decoy is one layer among several, useful against specific opportunistic threat profiles, structurally inadequate against coercion. It should not be treated as the primary defence against an in-person attacker — the structural defence against coercion is to genuinely not be able to move funds unilaterally (multisig with remote confirmer, time-locked transactions, geographic distribution). The decoy is a partial measure.
A funded decoy is more convincing than an empty one. The trade-off: the funds in the decoy are exposed in the cases where the decoy “works” — the attacker takes them. Sizing the decoy is a balance between deniability and acceptable loss.
Multiple passphrases for different wallets
The pattern: one seed, several passphrases, several wallets — passphrase A for spending, passphrase B for savings, passphrase C for travel money, passphrase D for a family member’s allocation. The seed is backed up once; each passphrase is backed up separately; the holder switches wallets by switching passphrases at device load.
Use cases where the pattern is appealing:
- Compartmentalization across purposes — a clean operational separation between spending, savings, and high-friction-cold without needing multiple hardware wallets
- Family-member separation — distinct wallets for distinct people, derived from one master seed the holder controls
- Travel patterns — a “travel passphrase” wallet with a small balance, kept separate from main savings
Failure modes the pattern introduces:
- Passphrase confusion — multiple passphrases multiply the recall burden and the mis-entry risk. The “which passphrase opens which wallet?” problem under stress is real.
- Backup multiplication — each passphrase is a new artifact with its own backup discipline. Three passphrases means three separate backup chains, each of which must survive the holding horizon and be findable by heirs.
- Fingerprint tracking burden — each wallet has its own fingerprint; verifying the right wallet loaded for the right purpose requires checking against the right recorded fingerprint. The administrative overhead compounds.
- Inheritance complexity — the heir now needs to learn that multiple wallets exist, find each passphrase backup, and verify each correctly. The passphrase-only-in-head failure mode multiplies across passphrases.
When the pattern is appropriate: holders with explicit compartmentalization needs and the discipline to maintain parallel backup chains. The Coldcard’s multi-passphrase wallet support is designed for this use case and includes the operational tooling to manage it.
When the pattern is a mistake: holders who adopt it because “more wallets is more security.” Each additional passphrase is a new single point of failure. For most compartmentalization needs, BIP-85 child seeds is a structurally cleaner approach — the child seeds have independent entropy and can be backed up independently rather than depending on a shared seed plus distinct passphrases. For separation across heirs or jurisdictions, SLIP-39 and Shamir Secret Sharing or Multisig setups is generally a better answer.
Tradeoffs and considerations
Single-sig’s simplicity is a structural feature, not a deficiency
The literature’s emphasis on multisig as the “serious” configuration can read as implying single-sig is provisional — a starter setup to be climbed away from as soon as holdings justify the climb. The synthesis reading is the opposite: complexity is the top cause of self-inflicted Bitcoin loss, and the configurations that age best are the ones the holder can sustain across the holding horizon. A single-sig setup the holder genuinely understands, has tested, and has documented for heirs is structurally safer than a higher-rung configuration the holder is operating at the edge of their competence.
The right framing: choose the lowest-complexity configuration that adequately covers your threat model. For many holders, that configuration is single-sig.
The passphrase is a sharp loss-vs-exposure trade
The passphrase reduces exposure risk substantially and increases loss risk substantially. The trade is favourable when exposure risk dominates the holder’s threat model AND the passphrase backup discipline is sustained. The trade is unfavourable when yourself-category risks dominate — and the synthesis is direct that yourself-category risks dominate for most holders. See Loss vs exposure failure modes for the framing and Threat modeling for self-custody for the categorization.
The detailed treatment of when the trade is favourable lives in Passphrases and the 25th word. The configuration-level takeaway: the passphrase is not a default upgrade. It is a specific tool for a specific named threat.
Multi-passphrase complexity scales superlinearly
Two passphrases on one seed is not “twice the complexity” of one passphrase; it is meaningfully more — because the recall, backup, fingerprint-tracking, and inheritance burdens all compound. The synthesis treats stacked custom passphrases as one of the most-harmful patterns in the literature. Holders who find themselves wanting a second passphrase should evaluate whether the structural need is genuinely passphrase-shaped or whether BIP-85 child seeds, SLIP-39 and Shamir Secret Sharing, or Multisig setups would address the underlying need more cleanly.
When single-sig + passphrase is preferable to multisig
Single-sig + passphrase has one device, one seed, one passphrase, and one signing surface — three artifacts under the holder’s discipline. DIY 2-of-3 multisig has three devices, three seed backups, one descriptor, and coordinator state — six to eight artifacts. For holders at Tier 1 or low Tier 2 whose threat model is dominated by seed-exposure rather than coercion or coordinated attack, the single-sig + passphrase configuration is often a better fit than DIY multisig — the operational discipline required is lower, recovery is faster, and inheritance is structurally simpler.
The holder’s question: which configuration can you sustain end-to-end, including testing, documentation, and inheritance? That answer is often single-sig + passphrase even at holding levels where multisig is theoretically defensible.
When multisig is structurally superior
The passphrase concentrates risk on the seed-plus-passphrase pair. An attacker who obtains both spends the funds; the holder who loses either loses access. Multisig spreads risk across multiple keys — no single key is sufficient, no single loss is catastrophic. For threat models that include coercion, sophisticated targeted attacks, jurisdictional risk, or the holder’s own operational fragility, the structural protection of multisig is genuinely different from what a passphrase can provide.
The passphrase + multisig combination (passphrase on each multisig key) is sometimes proposed; the operational complexity is usually prohibitive. The cleaner pattern for holders who want both exposure and multi-key protection: DIY 2-of-3 multisig without passphrases, with each seed backup placed in a location where seed-exposure is not the dominant threat. See Multisig setups for the full treatment.
Tiered application
Tier 0 (under $1K): Baseline single-sig is correct. The passphrase complexity is not justified at this scale; the inheritance burden it adds is typically larger than the exposure protection it provides.
Tier 1 (50K): Baseline single-sig is the default. Single-sig + passphrase is appropriate where seed-exposure is a named threat (the holder moves frequently, travels with backups, works in shared spaces) AND the passphrase backup discipline is sustained. Multisig is overkill at this tier and the complexity often dominates the benefit.
Tier 2 (1M+): Single-sig + passphrase is reasonable as the operational configuration for spending and near-term reserves; multisig (DIY or collaborative — see Multisig setups and Collaborative custody services) becomes the appropriate configuration for the long-term-savings portion of the holding. A tiered-wallet portfolio (the Hot vs cold storage pattern, extended) is often the right answer at this tier — different configurations for different purposes.
Tier 3 (>$1M): Single-sig + passphrase as a standalone protection is structurally fragile at this tier — the trade-off favours multisig configurations. The passphrase has a role paired with multisig (passphrase on the operational portion; multisig on deep cold) but should not be the sole defence. Climbing past single-sig + passphrase is structurally indicated.
In every tier, the principle: the configuration is only as safe as the discipline that sustains it. A well-managed Configuration 1 is structurally safer than a poorly-managed Configuration 2.
Common pitfalls
Treating single-sig as a beginner stop. Single-sig is a defensible terminal configuration for the holders it fits. Climbing the ladder because “more security is better” is the pattern the synthesis catalogues as the dominant cause of self-inflicted loss.
Adopting a passphrase without sustaining the backup. The passphrase that exists only in the holder’s head is the most-cited inheritance failure mode in the literature. The seed phrase — which is backed up — gives the illusion that the wallet is recoverable. It is not. The detailed treatment lives in Passphrases and the 25th word; the configuration-level rule: if the holder cannot articulate the passphrase backup discipline before adopting it, the passphrase is a self-inflicted loss vector.
Storing the seed and passphrase in the same location. The passphrase’s structural purpose is that the seed alone is insufficient. Co-locating them defeats the exposure protection while preserving all of the additional loss risk. Different locations, different access patterns.
Skipping the fingerprint verification at setup. Hardware wallets display a fingerprint when a passphrase-protected wallet loads. A passphrase that “almost matches” the original produces a different wallet, not an error. Without the recorded fingerprint, the holder may discover the mismatch only at restoration time — too late.
Funding the wallet before testing recovery. A backup that has not been restored from is a hope, not a backup. For single-sig: wipe and restore on the same device. For single-sig + passphrase: wipe and restore including the passphrase, verify the fingerprint matches, confirm the receive address matches. See Recovery rehearsal practice.
Treating the decoy as the primary defence against coercion. The decoy works against passive-search threats; it is structurally inadequate against in-person coercion. Treating plausible deniability as the passphrase’s main value overstates what the pattern can do. See Common attack vectors.
Multi-passphrase stacking. Each additional passphrase is a new single point of failure with its own backup chain. The pattern is generally a mistake for most holders; BIP-85 child seeds, SLIP-39 and Shamir Secret Sharing, or Multisig setups handle the underlying compartmentalization needs more cleanly.
Photographing or digitally storing the passphrase. The passphrase is subject to the same operational rules as the seed — no photos, no password managers, no digital copies. The exposure surface for the passphrase is the same surface that makes the seed dangerous to digitize. See Seed phrases and BIP-39.
Not documenting the passphrase’s existence for heirs. An heir who finds the seed and loads it sees the decoy (or empty) wallet. Without documentation that a passphrase exists and where it is backed up, the heir concludes “there was nothing here.” The seed-and-only-the-seed inheritance is the failure mode the synthesis catalogues most often.
Choosing a weak passphrase. A dictionary word, a family name, a date — the attacker with the seed can try common candidates and find the passphrase. Passphrase strength should match the value being protected. The detailed strength calculus lives in Passphrases and the 25th word.
Comparison with alternatives
| Approach | Structural protection | Operational complexity | Inheritance complexity | Tier fit |
|---|---|---|---|---|
| Single-sig | Single point of failure on the seed | Lowest | Lowest | Tier 0–1 |
| Single-sig + passphrase | Two artifacts must be compromised | Low-medium | Medium-high (passphrase backup required) | Tier 1–2 |
| SLIP-39 | Distributed backup, single-sig operation | Medium | Medium (share coordination) | Tier 1–2 |
| DIY 2-of-3 multisig | No single-key compromise | High | High | Tier 2–3 |
| Collaborative 2-of-3 | Same as DIY but with partner managing complexity | Medium | Lower (partner-supported) | Tier 2–3 |
The decision pattern matches the Self-custody configuration ladder: choose the lowest-complexity configuration that adequately covers your threat model. The passphrase is the right addition for specific named threats; it is not a default upgrade from baseline single-sig.
Tooling and resources
Hardware-wallet ergonomics for passphrase entry:
- Coldcard Q — full QWERTY keyboard; best-in-class for passphrase entry; the most ergonomic option for holders who plan to use passphrases routinely
- Trezor Safe 5 — colour touchscreen; acceptable passphrase entry; the touchscreen ergonomics are a meaningful upgrade over older Trezor models
- BitBox BitBox02 — button-by-button character selection; tedious for long passphrases; appropriate for low-frequency passphrase entry
- Foundation Passport — air-gap-first; passphrase entry via the device keypad; the QR-only flow adds friction to the overall operational loop
- Blockstream Jade — passphrase support; budget-appropriate ergonomics; suitable for holders who treat the passphrase as a low-frequency entry
- Bitkey — different architectural model; the passphrase pattern this note describes does not map cleanly to Bitkey’s design (see Bitkey)
The synthesis recommendation: holders who plan to use passphrases should evaluate device choice partly on passphrase-entry ergonomics. A passphrase that is painful to enter will be avoided, which erodes the security.
Coordinator options for single-sig (most setups use the vendor app and no separate coordinator):
- Sparrow Wallet, Specter Desktop, Nunchuk — full coordinator support for single-sig with PSBT flows
- Vendor companion apps — Coldcard’s “Mk4” app, BitBox app, Trezor Suite, Passport’s Envoy — sufficient for most single-sig operational needs
Primary practitioner sources:
- Jameson Lopp — passphrase guidance and the documented coercion-case database; the operational essays informing the decoy-pattern honesty
- BitBox — Passphrase Operational Guide; explicit treatment of the passphrase-backup problem
- Coldcard — passphrase implementation documentation including the multi-passphrase wallet pattern
- Trezor — passphrase-protected wallet documentation
- Casa, Unchained — passphrase-vs-multisig comparison material
The synthesis document: Bitcoin Self-Custody & Security (LegacyCipher, April 2026) — single-sig as Configuration 1 and single-sig + passphrase as Configuration 2 of the ladder.
As of 2026-05-17: the BIP-39 passphrase specification is stable; hardware-wallet passphrase support is universal among mainstream devices, with the entry ergonomics being the principal differentiator.
Open questions for further development
- The decoy-pattern effectiveness against specific named attacker profiles is mostly anecdotal in the literature. Are there comparative data on decoy-wallet outcomes across coercion-vs-opportunistic threat categories?
- The multi-passphrase pattern is widely discouraged in the synthesis but Coldcard’s tooling explicitly supports it. Is the device-level support evidence that the pattern is more defensible than the synthesis treats it, or is it tooling that exists because the use case is real even where the pattern is fragile?
- The single-sig + passphrase vs SLIP-39 comparison is structurally close — both are single-sig operational configurations with distributed exposure protection. The synthesis treats SLIP-39 as the cleaner inheritance answer (because the passphrase-backup problem dissolves into share coordination); is the comparison well-grounded in practice?
- Passphrase fingerprint verification depends on the holder having recorded the fingerprint at setup. For holders who did not, recovery becomes a search problem if the passphrase is mis-remembered. Should the framework treat fingerprint recording as non-negotiable rather than as a best practice?
- The passphrase-on-the-multisig-key pattern (where each multisig key uses its own passphrase) is sometimes proposed for additional defence-in-depth. The operational complexity is usually prohibitive — but the pattern is occasionally adopted. Should the framework treat it explicitly?
Related notes
The framing context:
- Loss vs exposure failure modes — the passphrase is a sharp loss-vs-exposure trade
- Threat modeling for self-custody — passphrase appropriateness depends on threat profile
- Self-custody configuration ladder — Configuration 1 (single-sig) and Configuration 2 (single-sig + passphrase)
Adjacent custody configurations:
- Multisig setups — the structural alternative when seed-plus-passphrase concentration is the dominant risk
- Collaborative custody services — the partnered alternative for Tier 2+ holders
- Hot vs cold storage — single-sig sits across the temperature spectrum
The mechanism notes this configuration defers to:
- Seed phrases and BIP-39 — the seed the configuration is built on
- Passphrases and the 25th word — the cryptographic and operational depth of the passphrase variation
- BIP-85 child seeds — the cleaner answer for compartmentalization needs the multi-passphrase pattern often targets
- SLIP-39 and Shamir Secret Sharing — the alternative inheritance answer to the passphrase-backup problem
- PSBT and wallet descriptors — the infrastructure when a coordinator is used
Hardware wallets:
- Hardware wallets overview — device-selection framework
- Coldcard, Trezor, BitBox, Foundation Passport, Blockstream Jade, Bitkey, Ledger considerations and tradeoffs
Backup and operational discipline:
- Backup strategies for seeds — the discipline the seed backup rests on
- Steel seed storage — the durable-medium specifics
- Recovery rehearsal practice — the test that distinguishes a setup from a hope
Operational security:
- Common attack vectors — the threat catalogue including the coercion cases the decoy pattern engages with
- Operational security practices — the behavioural layer
- Common failure modes in self-custody — the catalogued failures including the passphrase-only-in-head pattern
Inheritance:
- Inheritance planning for bitcoin — the load-bearing consideration for whether the passphrase variation is appropriate
The principal practitioner:
The sub-MOC home: