{
  "reviewed": "2026-11-12",
  "scope": "177 reader documents inventoried; 82 targeted correction rules, 53 current-context modules and 13 localized update summaries. Source review is not hands-on validation of every historical walkthrough.",
  "articles": [
    {
      "id": "inheritance-plan",
      "title": "Make a plan someone else can follow",
      "category": "Inheritance",
      "description": "Turn your recovery knowledge into clear instructions for the people who may need them.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Start with the human problem",
          "paragraphs": [
            "You may know exactly which wallet you use and where every backup belongs. Someone helping after your death or incapacity may know none of that. The first inheritance task is to make the existence of the arrangement discoverable to the right person, with a clear route to trustworthy help.",
            "A useful plan should answer: what exists, who is intended to act, how they find the instructions, and what they should do first. Draft that explanation in ordinary language. Avoid a puzzle that depends on remembering an old conversation or guessing what an unexplained device is for."
          ],
          "bullets": []
        },
        {
          "heading": "Keep instructions and spending authority distinct",
          "paragraphs": [
            "A readable instruction sheet does not need to contain every secret. It can identify wallet types, explain the required recovery materials and describe how an authorized person can access them. Decide deliberately who can discover the plan and who can actually satisfy the wallet’s spending conditions.",
            "If you use multisig, include the configuration backup and a description of the threshold. If you use a passphrase, the recovery plan must account for it. Do not put actual recovery words into this prototype or any online planning worksheet. Use the site to understand the structure, then create and store your private materials appropriately."
          ],
          "bullets": []
        },
        {
          "heading": "Understand the promises of an assisted service",
          "paragraphs": [
            "Inheritance products can use different mechanisms. A service-enforced date relies on the service following its rules and being available. An on-chain timelock encodes conditions into the wallet’s spending policy. These are different dependencies, even if the interfaces use similar language.",
            "Nunchuk’s documentation, for example, distinguishes on-chain and off-chain inheritance arrangements and describes different recovery requirements. Read the specific product documentation rather than assuming every subscription works alike. Ask what happens if the company closes, a beneficiary loses their materials, or the plan must change. Keep the answers with the instructions."
          ],
          "bullets": []
        },
        {
          "heading": "Rehearse with fictional information",
          "paragraphs": [
            "Give your proposed helper a dummy instruction sheet and fictional materials. Ask them to explain the first three actions they would take. Watch for ambiguous words, missing contacts and assumptions about technical knowledge. A confusing rehearsal is useful feedback: simplify the document before anyone needs it in a stressful situation.",
            "Technical access and legal entitlement are separate matters. Coordinate the technical arrangement with qualified local estate-planning advice, especially when multiple beneficiaries, trustees or jurisdictions are involved. This guide is a practical preparation exercise rather than a legal document or a complete estate plan.",
            "Review after meaningful life or wallet changes. A moved backup, changed beneficiary, new passphrase or altered signing policy can invalidate yesterday’s instructions. The desired outcome is a short, current route that another person can understand, with enough redundancy to survive ordinary mistakes and enough care to avoid granting unintended access."
          ],
          "bullets": [
            "Someone appropriate knows the plan exists.",
            "The instructions identify every required recovery component.",
            "A helper has rehearsed with dummy information.",
            "Technical access and the estate plan have been coordinated."
          ]
        }
      ],
      "sources": [
        {
          "title": "Nunchuk: inheritance FAQ and service dependencies",
          "url": "https://nunchuk.io/faq"
        },
        {
          "title": "Nunchuk: inheritance mechanisms",
          "url": "https://nunchuk.io/inheritance"
        },
        {
          "title": "Nunchuk: claiming instructions",
          "url": "https://nunchuk.io/howtoclaim"
        },
        {
          "title": "BIP129: wallet configuration",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 430,
      "html": "<section><h2>Start with the human problem</h2><p>You may know exactly which wallet you use and where every backup belongs. Someone helping after your death or incapacity may know none of that. The first inheritance task is to make the existence of the arrangement discoverable to the right person, with a clear route to trustworthy help.</p><p>A useful plan should answer: what exists, who is intended to act, how they find the instructions, and what they should do first. Draft that explanation in ordinary language. Avoid a puzzle that depends on remembering an old conversation or guessing what an unexplained device is for.</p></section><section><h2>Keep instructions and spending authority distinct</h2><p>A readable instruction sheet does not need to contain every secret. It can identify wallet types, explain the required recovery materials and describe how an authorized person can access them. Decide deliberately who can discover the plan and who can actually satisfy the wallet’s spending conditions.</p><p>If you use multisig, include the configuration backup and a description of the threshold. If you use a passphrase, the recovery plan must account for it. Do not put actual recovery words into this prototype or any online planning worksheet. Use the site to understand the structure, then create and store your private materials appropriately.</p></section><section><h2>Understand the promises of an assisted service</h2><p>Inheritance products can use different mechanisms. A service-enforced date relies on the service following its rules and being available. An on-chain timelock encodes conditions into the wallet’s spending policy. These are different dependencies, even if the interfaces use similar language.</p><p>Nunchuk’s documentation, for example, distinguishes on-chain and off-chain inheritance arrangements and describes different recovery requirements. Read the specific product documentation rather than assuming every subscription works alike. Ask what happens if the company closes, a beneficiary loses their materials, or the plan must change. Keep the answers with the instructions.</p></section><section><h2>Rehearse with fictional information</h2><p>Give your proposed helper a dummy instruction sheet and fictional materials. Ask them to explain the first three actions they would take. Watch for ambiguous words, missing contacts and assumptions about technical knowledge. A confusing rehearsal is useful feedback: simplify the document before anyone needs it in a stressful situation.</p><p>Technical access and legal entitlement are separate matters. Coordinate the technical arrangement with qualified local estate-planning advice, especially when multiple beneficiaries, trustees or jurisdictions are involved. This guide is a practical preparation exercise rather than a legal document or a complete estate plan.</p><p>Review after meaningful life or wallet changes. A moved backup, changed beneficiary, new passphrase or altered signing policy can invalidate yesterday’s instructions. The desired outcome is a short, current route that another person can understand, with enough redundancy to survive ordinary mistakes and enough care to avoid granting unintended access.</p><ul><li>Someone appropriate knows the plan exists.</li><li>The instructions identify every required recovery component.</li><li>A helper has rehearsed with dummy information.</li><li>Technical access and the estate plan have been coordinated.</li></ul></section>"
    },
    {
      "id": "bitcoin-privacy",
      "title": "Your balance is a collection of stories",
      "category": "Privacy",
      "description": "Learn what UTXOs reveal, and make deliberate choices before you spend.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Look beneath the balance",
          "paragraphs": [
            "A wallet’s balance combines the amounts in its unspent transaction outputs, usually shortened to UTXOs. Each output comes from a previous transaction and can later be spent as an input. The interface may show one number, but the underlying pieces can have different histories and different privacy implications.",
            "Imagine receiving one payment from a customer and another from a friend. Combining those outputs in a later transaction can create evidence that they were controlled together. That observation is not absolute proof in every transaction design, but it is a useful reason to understand what your wallet selects."
          ],
          "bullets": []
        },
        {
          "heading": "Label before you forget",
          "paragraphs": [
            "Private labels can help you remember why an output exists. Use descriptions that make sense to you, such as a project name or a spending purpose, rather than relying on memory months later. Keep label backups protected: transaction metadata can be sensitive even when it contains no signing keys.",
            "For a learning exercise, draw three fictional incoming payments and a purchase on paper. Decide which incoming payment should fund the purchase and where the remaining value goes. This small exercise makes the change output easier to recognize when you inspect a real wallet’s transaction preview."
          ],
          "bullets": []
        },
        {
          "heading": "Use coin control deliberately",
          "paragraphs": [
            "Coin control lets you choose which outputs fund a payment. Sparrow’s official FAQ describes selecting outputs in its UTXOs view and using Send Selected. You can inspect the proposed transaction before signing; there is no need to create a real transfer merely to learn the interface.",
            "Check the recipient, the selected inputs, the change destination and the fee. Spending an output consumes it in full; the transaction can return excess value as change. More inputs generally make a transaction larger, so a choice that seems tidy can affect both privacy and cost. Do not consolidate everything simply because fewer rows look cleaner."
          ],
          "bullets": []
        },
        {
          "heading": "Privacy is a routine, not a switch",
          "paragraphs": [
            "Use fresh receiving addresses where your wallet supports them, avoid publishing transaction details unnecessarily, and consider which server learns your wallet queries. Running your own node can reduce reliance on a third-party server, but it does not erase the public transaction graph or remove the need to manage network privacy.",
            "Keep promises modest. Coin control does not make bitcoin anonymous, and one tool cannot undo every earlier disclosure. A useful next step is to review one fictional payment in the transaction lab, identify the information each participant could learn, and write down one habit you want to improve. Repeat the exercise when your wallet or spending pattern changes.",
            "Before changing a real wallet, explain your intended improvement in one sentence. If you cannot identify which disclosure it reduces, pause and learn more. More transactions and more tools do not automatically produce better privacy."
          ],
          "bullets": [
            "Use labels you can understand later.",
            "Inspect inputs and change before signing.",
            "Avoid combining unrelated histories without considering why.",
            "Treat public transaction and wallet metadata as lasting disclosures."
          ]
        }
      ],
      "sources": [
        {
          "title": "Bitcoin developer guide: transactions and UTXOs",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        },
        {
          "title": "Sparrow: coin control FAQ",
          "url": "https://www.sparrowwallet.com/docs/faq.html"
        },
        {
          "title": "Bitcoin.org: privacy practices",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: node and server tradeoffs",
          "url": "https://sparrowwallet.com/docs/best-practices.html"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 437,
      "html": "<section><h2>Look beneath the balance</h2><p>A wallet’s balance combines the amounts in its unspent transaction outputs, usually shortened to UTXOs. Each output comes from a previous transaction and can later be spent as an input. The interface may show one number, but the underlying pieces can have different histories and different privacy implications.</p><p>Imagine receiving one payment from a customer and another from a friend. Combining those outputs in a later transaction can create evidence that they were controlled together. That observation is not absolute proof in every transaction design, but it is a useful reason to understand what your wallet selects.</p></section><section><h2>Label before you forget</h2><p>Private labels can help you remember why an output exists. Use descriptions that make sense to you, such as a project name or a spending purpose, rather than relying on memory months later. Keep label backups protected: transaction metadata can be sensitive even when it contains no signing keys.</p><p>For a learning exercise, draw three fictional incoming payments and a purchase on paper. Decide which incoming payment should fund the purchase and where the remaining value goes. This small exercise makes the change output easier to recognize when you inspect a real wallet’s transaction preview.</p></section><section><h2>Use coin control deliberately</h2><p>Coin control lets you choose which outputs fund a payment. Sparrow’s official FAQ describes selecting outputs in its UTXOs view and using Send Selected. You can inspect the proposed transaction before signing; there is no need to create a real transfer merely to learn the interface.</p><p>Check the recipient, the selected inputs, the change destination and the fee. Spending an output consumes it in full; the transaction can return excess value as change. More inputs generally make a transaction larger, so a choice that seems tidy can affect both privacy and cost. Do not consolidate everything simply because fewer rows look cleaner.</p></section><section><h2>Privacy is a routine, not a switch</h2><p>Use fresh receiving addresses where your wallet supports them, avoid publishing transaction details unnecessarily, and consider which server learns your wallet queries. Running your own node can reduce reliance on a third-party server, but it does not erase the public transaction graph or remove the need to manage network privacy.</p><p>Keep promises modest. Coin control does not make bitcoin anonymous, and one tool cannot undo every earlier disclosure. A useful next step is to review one fictional payment in the transaction lab, identify the information each participant could learn, and write down one habit you want to improve. Repeat the exercise when your wallet or spending pattern changes.</p><p>Before changing a real wallet, explain your intended improvement in one sentence. If you cannot identify which disclosure it reduces, pause and learn more. More transactions and more tools do not automatically produce better privacy.</p><ul><li>Use labels you can understand later.</li><li>Inspect inputs and change before signing.</li><li>Avoid combining unrelated histories without considering why.</li><li>Treat public transaction and wallet metadata as lasting disclosures.</li></ul></section>"
    },
    {
      "id": "multisig-decision",
      "title": "Do you actually need multisig?",
      "category": "Multisig",
      "description": "A decision guide for adding resilience without adding unmanageable complexity.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Name the failure you are trying to survive",
          "paragraphs": [
            "A multisignature wallet requires a specified number of independent keys to approve spending. In a 2-of-3 setup, two valid signers can authorize a transaction. This can distribute responsibility and tolerate the loss of one signer, but the arrangement only helps if the keys and recovery material are genuinely managed as separate failure domains.",
            "Begin with a sentence: “I want my wallet to remain recoverable if this particular thing happens.” Losing a device, losing access to a location and needing another person’s cooperation are different situations. Write down the likely failure before choosing a threshold or buying more hardware."
          ],
          "bullets": []
        },
        {
          "heading": "Count the work, not just the keys",
          "paragraphs": [
            "A new signer adds setup, storage, backup and maintenance work. Every payment also needs the required signers to be available. If you cannot reliably access them, a technically strong policy can become an operational problem. Think about ordinary travel, illness, damaged devices and changes in the people involved.",
            "Make a paper diagram using names such as Signer A, Signer B and Signer C, without keys or precise locations. For each scenario, cross out the unavailable signer and ask whether the remaining people can still complete the intended procedure. Then ask the opposite question: could someone obtain enough authority too easily?"
          ],
          "bullets": []
        },
        {
          "heading": "Back up the map as well as the keys",
          "paragraphs": [
            "Cosigner backups are only part of the recovery story. Preserve the wallet configuration, including the threshold, public keys, derivation information and address or script type. Standards such as BSMS exist to describe and exchange multisig setup information. Use the exports supported by your coordinator and signing devices.",
            "Public wallet configuration cannot normally spend alone, but it can reveal sensitive information about the wallet. Store it accordingly. Test that you can identify and open the correct configuration, and retain a clear description of which signer belongs to which backup. Similar file names are a poor substitute for a documented process."
          ],
          "bullets": []
        },
        {
          "heading": "Prove the workflow before relying on it",
          "paragraphs": [
            "Use a separate practice setup to learn coordination, address verification and signing. Then follow current official instructions for the actual devices and coordinator you select. Verify the wallet policy and receiving address on supported signing devices. Make a small test transaction and a planned recovery rehearsal before treating the arrangement as dependable.",
            "Multisig is an option, not a graduation requirement. A well-understood single-signature wallet can be more appropriate than a threshold arrangement you cannot maintain. If you choose assisted custody, document what the provider can do, what it cannot do, and whether you can recover independently if its service disappears.",
            "A useful decision can be “not yet.” Practice the coordination workflow with dummy material, identify the parts that confuse you, and return to the design after you can describe each participant’s role without referring to a diagram."
          ],
          "bullets": [
            "I can explain the failure multisig addresses.",
            "I have independent signers and clear responsibilities.",
            "I have complete, readable configuration backups.",
            "I can demonstrate spending and recovery."
          ]
        }
      ],
      "sources": [
        {
          "title": "BIP129: secure multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "Sparrow: storage tradeoffs",
          "url": "https://sparrowwallet.com/docs/best-practices.html"
        },
        {
          "title": "Nunchuk: recovery and service dependencies",
          "url": "https://nunchuk.io/faq"
        },
        {
          "title": "BIP380: output script descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 434,
      "html": "<section><h2>Name the failure you are trying to survive</h2><p>A multisignature wallet requires a specified number of independent keys to approve spending. In a 2-of-3 setup, two valid signers can authorize a transaction. This can distribute responsibility and tolerate the loss of one signer, but the arrangement only helps if the keys and recovery material are genuinely managed as separate failure domains.</p><p>Begin with a sentence: “I want my wallet to remain recoverable if this particular thing happens.” Losing a device, losing access to a location and needing another person’s cooperation are different situations. Write down the likely failure before choosing a threshold or buying more hardware.</p></section><section><h2>Count the work, not just the keys</h2><p>A new signer adds setup, storage, backup and maintenance work. Every payment also needs the required signers to be available. If you cannot reliably access them, a technically strong policy can become an operational problem. Think about ordinary travel, illness, damaged devices and changes in the people involved.</p><p>Make a paper diagram using names such as Signer A, Signer B and Signer C, without keys or precise locations. For each scenario, cross out the unavailable signer and ask whether the remaining people can still complete the intended procedure. Then ask the opposite question: could someone obtain enough authority too easily?</p></section><section><h2>Back up the map as well as the keys</h2><p>Cosigner backups are only part of the recovery story. Preserve the wallet configuration, including the threshold, public keys, derivation information and address or script type. Standards such as BSMS exist to describe and exchange multisig setup information. Use the exports supported by your coordinator and signing devices.</p><p>Public wallet configuration cannot normally spend alone, but it can reveal sensitive information about the wallet. Store it accordingly. Test that you can identify and open the correct configuration, and retain a clear description of which signer belongs to which backup. Similar file names are a poor substitute for a documented process.</p></section><section><h2>Prove the workflow before relying on it</h2><p>Use a separate practice setup to learn coordination, address verification and signing. Then follow current official instructions for the actual devices and coordinator you select. Verify the wallet policy and receiving address on supported signing devices. Make a small test transaction and a planned recovery rehearsal before treating the arrangement as dependable.</p><p>Multisig is an option, not a graduation requirement. A well-understood single-signature wallet can be more appropriate than a threshold arrangement you cannot maintain. If you choose assisted custody, document what the provider can do, what it cannot do, and whether you can recover independently if its service disappears.</p><p>A useful decision can be “not yet.” Practice the coordination workflow with dummy material, identify the parts that confuse you, and return to the design after you can describe each participant’s role without referring to a diagram.</p><ul><li>I can explain the failure multisig addresses.</li><li>I have independent signers and clear responsibilities.</li><li>I have complete, readable configuration backups.</li><li>I can demonstrate spending and recovery.</li></ul></section>"
    },
    {
      "id": "lightning-without-surprises",
      "title": "Lightning, without the surprises",
      "category": "Lightning",
      "description": "Understand custody, capacity and costs before your first everyday payment.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Start with the payment you want to make",
          "paragraphs": [
            "Lightning is a way to make bitcoin payments through payment channels. It can make everyday transfers feel quick, but a fast interface does not mean every wallet has the same security model. Before choosing an app, decide whether your priority is occasional spending, receiving regular payments, or operating your own Lightning node.",
            "Then ask three separate questions: who controls the keys, who supplies the infrastructure, and what is required to recover? A provider can help with connectivity or liquidity while you retain keys. Another service may hold the funds on your behalf. The word “Lightning” alone does not tell you which arrangement you are using."
          ],
          "bullets": []
        },
        {
          "heading": "A balance is not the whole story",
          "paragraphs": [
            "Payment channels have directional capacity. Being able to send a certain amount does not automatically mean you can receive that amount. Wallets may manage this complexity for you, but the underlying requirement still exists. Receiving funds can require additional liquidity, and arranging it may involve a cost.",
            "Think about your likely pattern of use. Someone receiving many payments has a different problem from someone who mostly spends. Read how your chosen wallet handles these patterns and what happens when capacity is insufficient. The result may be a quoted fee, a wait, a different payment route or a failed attempt."
          ],
          "bullets": []
        },
        {
          "heading": "Read the complete quote",
          "paragraphs": [
            "Routing fees compensate intermediate Lightning nodes. Depending on the wallet and action, there can also be service charges, swap costs or on-chain fees associated with channel operations. A price quoted in an old tutorial is not a promise about the payment you are making today.",
            "Before confirming, check the destination, amount and full fee shown by your wallet. If the quote is surprising, stop and read what action the wallet is proposing. Do not repeatedly press send on a payment with an uncertain status. Check the wallet’s payment details and the recipient’s confirmation first."
          ],
          "bullets": []
        },
        {
          "heading": "Rehearse the exit as well as the entrance",
          "paragraphs": [
            "Recovery is implementation-specific. For example, Phoenix’s project documentation describes a self-custodial wallet and places responsibility for its recovery phrase with the user. A node operator can have additional channel-backup responsibilities. Do not assume that a procedure written for a normal on-chain wallet also covers every Lightning wallet.",
            "Before committing more to the workflow, find the current backup and recovery instructions and understand how funds can return to an on-chain wallet. Your learning exercise is complete when you can explain both a normal payment and a failure case. Start with a small spending budget that fits your own circumstances, and grow your knowledge before increasing operational complexity.",
            "Keep a short learning log with the type of operation, the quoted fee and what happened. Use fictional amounts in any shared notes. Over time, this makes it easier to recognize routine behavior and identify an unusual request."
          ],
          "bullets": [
            "Confirm the custody model.",
            "Check receiving capacity and any liquidity charge.",
            "Review the total fee and payment status.",
            "Understand recovery and your on-chain exit."
          ]
        }
      ],
      "sources": [
        {
          "title": "ACINQ: Phoenix project and backup responsibility",
          "url": "https://github.com/ACINQ/phoenix"
        },
        {
          "title": "Lightning Labs: channel fees",
          "url": "https://docs.lightning.engineering/the-lightning-network/pathfinding/channel-fees"
        },
        {
          "title": "Lightning Labs: managing liquidity",
          "url": "https://docs.lightning.engineering/the-lightning-network/liquidity/manage-liquidity"
        },
        {
          "title": "Lightning Labs: Loop",
          "url": "https://lightning.engineering/loop/"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 442,
      "html": "<section><h2>Start with the payment you want to make</h2><p>Lightning is a way to make bitcoin payments through payment channels. It can make everyday transfers feel quick, but a fast interface does not mean every wallet has the same security model. Before choosing an app, decide whether your priority is occasional spending, receiving regular payments, or operating your own Lightning node.</p><p>Then ask three separate questions: who controls the keys, who supplies the infrastructure, and what is required to recover? A provider can help with connectivity or liquidity while you retain keys. Another service may hold the funds on your behalf. The word “Lightning” alone does not tell you which arrangement you are using.</p></section><section><h2>A balance is not the whole story</h2><p>Payment channels have directional capacity. Being able to send a certain amount does not automatically mean you can receive that amount. Wallets may manage this complexity for you, but the underlying requirement still exists. Receiving funds can require additional liquidity, and arranging it may involve a cost.</p><p>Think about your likely pattern of use. Someone receiving many payments has a different problem from someone who mostly spends. Read how your chosen wallet handles these patterns and what happens when capacity is insufficient. The result may be a quoted fee, a wait, a different payment route or a failed attempt.</p></section><section><h2>Read the complete quote</h2><p>Routing fees compensate intermediate Lightning nodes. Depending on the wallet and action, there can also be service charges, swap costs or on-chain fees associated with channel operations. A price quoted in an old tutorial is not a promise about the payment you are making today.</p><p>Before confirming, check the destination, amount and full fee shown by your wallet. If the quote is surprising, stop and read what action the wallet is proposing. Do not repeatedly press send on a payment with an uncertain status. Check the wallet’s payment details and the recipient’s confirmation first.</p></section><section><h2>Rehearse the exit as well as the entrance</h2><p>Recovery is implementation-specific. For example, Phoenix’s project documentation describes a self-custodial wallet and places responsibility for its recovery phrase with the user. A node operator can have additional channel-backup responsibilities. Do not assume that a procedure written for a normal on-chain wallet also covers every Lightning wallet.</p><p>Before committing more to the workflow, find the current backup and recovery instructions and understand how funds can return to an on-chain wallet. Your learning exercise is complete when you can explain both a normal payment and a failure case. Start with a small spending budget that fits your own circumstances, and grow your knowledge before increasing operational complexity.</p><p>Keep a short learning log with the type of operation, the quoted fee and what happened. Use fictional amounts in any shared notes. Over time, this makes it easier to recognize routine behavior and identify an unusual request.</p><ul><li>Confirm the custody model.</li><li>Check receiving capacity and any liquidity charge.</li><li>Review the total fee and payment status.</li><li>Understand recovery and your on-chain exit.</li></ul></section>"
    },
    {
      "id": "recovery-rehearsal",
      "title": "A backup is a plan you have tested",
      "category": "Security",
      "description": "Rehearse recovery without turning an ordinary check into an emergency.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Define what the rehearsal proves",
          "paragraphs": [
            "A written backup is reassuring, but a useful test answers a specific question: can this material recover the wallet I expect? There are several separate checks. You might be testing whether the words are correct, whether a passphrase opens the right wallet, whether the wallet configuration is complete, or whether another person can follow your instructions.",
            "Do the smallest test that answers the question. A supported dry-run backup check is often a sensible first step. It avoids deliberately destroying your working setup. Read the instructions for your exact device before starting, and do not erase your only functioning signer just to see what happens."
          ],
          "bullets": []
        },
        {
          "heading": "Make a recovery inventory",
          "paragraphs": [
            "Record the wallet application, backup standard, account or address type, and whether an extra passphrase is required. A multisignature wallet also needs its wallet configuration, including the spending policy and cosigner public information. A label saying “Bitcoin backup” is less useful than a clear explanation of which wallet the material belongs to.",
            "Keep the inventory separate from the secrets. It should tell you what exists and how to find authorized instructions, not become a second copy of every key. If you use several accounts or wallet types, include each in the scope of the test. Restoring one address does not automatically demonstrate recovery of everything you own."
          ],
          "bullets": []
        },
        {
          "heading": "Choose the right level of testing",
          "paragraphs": [
            "A device’s backup-check function can confirm that its stored secret matches the recovery material. It may not test optional passphrases or additional wallet configurations. For a passphrase wallet, use the project’s documented verification process and compare a known receive address. Never paste a real seed or passphrase into a website to check it.",
            "A fuller recovery rehearsal can use a suitable spare device and the manufacturer’s procedure. Plan where the device and backup will be handled, how you will verify the resulting wallet, and how the spare will be secured afterwards. A spare restored signer contains spending authority; treat it as such."
          ],
          "bullets": []
        },
        {
          "heading": "Write down the result, not the secret",
          "paragraphs": [
            "Your record might say: “Checked backup on 12 November; passphrase wallet matched the expected address; configuration export readable.” If the test fails, keep the existing working setup intact while you investigate the exact mismatch. Avoid repeated improvisation or following recovery instructions from someone who contacts you unexpectedly.",
            "Revisit the plan after meaningful changes: a new wallet, changed passphrase, altered multisig policy, moved backup location or a change in the person expected to help. There is no prize for checking constantly. The point is a current, understandable recovery process that reduces uncertainty when a device breaks.",
            "Set aside uninterrupted time for the exercise. Stop if you feel rushed or cannot explain the next action. Recovery practice is most valuable when it replaces assumptions with specific, recorded observations."
          ],
          "bullets": [
            "Identify the wallet and the question being tested.",
            "Use the supported check before considering a reset.",
            "Verify the expected wallet, not just valid-looking words.",
            "Record the date, result and next action without secrets."
          ]
        }
      ],
      "sources": [
        {
          "title": "Trezor: backup and recovery troubleshooting",
          "url": "https://trezor.io/support/troubleshooting/trezor-suite-issues/troubleshoot-wallet-backup-and-recovery-problems"
        },
        {
          "title": "Trezor: passphrase wallet verification",
          "url": "https://trezor.io/guides/trezor-suite/using-a-passphrase-wallet-in-trezor-suite"
        },
        {
          "title": "Bitcoin Core: managing wallets",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/managing-wallets.md"
        },
        {
          "title": "BIP129: secure multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 439,
      "html": "<section><h2>Define what the rehearsal proves</h2><p>A written backup is reassuring, but a useful test answers a specific question: can this material recover the wallet I expect? There are several separate checks. You might be testing whether the words are correct, whether a passphrase opens the right wallet, whether the wallet configuration is complete, or whether another person can follow your instructions.</p><p>Do the smallest test that answers the question. A supported dry-run backup check is often a sensible first step. It avoids deliberately destroying your working setup. Read the instructions for your exact device before starting, and do not erase your only functioning signer just to see what happens.</p></section><section><h2>Make a recovery inventory</h2><p>Record the wallet application, backup standard, account or address type, and whether an extra passphrase is required. A multisignature wallet also needs its wallet configuration, including the spending policy and cosigner public information. A label saying “Bitcoin backup” is less useful than a clear explanation of which wallet the material belongs to.</p><p>Keep the inventory separate from the secrets. It should tell you what exists and how to find authorized instructions, not become a second copy of every key. If you use several accounts or wallet types, include each in the scope of the test. Restoring one address does not automatically demonstrate recovery of everything you own.</p></section><section><h2>Choose the right level of testing</h2><p>A device’s backup-check function can confirm that its stored secret matches the recovery material. It may not test optional passphrases or additional wallet configurations. For a passphrase wallet, use the project’s documented verification process and compare a known receive address. Never paste a real seed or passphrase into a website to check it.</p><p>A fuller recovery rehearsal can use a suitable spare device and the manufacturer’s procedure. Plan where the device and backup will be handled, how you will verify the resulting wallet, and how the spare will be secured afterwards. A spare restored signer contains spending authority; treat it as such.</p></section><section><h2>Write down the result, not the secret</h2><p>Your record might say: “Checked backup on 12 November; passphrase wallet matched the expected address; configuration export readable.” If the test fails, keep the existing working setup intact while you investigate the exact mismatch. Avoid repeated improvisation or following recovery instructions from someone who contacts you unexpectedly.</p><p>Revisit the plan after meaningful changes: a new wallet, changed passphrase, altered multisig policy, moved backup location or a change in the person expected to help. There is no prize for checking constantly. The point is a current, understandable recovery process that reduces uncertainty when a device breaks.</p><p>Set aside uninterrupted time for the exercise. Stop if you feel rushed or cannot explain the next action. Recovery practice is most valuable when it replaces assumptions with specific, recorded observations.</p><ul><li>Identify the wallet and the question being tested.</li><li>Use the supported check before considering a reset.</li><li>Verify the expected wallet, not just valid-looking words.</li><li>Record the date, result and next action without secrets.</li></ul></section>"
    },
    {
      "id": "first-self-custody",
      "title": "Your first self-custody weekend",
      "category": "Wallets",
      "description": "A calm, practical route from a balance on a screen to a wallet you understand.",
      "minutes": 4,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Start with an outcome, not a shopping list",
          "paragraphs": [
            "Your first goal is modest: understand who can authorize a payment, know how your backup works, and recognize the address you intend to receive into. You do not need every privacy tool or the most elaborate signing setup to begin. A system you can explain and recover is a better starting point than a complicated system you only partly understand.",
            "This is a learning plan, not a recommendation to move a particular amount. Work with an empty practice wallet first. When you are ready for a real transaction, choose an amount whose loss would not materially affect you and account for the fees involved. Keep your existing access until the new workflow makes sense."
          ],
          "bullets": []
        },
        {
          "heading": "Choose by responsibility",
          "paragraphs": [
            "A custodial account delegates key control to its operator. Self-custody puts that responsibility with you. A mobile software wallet may be convenient for spending; a hardware signing device keeps signing keys in a separate environment. Neither label removes the need to understand recovery, updates and the information shown before you approve a transaction.",
            "Read the wallet project’s own setup and backup documentation. Reach its download page through a known official address, rather than a sponsored search result or an unsolicited support message. If the project provides signed releases, follow its verification procedure. Device models and menu labels change, so use instructions for the exact product in front of you."
          ],
          "bullets": []
        },
        {
          "heading": "Separate the things people call passwords",
          "paragraphs": [
            "A device PIN, an application password, a recovery phrase and an optional wallet passphrase can have different jobs. Do not assume that knowing one replaces the others. Write down the recovery requirements in plain language without putting the secrets themselves into this website, a chat, or a shared document.",
            "A BIP39 passphrase creates a different wallet in combination with the recovery words. A typo can produce a perfectly valid but empty wallet. Adding one is a deliberate recovery decision, not a mandatory beginner setting. Use the backup format your wallet actually supports; not every wallet backup is BIP39."
          ],
          "bullets": []
        },
        {
          "heading": "Finish with a small rehearsal",
          "paragraphs": [
            "First use the manufacturer’s supported backup-check procedure. Then verify a receiving address through the signing device where supported, compare the full address and review the amount and fee before approving a small practice payment. Make a simple private note of what each screen meant and where the official recovery instructions are.",
            "At the end of the weekend, you should be able to describe the complete process aloud. If a step still feels mysterious, pause there. Successful self-custody is a repeatable routine, and your next task is to make that routine easier to follow under pressure.",
            "A useful final question is: could I repeat these steps next month without this tab open? If the answer is no, improve your private instructions before adding another feature."
          ],
          "bullets": [
            "I know which device or person controls spending.",
            "I understand my exact backup requirements.",
            "I can verify a receiving address independently.",
            "I have a recovery plan I have rehearsed safely."
          ]
        }
      ],
      "sources": [
        {
          "title": "Bitcoin.org: securing your wallet",
          "url": "https://bitcoin.org/en/secure-your-wallet"
        },
        {
          "title": "Sparrow: quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Trezor: passphrase wallets",
          "url": "https://trezor.io/guides/trezor-suite/using-a-passphrase-wallet-in-trezor-suite"
        },
        {
          "title": "BIP39: mnemonic code",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "words": 445,
      "html": "<section><h2>Start with an outcome, not a shopping list</h2><p>Your first goal is modest: understand who can authorize a payment, know how your backup works, and recognize the address you intend to receive into. You do not need every privacy tool or the most elaborate signing setup to begin. A system you can explain and recover is a better starting point than a complicated system you only partly understand.</p><p>This is a learning plan, not a recommendation to move a particular amount. Work with an empty practice wallet first. When you are ready for a real transaction, choose an amount whose loss would not materially affect you and account for the fees involved. Keep your existing access until the new workflow makes sense.</p></section><section><h2>Choose by responsibility</h2><p>A custodial account delegates key control to its operator. Self-custody puts that responsibility with you. A mobile software wallet may be convenient for spending; a hardware signing device keeps signing keys in a separate environment. Neither label removes the need to understand recovery, updates and the information shown before you approve a transaction.</p><p>Read the wallet project’s own setup and backup documentation. Reach its download page through a known official address, rather than a sponsored search result or an unsolicited support message. If the project provides signed releases, follow its verification procedure. Device models and menu labels change, so use instructions for the exact product in front of you.</p></section><section><h2>Separate the things people call passwords</h2><p>A device PIN, an application password, a recovery phrase and an optional wallet passphrase can have different jobs. Do not assume that knowing one replaces the others. Write down the recovery requirements in plain language without putting the secrets themselves into this website, a chat, or a shared document.</p><p>A BIP39 passphrase creates a different wallet in combination with the recovery words. A typo can produce a perfectly valid but empty wallet. Adding one is a deliberate recovery decision, not a mandatory beginner setting. Use the backup format your wallet actually supports; not every wallet backup is BIP39.</p></section><section><h2>Finish with a small rehearsal</h2><p>First use the manufacturer’s supported backup-check procedure. Then verify a receiving address through the signing device where supported, compare the full address and review the amount and fee before approving a small practice payment. Make a simple private note of what each screen meant and where the official recovery instructions are.</p><p>At the end of the weekend, you should be able to describe the complete process aloud. If a step still feels mysterious, pause there. Successful self-custody is a repeatable routine, and your next task is to make that routine easier to follow under pressure.</p><p>A useful final question is: could I repeat these steps next month without this tab open? If the answer is no, improve your private instructions before adding another feature.</p><ul><li>I know which device or person controls spending.</li><li>I understand my exact backup requirements.</li><li>I can verify a receiving address independently.</li><li>I have a recovery plan I have rehearsed safely.</li></ul></section>"
    },
    {
      "id": "sparrow-2026",
      "title": "Sparrow: build a wallet you can inspect",
      "category": "Wallets",
      "description": "A current workflow for choosing a connection, pairing a signer and reviewing every payment.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Choose the job before creating a wallet",
          "paragraphs": [
            "Sparrow is a desktop Bitcoin wallet that makes transaction details visible. It can hold software keys, coordinate hardware signers, or watch a wallet without holding its private keys. Decide which role you want before starting. A watch-only setup for a hardware device should receive public wallet information, not the device’s recovery words.",
            "This guide is a preparation and review workflow. It deliberately avoids asking you to move funds while learning. Open the official documentation for the product and operating system you use. Older screenshots in the archive remain useful context, but they are not evidence that every menu, integration or device instruction is still current."
          ],
          "bullets": []
        },
        {
          "heading": "Install and choose your connection",
          "paragraphs": [
            "Download the correct installer and its verification files from Sparrow’s official download page. Complete the project’s signature and checksum procedure before opening the installer. An existing trusted Sparrow installation can use its Verify Download tool; a fresh installation should follow the documented bootstrap verification procedure.",
            "Next choose the server connection. A public Electrum server is convenient but learns information about the wallet queries it serves. Your own Bitcoin Core or private Electrum server gives you a different trust and privacy arrangement. Choose deliberately, and record which connection you selected so that a later change is visible rather than accidental."
          ],
          "bullets": []
        },
        {
          "heading": "Pair a signer and verify the wallet",
          "paragraphs": [
            "Create the intended wallet policy and import the supported public export from your signing device. Match the account and script type to the device’s instructions. Export formats are not interchangeable merely because they contain a QR code. Check the resulting wallet fingerprint or identifying information, and verify a receive address on the signer where supported.",
            "For multisig, every signer needs the complete intended policy. A coordinator’s attractive interface does not replace checking the threshold and cosigners. Keep the wallet configuration export with your recovery plan. Public configuration can reveal your wallet history, so treat it as private even though it is not normally sufficient to sign a payment."
          ],
          "bullets": []
        },
        {
          "heading": "Learn the transaction preview",
          "paragraphs": [
            "Inspect the UTXOs view to understand the separate outputs behind the total balance. Add useful private labels before the history becomes difficult to remember. Sparrow’s coin-control workflow lets you select particular outputs and choose Send Selected. The unsigned preview is a good place to learn without approving a payment.",
            "Check the destination, amount, fee, selected inputs and change. On a real payment, the signing device is the approval point: compare what it displays with your intent. Return the signed transaction to the coordinator only after those checks. Broadcasting and signing are separate actions; learn how the application represents each stage."
          ],
          "bullets": []
        },
        {
          "heading": "Finish with a recovery record",
          "paragraphs": [
            "Keep a short record of the application, wallet policy, account information, signing device and backup method. Use a supported backup check or an appropriately planned spare-device rehearsal rather than wiping your only working signer. Store labels and wallet metadata securely, since reconstructing addresses does not necessarily recover your explanations of them.",
            "Sparrow removed the Whirlpool client in version 1.9.0. A historical tutorial showing that tab is not a current mixing setup guide. The skills to carry forward are installation verification, explicit server choice, address verification and deliberate transaction review. When any of those fails, stop and resolve that specific mismatch before signing."
          ],
          "bullets": [
            "Identify whether the wallet can sign or only watch.",
            "Verify the download and server choice.",
            "Verify the receive address on the signer.",
            "Review inputs, change and fees before approval."
          ]
        }
      ],
      "sources": [
        {
          "title": "Sparrow download verification",
          "url": "https://sparrowwallet.com/download/"
        },
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow FAQ",
          "url": "https://sparrowwallet.com/docs/faq.html"
        },
        {
          "title": "BIP174: partially signed transactions",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki"
        },
        {
          "title": "BIP129: secure multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "Sparrow 1.9.0 release",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Choose the job before creating a wallet</h2>\n<p>Sparrow is a desktop Bitcoin wallet that makes transaction details visible. It can hold software keys, coordinate hardware signers, or watch a wallet without holding its private keys. Decide which role you want before starting. A watch-only setup for a hardware device should receive public wallet information, not the device’s recovery words.</p>\n<p>This guide is a preparation and review workflow. It deliberately avoids asking you to move funds while learning. Open the official documentation for the product and operating system you use. Older screenshots in the archive remain useful context, but they are not evidence that every menu, integration or device instruction is still current.</p>\n<h2 id=\"section-1\">Install and choose your connection</h2>\n<p>Download the correct installer and its verification files from Sparrow’s official download page. Complete the project’s signature and checksum procedure before opening the installer. An existing trusted Sparrow installation can use its Verify Download tool; a fresh installation should follow the documented bootstrap verification procedure.</p>\n<p>Next choose the server connection. A public Electrum server is convenient but learns information about the wallet queries it serves. Your own Bitcoin Core or private Electrum server gives you a different trust and privacy arrangement. Choose deliberately, and record which connection you selected so that a later change is visible rather than accidental.</p>\n<h2 id=\"section-2\">Pair a signer and verify the wallet</h2>\n<p>Create the intended wallet policy and import the supported public export from your signing device. Match the account and script type to the device’s instructions. Export formats are not interchangeable merely because they contain a QR code. Check the resulting wallet fingerprint or identifying information, and verify a receive address on the signer where supported.</p>\n<p>For multisig, every signer needs the complete intended policy. A coordinator’s attractive interface does not replace checking the threshold and cosigners. Keep the wallet configuration export with your recovery plan. Public configuration can reveal your wallet history, so treat it as private even though it is not normally sufficient to sign a payment.</p>\n<h2 id=\"section-3\">Learn the transaction preview</h2>\n<p>Inspect the UTXOs view to understand the separate outputs behind the total balance. Add useful private labels before the history becomes difficult to remember. Sparrow’s coin-control workflow lets you select particular outputs and choose Send Selected. The unsigned preview is a good place to learn without approving a payment.</p>\n<p>Check the destination, amount, fee, selected inputs and change. On a real payment, the signing device is the approval point: compare what it displays with your intent. Return the signed transaction to the coordinator only after those checks. Broadcasting and signing are separate actions; learn how the application represents each stage.</p>\n<h2 id=\"section-4\">Finish with a recovery record</h2>\n<p>Keep a short record of the application, wallet policy, account information, signing device and backup method. Use a supported backup check or an appropriately planned spare-device rehearsal rather than wiping your only working signer. Store labels and wallet metadata securely, since reconstructing addresses does not necessarily recover your explanations of them.</p>\n<p>Sparrow removed the Whirlpool client in version 1.9.0. A historical tutorial showing that tab is not a current mixing setup guide. The skills to carry forward are installation verification, explicit server choice, address verification and deliberate transaction review. When any of those fails, stop and resolve that specific mismatch before signing.</p>\n<ul><li>Identify whether the wallet can sign or only watch.</li><li>Verify the download and server choice.</li><li>Verify the receive address on the signer.</li><li>Review inputs, change and fees before approval.</li></ul>",
      "words": 571
    },
    {
      "id": "bluewallet-2026",
      "title": "BlueWallet: a clearer everyday wallet",
      "category": "Wallets",
      "description": "Separate on-chain spending, watch-only access and Lightning before you set up.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Pick the wallet type you actually need",
          "paragraphs": [
            "BlueWallet can show several wallets inside one application. That makes it important to identify each one’s role. An on-chain software wallet holds signing authority on the phone. A watch-only wallet observes public information and can prepare transactions, but relies on another signer. A multisig vault has its own policy and recovery requirements.",
            "Write a short purpose for each wallet you create, such as everyday spending or watching a hardware account. Resist adding every available option on the first day. A small number of clearly named wallets is easier to back up, inspect and explain than a collection whose different security assumptions have been forgotten."
          ],
          "bullets": []
        },
        {
          "heading": "Create and back up the on-chain wallet",
          "paragraphs": [
            "Use the official BlueWallet website to find the correct distribution for your device. In the documented creation flow, add a wallet and select Bitcoin for an ordinary on-chain wallet. Read the generated backup instructions before receiving funds. Make the backup private and offline; the site you are reading does not need to see it.",
            "Each BlueWallet wallet has its own backup. There is not one universal export covering every wallet in the app. Open the relevant wallet’s options and use its Export/Backup function. Different wallet types may export different material, so label your private recovery records with the type of wallet they recover."
          ],
          "bullets": []
        },
        {
          "heading": "Use watch-only access intentionally",
          "paragraphs": [
            "For a hardware wallet, import the supported public wallet export rather than the seed. This lets the phone act as a coordinator while the signing device retains spending authority. Follow the exact pairing instructions for both products, then confirm that the wallet shown on the phone is the account you intended.",
            "A watch-only wallet is not a spending backup. Losing the signer and its recovery material cannot be repaired by a screen that still shows a balance. Conversely, public wallet information can expose transaction history even though it cannot spend. Avoid sharing screenshots, exports or QR codes casually just because they are described as public."
          ],
          "bullets": []
        },
        {
          "heading": "Receive, inspect, then spend",
          "paragraphs": [
            "When receiving, use a fresh address where supported and verify it on the hardware device if that is your signing arrangement. For a payment, review the complete recipient address, amount and fee before approval. If you use an external signer, the unsigned transaction goes to that signer and the completed result returns for broadcast.",
            "Learn what the wallet’s pending and confirmed states mean before treating a payment as finished. A transaction awaiting inclusion is not necessarily broken. Use the application’s documented transaction controls and investigate its current state before repeating a payment. If a recipient reports a mismatch, compare the transaction details rather than creating another transfer immediately."
          ],
          "bullets": []
        },
        {
          "heading": "Understand the Lightning boundary",
          "paragraphs": [
            "BlueWallet’s hosted Lndhub.io service was retired in 2023. Current Lightning use connects to an LNDHub arrangement you supply; an old tutorial that assumes the hosted service is not a current onboarding path. The operator of that LNDHub and its backup credentials introduce a separate custody and recovery model from an ordinary on-chain wallet.",
            "Finish your setup by listing the wallet types you use and their separate recovery requirements. Then test your understanding with fictional scenarios: the phone is lost, the hardware signer is unavailable, or the node cannot be reached. The answer should come from your documented setup rather than from the fact that all three balances happen to appear in the same app."
          ],
          "bullets": [
            "Back up every wallet separately.",
            "Distinguish a public export from spending authority.",
            "Check the payment details before signing.",
            "Treat LNDHub as a separate service dependency."
          ]
        }
      ],
      "sources": [
        {
          "title": "BlueWallet support",
          "url": "https://bluewallet.io/docs/"
        },
        {
          "title": "BlueWallet wallet backups",
          "url": "https://bluewallet.io/docs/backup-wallet/"
        },
        {
          "title": "Create a Bitcoin wallet in BlueWallet",
          "url": "https://bluewallet.io/docs/create-bitcoin-wallet/"
        },
        {
          "title": "BlueWallet multisig vaults",
          "url": "https://bluewallet.io/docs/multisig-wallet/"
        },
        {
          "title": "BlueWallet Lndhub.io retirement",
          "url": "https://bluewallet.io/sunsetting-lndhub/"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Pick the wallet type you actually need</h2>\n<p>BlueWallet can show several wallets inside one application. That makes it important to identify each one’s role. An on-chain software wallet holds signing authority on the phone. A watch-only wallet observes public information and can prepare transactions, but relies on another signer. A multisig vault has its own policy and recovery requirements.</p>\n<p>Write a short purpose for each wallet you create, such as everyday spending or watching a hardware account. Resist adding every available option on the first day. A small number of clearly named wallets is easier to back up, inspect and explain than a collection whose different security assumptions have been forgotten.</p>\n<h2 id=\"section-1\">Create and back up the on-chain wallet</h2>\n<p>Use the official BlueWallet website to find the correct distribution for your device. In the documented creation flow, add a wallet and select Bitcoin for an ordinary on-chain wallet. Read the generated backup instructions before receiving funds. Make the backup private and offline; the site you are reading does not need to see it.</p>\n<p>Each BlueWallet wallet has its own backup. There is not one universal export covering every wallet in the app. Open the relevant wallet’s options and use its Export/Backup function. Different wallet types may export different material, so label your private recovery records with the type of wallet they recover.</p>\n<h2 id=\"section-2\">Use watch-only access intentionally</h2>\n<p>For a hardware wallet, import the supported public wallet export rather than the seed. This lets the phone act as a coordinator while the signing device retains spending authority. Follow the exact pairing instructions for both products, then confirm that the wallet shown on the phone is the account you intended.</p>\n<p>A watch-only wallet is not a spending backup. Losing the signer and its recovery material cannot be repaired by a screen that still shows a balance. Conversely, public wallet information can expose transaction history even though it cannot spend. Avoid sharing screenshots, exports or QR codes casually just because they are described as public.</p>\n<h2 id=\"section-3\">Receive, inspect, then spend</h2>\n<p>When receiving, use a fresh address where supported and verify it on the hardware device if that is your signing arrangement. For a payment, review the complete recipient address, amount and fee before approval. If you use an external signer, the unsigned transaction goes to that signer and the completed result returns for broadcast.</p>\n<p>Learn what the wallet’s pending and confirmed states mean before treating a payment as finished. A transaction awaiting inclusion is not necessarily broken. Use the application’s documented transaction controls and investigate its current state before repeating a payment. If a recipient reports a mismatch, compare the transaction details rather than creating another transfer immediately.</p>\n<h2 id=\"section-4\">Understand the Lightning boundary</h2>\n<p>BlueWallet’s hosted Lndhub.io service was retired in 2023. Current Lightning use connects to an LNDHub arrangement you supply; an old tutorial that assumes the hosted service is not a current onboarding path. The operator of that LNDHub and its backup credentials introduce a separate custody and recovery model from an ordinary on-chain wallet.</p>\n<p>Finish your setup by listing the wallet types you use and their separate recovery requirements. Then test your understanding with fictional scenarios: the phone is lost, the hardware signer is unavailable, or the node cannot be reached. The answer should come from your documented setup rather than from the fact that all three balances happen to appear in the same app.</p>\n<ul><li>Back up every wallet separately.</li><li>Distinguish a public export from spending authority.</li><li>Check the payment details before signing.</li><li>Treat LNDHub as a separate service dependency.</li></ul>",
      "words": 585
    },
    {
      "id": "passport-2026",
      "title": "Passport: start with the right model",
      "category": "Wallets",
      "description": "A practical setup and recovery map for Passport Core and Passport Prime.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Model names matter",
          "paragraphs": [
            "Foundation documents Passport Core and Passport Prime separately. They have different interfaces and backup workflows, so a tutorial titled simply “Passport” is not enough to identify the right procedure. Start by checking the exact model in front of you and opening its own setup guide from Foundation’s documentation hub.",
            "The archived article describes an earlier product experience. Preserve it for context, but do not use a familiar-looking photograph to infer that the same buttons or recovery materials apply to a different model. This guide explains the decisions you should make; the manufacturer’s current model-specific instructions supply the precise device steps."
          ],
          "bullets": []
        },
        {
          "heading": "Establish device and software authenticity",
          "paragraphs": [
            "For Passport Core, the official setup sequence covers packaging checks, supply-chain validation, a PIN and firmware updates before seed setup. Follow those checks in order. If validation fails or packaging differs unexpectedly, pause and contact Foundation through a verified official channel rather than improvising around the warning.",
            "Install the companion software through Foundation’s published links and follow the supported firmware procedure for your model. Keep the distinction between device authentication and software verification clear: they answer related but different questions. Record the model and installed software versions in a non-secret maintenance note so you can find the appropriate instructions later."
          ],
          "bullets": []
        },
        {
          "heading": "Understand what your backup needs",
          "paragraphs": [
            "Passport Core supports an encrypted microSD backup and seed-word recovery. The encrypted backup includes device information and requires its Backup Code; the card alone is not the complete recovery method. Foundation documents a 20-digit code for this Core workflow and recommends separating the code from the encrypted media.",
            "Passport Prime has its own documentation for backups and keycards. Do not substitute the Core card-and-code procedure for Prime’s recovery plan. In either case, distinguish the device PIN from the recovery materials. A PIN protects access to a device; it is not a universal replacement for the information needed when that device is lost."
          ],
          "bullets": []
        },
        {
          "heading": "Connect a coordinator without moving the secret",
          "paragraphs": [
            "A companion wallet displays balances and prepares transactions. In a normal hardware-signing arrangement, it receives the supported public wallet information while the device holds the signing keys. Foundation provides connection guides for Envoy and several third-party coordinators. Choose one supported combination and finish that workflow before experimenting with others.",
            "Confirm the intended account and verify a receiving address through the hardware device where supported. If you later add multisig, treat it as a new wallet policy with additional configuration backups. A QR transfer is merely a transport mechanism; you still need to know whether it represents public wallet information, a transaction or sensitive backup material."
          ],
          "bullets": []
        },
        {
          "heading": "Rehearse and maintain the arrangement",
          "paragraphs": [
            "Before relying on the wallet, write down the recovery components without copying the secrets into a shared checklist. Use the manufacturer’s recovery checklist to identify what would be needed after loss of the device, loss of the phone, or damage to the backup medium. A useful private record also identifies any optional passphrase and additional accounts.",
            "Rehearse with the supported checking procedure or a carefully planned spare device. Avoid erasing your only functioning signer during an ordinary learning exercise. Finish with a small, clearly understood transaction only when you are comfortable with the whole flow, including the fee and address verification. A successful setup is one you can explain later without relying on the original packaging or a memory of a video."
          ],
          "bullets": [
            "Identify Core or Prime before following a tutorial.",
            "Complete the model-specific authenticity checks.",
            "Know every component required by your backup.",
            "Verify accounts and addresses during pairing."
          ]
        }
      ],
      "sources": [
        {
          "title": "Passport Core setup",
          "url": "https://docs.foundation.xyz/passport/setup/"
        },
        {
          "title": "Passport Core backups",
          "url": "https://docs.foundation.xyz/backups/passport-core/"
        },
        {
          "title": "Passport Prime documentation",
          "url": "https://docs.foundation.xyz/prime/home/"
        },
        {
          "title": "Passport Core wallet connections",
          "url": "https://docs.foundation.xyz/passport/connect/"
        },
        {
          "title": "Foundation recovery checklist",
          "url": "https://docs.foundation.xyz/backups/recovery/"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Model names matter</h2>\n<p>Foundation documents Passport Core and Passport Prime separately. They have different interfaces and backup workflows, so a tutorial titled simply “Passport” is not enough to identify the right procedure. Start by checking the exact model in front of you and opening its own setup guide from Foundation’s documentation hub.</p>\n<p>The archived article describes an earlier product experience. Preserve it for context, but do not use a familiar-looking photograph to infer that the same buttons or recovery materials apply to a different model. This guide explains the decisions you should make; the manufacturer’s current model-specific instructions supply the precise device steps.</p>\n<h2 id=\"section-1\">Establish device and software authenticity</h2>\n<p>For Passport Core, the official setup sequence covers packaging checks, supply-chain validation, a PIN and firmware updates before seed setup. Follow those checks in order. If validation fails or packaging differs unexpectedly, pause and contact Foundation through a verified official channel rather than improvising around the warning.</p>\n<p>Install the companion software through Foundation’s published links and follow the supported firmware procedure for your model. Keep the distinction between device authentication and software verification clear: they answer related but different questions. Record the model and installed software versions in a non-secret maintenance note so you can find the appropriate instructions later.</p>\n<h2 id=\"section-2\">Understand what your backup needs</h2>\n<p>Passport Core supports an encrypted microSD backup and seed-word recovery. The encrypted backup includes device information and requires its Backup Code; the card alone is not the complete recovery method. Foundation documents a 20-digit code for this Core workflow and recommends separating the code from the encrypted media.</p>\n<p>Passport Prime has its own documentation for backups and keycards. Do not substitute the Core card-and-code procedure for Prime’s recovery plan. In either case, distinguish the device PIN from the recovery materials. A PIN protects access to a device; it is not a universal replacement for the information needed when that device is lost.</p>\n<h2 id=\"section-3\">Connect a coordinator without moving the secret</h2>\n<p>A companion wallet displays balances and prepares transactions. In a normal hardware-signing arrangement, it receives the supported public wallet information while the device holds the signing keys. Foundation provides connection guides for Envoy and several third-party coordinators. Choose one supported combination and finish that workflow before experimenting with others.</p>\n<p>Confirm the intended account and verify a receiving address through the hardware device where supported. If you later add multisig, treat it as a new wallet policy with additional configuration backups. A QR transfer is merely a transport mechanism; you still need to know whether it represents public wallet information, a transaction or sensitive backup material.</p>\n<h2 id=\"section-4\">Rehearse and maintain the arrangement</h2>\n<p>Before relying on the wallet, write down the recovery components without copying the secrets into a shared checklist. Use the manufacturer’s recovery checklist to identify what would be needed after loss of the device, loss of the phone, or damage to the backup medium. A useful private record also identifies any optional passphrase and additional accounts.</p>\n<p>Rehearse with the supported checking procedure or a carefully planned spare device. Avoid erasing your only functioning signer during an ordinary learning exercise. Finish with a small, clearly understood transaction only when you are comfortable with the whole flow, including the fee and address verification. A successful setup is one you can explain later without relying on the original packaging or a memory of a video.</p>\n<ul><li>Identify Core or Prime before following a tutorial.</li><li>Complete the model-specific authenticity checks.</li><li>Know every component required by your backup.</li><li>Verify accounts and addresses during pairing.</li></ul>",
      "words": 580
    },
    {
      "id": "verify-downloads-2026",
      "title": "Verify the software before you trust it",
      "category": "Security",
      "description": "Learn the difference between a matching file, a valid signature and a trusted signer.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Three questions, three separate checks",
          "paragraphs": [
            "Before installing Bitcoin software, ask whether you downloaded the intended product, whether the file matches the release record, and whether that record was signed by the expected developer. A checksum answers a file-integrity question. A signature connects data to a signing key. Establishing whose key it is remains a separate step.",
            "This distinction prevents a common false conclusion: a “good signature” message does not mean an unknown key is the developer you intended to trust. Likewise, a matching hash copied from the same untrusted download page provides weak protection against that entire page being replaced. Verification is a chain of evidence, not a green icon."
          ],
          "bullets": []
        },
        {
          "heading": "Collect one coherent release",
          "paragraphs": [
            "Begin at the project’s official download page. Select the installer for your operating system and processor architecture, then obtain the checksum manifest and signature associated with that same release. Keep them together in a clearly named folder. Mixing a new installer with an old manifest will fail even if both files are legitimate.",
            "Use the project’s documented procedure and signing-key information. A release may have one maintainer signature or attestations from several builders. Preserve the full fingerprint you checked in a private installation record; a short name or email address displayed by a tool is not a substitute for the expected key identity."
          ],
          "bullets": []
        },
        {
          "heading": "Verify the signature and the file",
          "paragraphs": [
            "For a detached OpenPGP signature, GnuPG’s verify operation checks the signature against the corresponding data file. Follow the project’s exact command and file order. Read the result, including which key signed the data. If the signature is bad, the files do not match or the expected key cannot be established, stop before installation.",
            "Then calculate the installer’s hash and compare it with the authenticated manifest. Confirm that the output names the file you will actually run. “No files checked” is not success. A hash match for a different operating-system package does not verify your installer, and a successful signature check alone does not check a separately downloaded binary."
          ],
          "bullets": []
        },
        {
          "heading": "Use convenience tools with a clear starting point",
          "paragraphs": [
            "Sparrow offers a Verify Download interface in supported versions. Its download page explains using the installer, manifest and signature together. This is convenient when you already have a trusted installation, but you still need a sound starting point for the first installation. Do not install an unverified copy solely to have it declare itself trustworthy.",
            "Bitcoin Core’s download documentation publishes platform-specific checksum and signature procedures. Use the current page rather than copying a versioned command from an old screenshot. The example filename should be adapted to the actual release you downloaded, while the verification logic remains the same."
          ],
          "bullets": []
        },
        {
          "heading": "Know the limit and keep useful evidence",
          "paragraphs": [
            "Verification can detect a mismatch or an unexpected signer. It does not prove that software has no bugs, that a developer is infallible or that the operating system executing the verifier is clean. That is a reason to understand the result precisely, not a reason to skip the check.",
            "Keep a brief record of the official source, release, full signing-key fingerprint, installer hash and verification result. Recheck the process when signing keys or release methods change. If you are teaching someone, practice with a harmless downloaded file first and deliberately change it to see verification fail. Learning the failure state makes the success state much easier to interpret."
          ],
          "bullets": [
            "Match product, platform and release.",
            "Establish the expected signing key.",
            "Verify both the signed manifest and the installer hash.",
            "Install only the file you verified."
          ]
        }
      ],
      "sources": [
        {
          "title": "GnuPG verification commands",
          "url": "https://www.gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html"
        },
        {
          "title": "Sparrow download verification",
          "url": "https://sparrowwallet.com/download/"
        },
        {
          "title": "Bitcoin Core download and verification",
          "url": "https://bitcoincore.org/en/download/"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Three questions, three separate checks</h2>\n<p>Before installing Bitcoin software, ask whether you downloaded the intended product, whether the file matches the release record, and whether that record was signed by the expected developer. A checksum answers a file-integrity question. A signature connects data to a signing key. Establishing whose key it is remains a separate step.</p>\n<p>This distinction prevents a common false conclusion: a “good signature” message does not mean an unknown key is the developer you intended to trust. Likewise, a matching hash copied from the same untrusted download page provides weak protection against that entire page being replaced. Verification is a chain of evidence, not a green icon.</p>\n<h2 id=\"section-1\">Collect one coherent release</h2>\n<p>Begin at the project’s official download page. Select the installer for your operating system and processor architecture, then obtain the checksum manifest and signature associated with that same release. Keep them together in a clearly named folder. Mixing a new installer with an old manifest will fail even if both files are legitimate.</p>\n<p>Use the project’s documented procedure and signing-key information. A release may have one maintainer signature or attestations from several builders. Preserve the full fingerprint you checked in a private installation record; a short name or email address displayed by a tool is not a substitute for the expected key identity.</p>\n<h2 id=\"section-2\">Verify the signature and the file</h2>\n<p>For a detached OpenPGP signature, GnuPG’s verify operation checks the signature against the corresponding data file. Follow the project’s exact command and file order. Read the result, including which key signed the data. If the signature is bad, the files do not match or the expected key cannot be established, stop before installation.</p>\n<p>Then calculate the installer’s hash and compare it with the authenticated manifest. Confirm that the output names the file you will actually run. “No files checked” is not success. A hash match for a different operating-system package does not verify your installer, and a successful signature check alone does not check a separately downloaded binary.</p>\n<h2 id=\"section-3\">Use convenience tools with a clear starting point</h2>\n<p>Sparrow offers a Verify Download interface in supported versions. Its download page explains using the installer, manifest and signature together. This is convenient when you already have a trusted installation, but you still need a sound starting point for the first installation. Do not install an unverified copy solely to have it declare itself trustworthy.</p>\n<p>Bitcoin Core’s download documentation publishes platform-specific checksum and signature procedures. Use the current page rather than copying a versioned command from an old screenshot. The example filename should be adapted to the actual release you downloaded, while the verification logic remains the same.</p>\n<h2 id=\"section-4\">Know the limit and keep useful evidence</h2>\n<p>Verification can detect a mismatch or an unexpected signer. It does not prove that software has no bugs, that a developer is infallible or that the operating system executing the verifier is clean. That is a reason to understand the result precisely, not a reason to skip the check.</p>\n<p>Keep a brief record of the official source, release, full signing-key fingerprint, installer hash and verification result. Recheck the process when signing keys or release methods change. If you are teaching someone, practice with a harmless downloaded file first and deliberately change it to see verification fail. Learning the failure state makes the success state much easier to interpret.</p>\n<ul><li>Match product, platform and release.</li><li>Establish the expected signing key.</li><li>Verify both the signed manifest and the installer hash.</li><li>Install only the file you verified.</li></ul>",
      "words": 577
    },
    {
      "id": "bitcoin-core-2026",
      "title": "Run a node you actually use",
      "category": "Nodes",
      "description": "Plan storage, validate the chain and connect your wallet without exposing administration.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Give the node a purpose",
          "paragraphs": [
            "A Bitcoin full node checks blocks and transactions against the rules it enforces. Running one is different from mining, and it does not automatically make every wallet on your network use it. A useful first goal is simple: synchronize your own node and deliberately connect one compatible wallet to it.",
            "Choose whether you want Bitcoin Core directly or a maintained node distribution that bundles additional services. A distribution can simplify administration, but each extra service adds its own updates, configuration and recovery responsibilities. Begin with the smallest setup that accomplishes your goal rather than enabling an entire app catalogue at once."
          ],
          "bullets": []
        },
        {
          "heading": "Budget for the whole system",
          "paragraphs": [
            "Check current storage, bandwidth and operating-system requirements before installation. Historic tutorials often quote blockchain sizes or hardware recommendations that age quickly. Allow room for growth and remember that an Electrum indexer, explorer or other application can need substantial additional storage beyond Bitcoin Core itself.",
            "Pruning discards older block files after validation and can reduce ongoing disk use. It does not skip initial validation or eliminate the initial download. It also affects later rescans and applications that need historical blocks. Choose pruning with the needs of your wallet and companion services in mind, rather than treating it as a universal storage toggle."
          ],
          "bullets": []
        },
        {
          "heading": "Install, synchronize and observe",
          "paragraphs": [
            "Download Bitcoin Core from its official site and verify the release before installation. Choose a data directory on reliable storage, review available space, and let the initial synchronization complete. Laptop sleep, unstable power and a constrained connection can interrupt progress; understand those environmental conditions before diagnosing a software fault.",
            "Use the application’s synchronization status and peer information to observe what is happening. A progress estimate is not a guarantee of completion time. Once synchronized, check that the node remains near the network tip during normal operation. A node that is installed but routinely disconnected may not give your wallet the information you expect."
          ],
          "bullets": []
        },
        {
          "heading": "Keep administration private",
          "paragraphs": [
            "Bitcoin Core’s RPC interface gives applications powerful control over the node and, where applicable, its wallets. The project warns that it can expose private data and operations affecting funds. Do not forward RPC to the public internet. Local cookie authentication is a straightforward option when the wallet and node run on the same machine.",
            "If you need access across machines, design that access deliberately using the current documentation and a private authenticated connection. Peer-to-peer Bitcoin traffic and administrative RPC are different services. Opening a port to participate in the network is not permission to expose a wallet-control interface."
          ],
          "bullets": []
        },
        {
          "heading": "Connect a wallet and maintain the result",
          "paragraphs": [
            "Sparrow’s official Core connection guide explains local configuration, authentication and the limitations of pruned rescans. Confirm the wallet’s server settings rather than assuming it switched automatically. If a restored wallet needs transactions older than the blocks your node retains, plan the documented recovery or rescan path instead of interpreting an empty balance as lost funds.",
            "Keep a maintenance record covering software updates, available storage, connection settings and backups of anything that cannot be recreated. The blockchain can be downloaded again; private wallet material and personal metadata need their own backup plan. Finish by explaining where validation happens, how your wallet reaches it, and what you would restore after a disk failure."
          ],
          "bullets": [
            "Plan storage for Core and every additional service.",
            "Verify the installation and finish synchronization.",
            "Keep RPC private.",
            "Confirm the wallet is using the intended node."
          ]
        }
      ],
      "sources": [
        {
          "title": "Running a full node",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core download and verification",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Bitcoin Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        },
        {
          "title": "Connecting Sparrow to Bitcoin Core",
          "url": "https://sparrowwallet.com/docs/connect-node.html"
        },
        {
          "title": "MyNode introduction",
          "url": "https://docs.mynodebtc.com/intro/introduction.html"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Give the node a purpose</h2>\n<p>A Bitcoin full node checks blocks and transactions against the rules it enforces. Running one is different from mining, and it does not automatically make every wallet on your network use it. A useful first goal is simple: synchronize your own node and deliberately connect one compatible wallet to it.</p>\n<p>Choose whether you want Bitcoin Core directly or a maintained node distribution that bundles additional services. A distribution can simplify administration, but each extra service adds its own updates, configuration and recovery responsibilities. Begin with the smallest setup that accomplishes your goal rather than enabling an entire app catalogue at once.</p>\n<h2 id=\"section-1\">Budget for the whole system</h2>\n<p>Check current storage, bandwidth and operating-system requirements before installation. Historic tutorials often quote blockchain sizes or hardware recommendations that age quickly. Allow room for growth and remember that an Electrum indexer, explorer or other application can need substantial additional storage beyond Bitcoin Core itself.</p>\n<p>Pruning discards older block files after validation and can reduce ongoing disk use. It does not skip initial validation or eliminate the initial download. It also affects later rescans and applications that need historical blocks. Choose pruning with the needs of your wallet and companion services in mind, rather than treating it as a universal storage toggle.</p>\n<h2 id=\"section-2\">Install, synchronize and observe</h2>\n<p>Download Bitcoin Core from its official site and verify the release before installation. Choose a data directory on reliable storage, review available space, and let the initial synchronization complete. Laptop sleep, unstable power and a constrained connection can interrupt progress; understand those environmental conditions before diagnosing a software fault.</p>\n<p>Use the application’s synchronization status and peer information to observe what is happening. A progress estimate is not a guarantee of completion time. Once synchronized, check that the node remains near the network tip during normal operation. A node that is installed but routinely disconnected may not give your wallet the information you expect.</p>\n<h2 id=\"section-3\">Keep administration private</h2>\n<p>Bitcoin Core’s RPC interface gives applications powerful control over the node and, where applicable, its wallets. The project warns that it can expose private data and operations affecting funds. Do not forward RPC to the public internet. Local cookie authentication is a straightforward option when the wallet and node run on the same machine.</p>\n<p>If you need access across machines, design that access deliberately using the current documentation and a private authenticated connection. Peer-to-peer Bitcoin traffic and administrative RPC are different services. Opening a port to participate in the network is not permission to expose a wallet-control interface.</p>\n<h2 id=\"section-4\">Connect a wallet and maintain the result</h2>\n<p>Sparrow’s official Core connection guide explains local configuration, authentication and the limitations of pruned rescans. Confirm the wallet’s server settings rather than assuming it switched automatically. If a restored wallet needs transactions older than the blocks your node retains, plan the documented recovery or rescan path instead of interpreting an empty balance as lost funds.</p>\n<p>Keep a maintenance record covering software updates, available storage, connection settings and backups of anything that cannot be recreated. The blockchain can be downloaded again; private wallet material and personal metadata need their own backup plan. Finish by explaining where validation happens, how your wallet reaches it, and what you would restore after a disk failure.</p>\n<ul><li>Plan storage for Core and every additional service.</li><li>Verify the installation and finish synchronization.</li><li>Keep RPC private.</li><li>Confirm the wallet is using the intended node.</li></ul>",
      "words": 563
    },
    {
      "id": "multisig-backup-2026",
      "title": "The complete multisig recovery kit",
      "category": "Security",
      "description": "Back up the policy, the keys and the knowledge needed to bring them together.",
      "minutes": 5,
      "reviewed": "2026-11-12",
      "sections": [
        {
          "heading": "Two kinds of information must survive",
          "paragraphs": [
            "A multisig wallet combines signing keys with a spending policy. The keys provide authority; the policy describes which keys and how many signatures are required. A pile of seed backups without the complete wallet configuration can make recovery much harder. A configuration file without enough signing authority cannot normally spend the funds.",
            "Start your inventory with those two categories. Name the wallet, its threshold, the cosigners and the software used to coordinate it. Use neutral labels such as Signer A in any learning exercise. Keep real seeds, passphrases and exact storage locations out of this website and out of shared planning documents."
          ],
          "bullets": []
        },
        {
          "heading": "Preserve the configuration in a supported format",
          "paragraphs": [
            "Wallet configuration needs to capture the relevant public keys, key origins or derivation information, script type and threshold. Output descriptors provide a language for describing scripts and key derivation. BSMS defines a coordinated multisig setup format. The appropriate export depends on what your coordinator and signers support.",
            "Export the complete wallet configuration using the application’s documented function and record which format it is. Do not assume that a screenshot of the wallet name, a single cosigner’s extended public key or an unsigned transaction is an equivalent backup. Keep more than one readable copy and test that you can identify the correct file."
          ],
          "bullets": []
        },
        {
          "heading": "Keep independent keys independent",
          "paragraphs": [
            "If all signing keys and their backups live together, one location failure can defeat the purpose of the threshold. The same is true if apparently separate signers ultimately depend on one unprotected secret. Consider both theft and loss when deciding who holds material and which locations can become unavailable.",
            "BlueWallet’s multisig documentation explicitly notes that keeping all vault keys on one device has the security characteristics of an ordinary single-device wallet. Its coordination backup is a separate part of recovery. Other coordinators use different names, so translate the label into the underlying question: what does this file recover, and what does it leave out?"
          ],
          "bullets": []
        },
        {
          "heading": "Test identification before testing spending",
          "paragraphs": [
            "Begin with a safe configuration exercise. Import a copy into a compatible coordinator in a controlled environment, verify the intended threshold and cosigners, and compare known receiving addresses. Public-only reconstruction can test whether your wallet map is correct without bringing the signing secrets onto a general-purpose computer.",
            "A fuller rehearsal should be planned with the actual signer models and backup formats. Use the supported recovery procedures and preserve your working setup until the test is understood. Any restored spare signer becomes another place holding spending authority. Account for it explicitly after the exercise rather than leaving it forgotten in a drawer."
          ],
          "bullets": []
        },
        {
          "heading": "Document the handoff and the failure cases",
          "paragraphs": [
            "Write a short sequence that another authorized person could follow: identify the wallet, locate the configuration, obtain the required signers, verify the receiving or spending details, and seek help through known official channels if something does not match. Do not embed every secret in the instructions themselves.",
            "Practice a loss scenario with dummy material. Remove one signer from the diagram and ask whether the remaining threshold can still be met. Then remove the coordinator computer and test whether the exported configuration supplies the missing map. These are different failures and deserve separate answers.",
            "Review the kit when the threshold, signer, passphrase, account or storage arrangement changes. The objective is not a larger folder of files. It is a recovery package whose components are identifiable, whose assumptions are documented, and whose operation has been demonstrated without undermining the separation that multisig was meant to create."
          ],
          "bullets": [
            "Back up complete policy and cosigner information.",
            "Maintain enough independent signing backups.",
            "Verify a reconstructed public wallet before signing.",
            "Record and rehearse realistic loss scenarios."
          ]
        }
      ],
      "sources": [
        {
          "title": "BIP129: secure multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380: output descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        },
        {
          "title": "BlueWallet multisig vaults",
          "url": "https://bluewallet.io/docs/multisig-wallet/"
        },
        {
          "title": "BIP174: partially signed transactions",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki"
        }
      ],
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Two kinds of information must survive</h2>\n<p>A multisig wallet combines signing keys with a spending policy. The keys provide authority; the policy describes which keys and how many signatures are required. A pile of seed backups without the complete wallet configuration can make recovery much harder. A configuration file without enough signing authority cannot normally spend the funds.</p>\n<p>Start your inventory with those two categories. Name the wallet, its threshold, the cosigners and the software used to coordinate it. Use neutral labels such as Signer A in any learning exercise. Keep real seeds, passphrases and exact storage locations out of this website and out of shared planning documents.</p>\n<h2 id=\"section-1\">Preserve the configuration in a supported format</h2>\n<p>Wallet configuration needs to capture the relevant public keys, key origins or derivation information, script type and threshold. Output descriptors provide a language for describing scripts and key derivation. BSMS defines a coordinated multisig setup format. The appropriate export depends on what your coordinator and signers support.</p>\n<p>Export the complete wallet configuration using the application’s documented function and record which format it is. Do not assume that a screenshot of the wallet name, a single cosigner’s extended public key or an unsigned transaction is an equivalent backup. Keep more than one readable copy and test that you can identify the correct file.</p>\n<h2 id=\"section-2\">Keep independent keys independent</h2>\n<p>If all signing keys and their backups live together, one location failure can defeat the purpose of the threshold. The same is true if apparently separate signers ultimately depend on one unprotected secret. Consider both theft and loss when deciding who holds material and which locations can become unavailable.</p>\n<p>BlueWallet’s multisig documentation explicitly notes that keeping all vault keys on one device has the security characteristics of an ordinary single-device wallet. Its coordination backup is a separate part of recovery. Other coordinators use different names, so translate the label into the underlying question: what does this file recover, and what does it leave out?</p>\n<h2 id=\"section-3\">Test identification before testing spending</h2>\n<p>Begin with a safe configuration exercise. Import a copy into a compatible coordinator in a controlled environment, verify the intended threshold and cosigners, and compare known receiving addresses. Public-only reconstruction can test whether your wallet map is correct without bringing the signing secrets onto a general-purpose computer.</p>\n<p>A fuller rehearsal should be planned with the actual signer models and backup formats. Use the supported recovery procedures and preserve your working setup until the test is understood. Any restored spare signer becomes another place holding spending authority. Account for it explicitly after the exercise rather than leaving it forgotten in a drawer.</p>\n<h2 id=\"section-4\">Document the handoff and the failure cases</h2>\n<p>Write a short sequence that another authorized person could follow: identify the wallet, locate the configuration, obtain the required signers, verify the receiving or spending details, and seek help through known official channels if something does not match. Do not embed every secret in the instructions themselves.</p>\n<p>Practice a loss scenario with dummy material. Remove one signer from the diagram and ask whether the remaining threshold can still be met. Then remove the coordinator computer and test whether the exported configuration supplies the missing map. These are different failures and deserve separate answers.</p>\n<p>Review the kit when the threshold, signer, passphrase, account or storage arrangement changes. The objective is not a larger folder of files. It is a recovery package whose components are identifiable, whose assumptions are documented, and whose operation has been demonstrated without undermining the separation that multisig was meant to create.</p>\n<ul><li>Back up complete policy and cosigner information.</li><li>Maintain enough independent signing backups.</li><li>Verify a reconstructed public wallet before signing.</li><li>Record and rehearse realistic loss scenarios.</li></ul>",
      "words": 607
    },
    {
      "id": "bitcoin-in-plain-english",
      "title": "Bitcoin, without the vocabulary test",
      "category": "Foundations",
      "description": "Understand keys, wallets, nodes and transactions before choosing your next tool.",
      "minutes": 5,
      "sections": [
        {
          "heading": "Start with one useful question",
          "paragraphs": [
            "When you look at a bitcoin balance, ask: who can authorise a payment? A self-custody wallet gives you that ability through private keys. A service account usually gives you a claim against an operator who controls the spending. Both can show the same number on a screen; they involve very different responsibilities.",
            "Your first learning goal is to recognise that difference. You do not need a new device, a complicated security arrangement or an opinion about the price to understand the system. Take an ordinary payment and follow what changes at each stage."
          ],
          "bullets": []
        },
        {
          "heading": "A wallet is a tool for using keys",
          "paragraphs": [
            "The bitcoin does not sit inside an app or a USB device. The blockchain records outputs that can be spent when their conditions are satisfied. Your wallet finds relevant outputs, helps construct a payment and, if it holds the required private keys, signs it. A hardware signer can keep those keys separate from the computer displaying the wallet.",
            "A watch-only wallet demonstrates the distinction: it can show transactions without having the ability to spend. Treat that visibility as sensitive, even though it does not grant signing authority. Recovery information needs a different level of protection because it can recreate that authority."
          ],
          "bullets": []
        },
        {
          "heading": "The balance is made from pieces",
          "paragraphs": [
            "A UTXO is an unspent transaction output: an amount available to be spent under particular conditions. Imagine receiving three separate payments. Your wallet may show one total while managing three outputs underneath. A later payment can consume one or several of them and create a recipient output plus change.",
            "This explains two otherwise surprising details. Sending a small payment can involve a larger input, and the change belongs back in your wallet. Combining inputs also publishes a relationship between them. A transaction preview is therefore useful for understanding both the payment and its privacy consequences."
          ],
          "bullets": []
        },
        {
          "heading": "Nodes and miners have different jobs",
          "paragraphs": [
            "A full node checks blocks and transactions against its rules. Miners assemble candidate blocks and perform proof of work. A miner cannot make an invalid payment acceptable to a node that rejects it. Running a node is about doing your own verification; it does not automatically mean mining or earning bitcoin.",
            "A broadcast transaction is a proposal being shared across the network. Inclusion in a block gives it a confirmation; subsequent blocks add further confirmations. Block production is variable. A fee estimate is not an appointment, and an app displaying a payment does not necessarily mean it has confirmed."
          ],
          "bullets": []
        },
        {
          "heading": "Turn understanding into a small practice",
          "paragraphs": [
            "Write down what you expect before using a wallet: which network you are using, who holds the keys, how you would recover, and how you will verify the destination. Then practise with an amount you can comfortably afford to lose. A successful tiny exercise is more useful than memorising ten product names.",
            "Afterwards, explain the result in your own words. Where was the change? Which fee did you pay? What would still work if the phone disappeared? These questions become a checklist you can reuse whenever the interface changes."
          ],
          "bullets": [
            "Wallet: the interface and software that help manage payments.",
            "Private key: authority to satisfy a spending condition.",
            "Node: independent verification of the rules.",
            "Confirmation: inclusion in the chain, followed by more blocks."
          ]
        }
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Sparrow: Features and transaction inspection",
          "url": "https://sparrowwallet.com/features/"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Start with one useful question</h2>\n<p>When you look at a bitcoin balance, ask: who can authorise a payment? A self-custody wallet gives you that ability through private keys. A service account usually gives you a claim against an operator who controls the spending. Both can show the same number on a screen; they involve very different responsibilities.</p>\n<p>Your first learning goal is to recognise that difference. You do not need a new device, a complicated security arrangement or an opinion about the price to understand the system. Take an ordinary payment and follow what changes at each stage.</p>\n<h2 id=\"section-1\">A wallet is a tool for using keys</h2>\n<p>The bitcoin does not sit inside an app or a USB device. The blockchain records outputs that can be spent when their conditions are satisfied. Your wallet finds relevant outputs, helps construct a payment and, if it holds the required private keys, signs it. A hardware signer can keep those keys separate from the computer displaying the wallet.</p>\n<p>A watch-only wallet demonstrates the distinction: it can show transactions without having the ability to spend. Treat that visibility as sensitive, even though it does not grant signing authority. Recovery information needs a different level of protection because it can recreate that authority.</p>\n<h2 id=\"section-2\">The balance is made from pieces</h2>\n<p>A UTXO is an unspent transaction output: an amount available to be spent under particular conditions. Imagine receiving three separate payments. Your wallet may show one total while managing three outputs underneath. A later payment can consume one or several of them and create a recipient output plus change.</p>\n<p>This explains two otherwise surprising details. Sending a small payment can involve a larger input, and the change belongs back in your wallet. Combining inputs also publishes a relationship between them. A transaction preview is therefore useful for understanding both the payment and its privacy consequences.</p>\n<h2 id=\"section-3\">Nodes and miners have different jobs</h2>\n<p>A full node checks blocks and transactions against its rules. Miners assemble candidate blocks and perform proof of work. A miner cannot make an invalid payment acceptable to a node that rejects it. Running a node is about doing your own verification; it does not automatically mean mining or earning bitcoin.</p>\n<p>A broadcast transaction is a proposal being shared across the network. Inclusion in a block gives it a confirmation; subsequent blocks add further confirmations. Block production is variable. A fee estimate is not an appointment, and an app displaying a payment does not necessarily mean it has confirmed.</p>\n<h2 id=\"section-4\">Turn understanding into a small practice</h2>\n<p>Write down what you expect before using a wallet: which network you are using, who holds the keys, how you would recover, and how you will verify the destination. Then practise with an amount you can comfortably afford to lose. A successful tiny exercise is more useful than memorising ten product names.</p>\n<p>Afterwards, explain the result in your own words. Where was the change? Which fee did you pay? What would still work if the phone disappeared? These questions become a checklist you can reuse whenever the interface changes.</p>\n<ul><li>Wallet: the interface and software that help manage payments.</li><li>Private key: authority to satisfy a spending condition.</li><li>Node: independent verification of the rules.</li><li>Confirmation: inclusion in the chain, followed by more blocks.</li></ul>",
      "words": 540
    },
    {
      "id": "privacy-as-a-routine",
      "title": "Make privacy a routine",
      "category": "Privacy",
      "description": "A practical review of what your wallet, payment partners and network connections reveal.",
      "minutes": 5,
      "sections": [
        {
          "heading": "Choose the information you want to protect",
          "paragraphs": [
            "Privacy becomes easier to reason about when you name the audience. A merchant, the operator of a wallet server, a payment provider and someone inspecting the blockchain see different information. There is no single switch that hides everything from everyone.",
            "Make a simple map of one ordinary payment. Note who knows your name, who knows an address, who sees the network connection and who receives the goods or message. This exercise is useful before choosing a product because it exposes the places where a privacy feature cannot help."
          ],
          "bullets": []
        },
        {
          "heading": "Separate receiving from publishing",
          "paragraphs": [
            "Bitcoin transactions are public. A fresh receiving address reduces direct address reuse, but it does not promise that later activity cannot be linked. Publishing a donation address alongside your identity deliberately makes that relationship visible. Decide whether that is appropriate for the purpose.",
            "Use wallet labels to remember where payments came from and what they were for. Choose descriptions that help you make spending decisions without becoming an unnecessary dossier. Treat exported labels, wallet screenshots and extended public keys as private records. Keep them out of public support conversations."
          ],
          "bullets": []
        },
        {
          "heading": "Read the transaction before signing",
          "paragraphs": [
            "Coin control means choosing which outputs to spend. It can help keep payments from different contexts apart. Combining a work payment and a personal payment in one transaction can expose a relationship you did not intend to publish. Change needs attention too, because it continues the transaction history.",
            "Before sending, inspect the inputs, recipient, change and fee in the wallet preview. Ask whether the payment merges contexts unnecessarily. Do not contort every payment into an elaborate construction: complexity that you cannot explain is hard to maintain and easy to undo later."
          ],
          "bullets": []
        },
        {
          "heading": "Distinguish the node from the network path",
          "paragraphs": [
            "Connecting to a public wallet server may reveal information about the addresses your wallet is interested in. Sparrow documents this trade-off during setup. Using your own node or a server you control can reduce that particular disclosure, provided the wallet actually uses it.",
            "That does not erase the transaction graph or information you already gave a counterparty. Likewise, protecting a network connection does not anonymise a bank transfer or a delivery address. Review the whole payment rather than judging privacy by one badge in the interface."
          ],
          "bullets": []
        },
        {
          "heading": "Treat collaborative spending as a technique",
          "paragraphs": [
            "Coinjoin and related techniques try to make transaction interpretation less certain. Their properties depend on the implementation and subsequent spending. They do not make identity information disappear from merchants, exchanges or your own records. Sparrow describes transaction constructions that introduce ambiguity; the benefit is not a universal anonymity guarantee.",
            "The original Whirlpool tutorials in this archive are historical: Sparrow removed its Whirlpool client in version 1.9.0. Read them for context, not as current installation instructions. Re-check project documentation before adopting any replacement and do not assume a familiar product name means the same operator or software."
          ],
          "bullets": []
        },
        {
          "heading": "A five-minute maintenance habit",
          "paragraphs": [
            "Once a month, review one recent payment and one receiving workflow. Look for an address you reused, a label you forgot, an unnecessary public screenshot or a server setting you did not intend. Fix the next occurrence rather than assuming an old disclosure can be reversed.",
            "The goal is a routine you can sustain. Better defaults, clear labels and deliberate spending choices will usually serve you longer than a one-off privacy ritual you do not understand."
          ],
          "bullets": [
            "Use a fresh address when appropriate.",
            "Keep different payment contexts legible to yourself.",
            "Check which server the wallet uses.",
            "Revisit assumptions whenever a service or wallet changes."
          ]
        }
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Choose the information you want to protect</h2>\n<p>Privacy becomes easier to reason about when you name the audience. A merchant, the operator of a wallet server, a payment provider and someone inspecting the blockchain see different information. There is no single switch that hides everything from everyone.</p>\n<p>Make a simple map of one ordinary payment. Note who knows your name, who knows an address, who sees the network connection and who receives the goods or message. This exercise is useful before choosing a product because it exposes the places where a privacy feature cannot help.</p>\n<h2 id=\"section-1\">Separate receiving from publishing</h2>\n<p>Bitcoin transactions are public. A fresh receiving address reduces direct address reuse, but it does not promise that later activity cannot be linked. Publishing a donation address alongside your identity deliberately makes that relationship visible. Decide whether that is appropriate for the purpose.</p>\n<p>Use wallet labels to remember where payments came from and what they were for. Choose descriptions that help you make spending decisions without becoming an unnecessary dossier. Treat exported labels, wallet screenshots and extended public keys as private records. Keep them out of public support conversations.</p>\n<h2 id=\"section-2\">Read the transaction before signing</h2>\n<p>Coin control means choosing which outputs to spend. It can help keep payments from different contexts apart. Combining a work payment and a personal payment in one transaction can expose a relationship you did not intend to publish. Change needs attention too, because it continues the transaction history.</p>\n<p>Before sending, inspect the inputs, recipient, change and fee in the wallet preview. Ask whether the payment merges contexts unnecessarily. Do not contort every payment into an elaborate construction: complexity that you cannot explain is hard to maintain and easy to undo later.</p>\n<h2 id=\"section-3\">Distinguish the node from the network path</h2>\n<p>Connecting to a public wallet server may reveal information about the addresses your wallet is interested in. Sparrow documents this trade-off during setup. Using your own node or a server you control can reduce that particular disclosure, provided the wallet actually uses it.</p>\n<p>That does not erase the transaction graph or information you already gave a counterparty. Likewise, protecting a network connection does not anonymise a bank transfer or a delivery address. Review the whole payment rather than judging privacy by one badge in the interface.</p>\n<h2 id=\"section-4\">Treat collaborative spending as a technique</h2>\n<p>Coinjoin and related techniques try to make transaction interpretation less certain. Their properties depend on the implementation and subsequent spending. They do not make identity information disappear from merchants, exchanges or your own records. Sparrow describes transaction constructions that introduce ambiguity; the benefit is not a universal anonymity guarantee.</p>\n<p>The original Whirlpool tutorials in this archive are historical: Sparrow removed its Whirlpool client in version 1.9.0. Read them for context, not as current installation instructions. Re-check project documentation before adopting any replacement and do not assume a familiar product name means the same operator or software.</p>\n<h2 id=\"section-5\">A five-minute maintenance habit</h2>\n<p>Once a month, review one recent payment and one receiving workflow. Look for an address you reused, a label you forgot, an unnecessary public screenshot or a server setting you did not intend. Fix the next occurrence rather than assuming an old disclosure can be reversed.</p>\n<p>The goal is a routine you can sustain. Better defaults, clear labels and deliberate spending choices will usually serve you longer than a one-off privacy ritual you do not understand.</p>\n<ul><li>Use a fresh address when appropriate.</li><li>Keep different payment contexts legible to yourself.</li><li>Check which server the wallet uses.</li><li>Revisit assumptions whenever a service or wallet changes.</li></ul>",
      "words": 586
    },
    {
      "id": "peer-to-peer-first-trade",
      "title": "Before your first peer-to-peer trade",
      "category": "Buying bitcoin",
      "description": "Compare the trade protocol, payment privacy, total cost and recovery path before committing.",
      "minutes": 5,
      "sections": [
        {
          "heading": "Start with the trade, not the slogan",
          "paragraphs": [
            "Peer-to-peer buying describes an interaction between people. It does not tell you who operates the interface, how disputes work, what information the payment method reveals or whether a trade has escrow. Treat each of these as a separate question.",
            "Before choosing an offer, write down the actual outcome you want: the amount of bitcoin received, the payment method available to you and a deadline you can meet. You are comparing complete workflows, not simply the percentage displayed next to a price."
          ],
          "bullets": []
        },
        {
          "heading": "Identify the exact product and protocol",
          "paragraphs": [
            "Bisq v1 and Bisq Easy are not interchangeable instructions. Bisq published a postmortem for a May 2026 incident affecting v1 altcoin trades and explicitly distinguished Bisq 2 and Bisq Easy as unaffected. That is a reason to check the precise product, release and current notices before following an archived walkthrough.",
            "RoboSats uses a trade workflow built around Lightning hold invoices. Hodl Hodl describes a multisignature escrow process. These mechanisms have different funding, timing and recovery requirements. Understand what must be locked, who can release it and what happens if the other person stops responding."
          ],
          "bullets": []
        },
        {
          "heading": "Read the payment method as a privacy policy",
          "paragraphs": [
            "A platform that does not request an identity document cannot stop a bank or payment provider keeping records. Your counterparty may receive your legal name or account information through the payment rail. Decide whether you are comfortable with that before opening a contract.",
            "Availability, limits and permitted use can change. Peach publishes jurisdiction and compliance conditions in its current terms; do not turn an old no-KYC headline into a universal promise. Use the current service terms and local requirements for your own situation rather than assuming every offer is available everywhere."
          ],
          "bullets": []
        },
        {
          "heading": "Compare the amount that actually arrives",
          "paragraphs": [
            "Add up the price premium, platform charges, payment-provider charges and any on-chain or Lightning costs. Distinguish a refundable deposit from a fee, while remembering that both can require funds upfront. Avoid hard-coded fee examples from an old article: inspect the live quote before accepting.",
            "For vouchers, check the retailer, the type of voucher, the redemption deadline and the destination requirements. Azteco documents retailer-set commissions and different redemption paths for on-chain and Lightning vouchers. Keep a voucher code private; it is not a receipt to post in a public support chat."
          ],
          "bullets": []
        },
        {
          "heading": "Keep the agreement and the evidence together",
          "paragraphs": [
            "Use the platform’s documented conversation and dispute process. Read the offer conditions before accepting and preserve the minimum records needed to establish what happened. Do not mark a payment received because someone sends a screenshot, and do not move outside the agreed flow because a stranger promises a discount.",
            "For a first attempt, favour an amount and timetable that leave room to learn. Know how you will ask for help without disclosing recovery words, wallet secrets or unnecessary account details. A rushed trade is a poor place to discover how escrow works."
          ],
          "bullets": []
        },
        {
          "heading": "Retire old instructions deliberately",
          "paragraphs": [
            "The original AgoraDesk announced its wind-down in 2024. Its article remains in this library as historical material, not as a functioning buying route. A similarly named site is not evidence of continuity with the original operator.",
            "Keep a short record of the service and protocol you used, the date, the total cost and what you would change next time. That record turns the first trade into a learning exercise instead of a product endorsement."
          ],
          "bullets": []
        }
      ],
      "sources": [
        {
          "title": "Bisq: Getting started",
          "url": "https://bisq.network/getting-started/"
        },
        {
          "title": "Bisq: May 2026 security incident postmortem",
          "url": "https://bisq.network/blog/security-incident-post-mortem/"
        },
        {
          "title": "RoboSats: Quick start",
          "url": "https://docs.robosats.org/docs/quick-start/"
        },
        {
          "title": "Hodl Hodl: Exchange FAQ",
          "url": "https://hodlhodl.com/pages/faq"
        },
        {
          "title": "Peach: Terms and conditions",
          "url": "https://peachbitcoin.com/terms-and-conditions/"
        },
        {
          "title": "AgoraDesk: Original service winding-down announcement",
          "url": "https://web.archive.org/web/20260620191832/https://agoradesk.com/blog/announcements/winding-down?language=en"
        },
        {
          "title": "Azteco: Commission fees",
          "url": "https://help.azte.co/article/27-what-are-the-commission-fees"
        },
        {
          "title": "Azteco: Voucher redemption",
          "url": "https://azte.co/redeem"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Start with the trade, not the slogan</h2>\n<p>Peer-to-peer buying describes an interaction between people. It does not tell you who operates the interface, how disputes work, what information the payment method reveals or whether a trade has escrow. Treat each of these as a separate question.</p>\n<p>Before choosing an offer, write down the actual outcome you want: the amount of bitcoin received, the payment method available to you and a deadline you can meet. You are comparing complete workflows, not simply the percentage displayed next to a price.</p>\n<h2 id=\"section-1\">Identify the exact product and protocol</h2>\n<p>Bisq v1 and Bisq Easy are not interchangeable instructions. Bisq published a postmortem for a May 2026 incident affecting v1 altcoin trades and explicitly distinguished Bisq 2 and Bisq Easy as unaffected. That is a reason to check the precise product, release and current notices before following an archived walkthrough.</p>\n<p>RoboSats uses a trade workflow built around Lightning hold invoices. Hodl Hodl describes a multisignature escrow process. These mechanisms have different funding, timing and recovery requirements. Understand what must be locked, who can release it and what happens if the other person stops responding.</p>\n<h2 id=\"section-2\">Read the payment method as a privacy policy</h2>\n<p>A platform that does not request an identity document cannot stop a bank or payment provider keeping records. Your counterparty may receive your legal name or account information through the payment rail. Decide whether you are comfortable with that before opening a contract.</p>\n<p>Availability, limits and permitted use can change. Peach publishes jurisdiction and compliance conditions in its current terms; do not turn an old no-KYC headline into a universal promise. Use the current service terms and local requirements for your own situation rather than assuming every offer is available everywhere.</p>\n<h2 id=\"section-3\">Compare the amount that actually arrives</h2>\n<p>Add up the price premium, platform charges, payment-provider charges and any on-chain or Lightning costs. Distinguish a refundable deposit from a fee, while remembering that both can require funds upfront. Avoid hard-coded fee examples from an old article: inspect the live quote before accepting.</p>\n<p>For vouchers, check the retailer, the type of voucher, the redemption deadline and the destination requirements. Azteco documents retailer-set commissions and different redemption paths for on-chain and Lightning vouchers. Keep a voucher code private; it is not a receipt to post in a public support chat.</p>\n<h2 id=\"section-4\">Keep the agreement and the evidence together</h2>\n<p>Use the platform’s documented conversation and dispute process. Read the offer conditions before accepting and preserve the minimum records needed to establish what happened. Do not mark a payment received because someone sends a screenshot, and do not move outside the agreed flow because a stranger promises a discount.</p>\n<p>For a first attempt, favour an amount and timetable that leave room to learn. Know how you will ask for help without disclosing recovery words, wallet secrets or unnecessary account details. A rushed trade is a poor place to discover how escrow works.</p>\n<h2 id=\"section-5\">Retire old instructions deliberately</h2>\n<p>The original AgoraDesk announced its wind-down in 2024. Its article remains in this library as historical material, not as a functioning buying route. A similarly named site is not evidence of continuity with the original operator.</p>\n<p>Keep a short record of the service and protocol you used, the date, the total cost and what you would change next time. That record turns the first trade into a learning exercise instead of a product endorsement.</p>",
      "words": 560
    },
    {
      "id": "lightning-wallet-map",
      "title": "Choose the Lightning setup you can maintain",
      "category": "Lightning",
      "description": "Separate custody, embedded nodes and remote controls before comparing wallet interfaces.",
      "minutes": 5,
      "sections": [
        {
          "heading": "The same screen can hide different responsibilities",
          "paragraphs": [
            "Two apps can both show a Lightning balance and a pay button while working very differently. One may represent money held by a service. Another may run a node on your phone. A third may control a node somewhere else. Start with where the spending authority lives, then consider convenience.",
            "Write a one-sentence description of your setup before funding it. Include who holds the keys, which device needs to be available and what you would need after losing that device. If that sentence is difficult to write, spend more time with the project documentation."
          ],
          "bullets": []
        },
        {
          "heading": "A remote control is not the node",
          "paragraphs": [
            "ZEUS supports several connection types, including remote LND and Core Lightning connections as well as local wallet options. When it controls a separate node, losing the phone does not mean the node itself has vanished. Conversely, saving the phone configuration is not a replacement for maintaining the node and its recovery material.",
            "Treat connection credentials as sensitive. A QR code used to connect a wallet may grant capabilities, not merely identify a server. Before sending a screenshot for help, establish what it contains and redact anything that could authorise access."
          ],
          "bullets": []
        },
        {
          "heading": "An embedded wallet brings the node with you",
          "paragraphs": [
            "Blixt describes itself as a Lightning node on the device, rather than a remote control for a home node. Its documentation distinguishes on-chain funds from channel funds and sets out specific backup and migration procedures. Read those procedures before treating a phone replacement like an ordinary app reinstall.",
            "Do not run a casual recovery rehearsal by cloning an active Lightning wallet onto another device. Follow the implementation’s documented migration or disaster-recovery path. A generic phone backup is not evidence that channel state can safely be restored."
          ],
          "bullets": []
        },
        {
          "heading": "Backup instructions belong to the implementation",
          "paragraphs": [
            "Even within ZEUS, the embedded LND and LDK documentation describe different recovery arrangements. The LND documentation discusses encrypted backup and channel recovery; the LDK documentation describes Versioned Storage Service for channel state. A familiar app logo is therefore not enough to choose the correct guide.",
            "Record the wallet mode, backup method and any server configuration required for recovery. Keep those notes separate from public troubleshooting messages. Review them after a major change or migration, rather than assuming a seed phrase makes every Lightning implementation interchangeable."
          ],
          "bullets": []
        },
        {
          "heading": "Usable balance is a practical question",
          "paragraphs": [
            "ZEUS explains that its displayed Lightning balance can differ from sending capacity because channel reserves and channel status matter. A failed payment is not automatically a loss of funds. It can indicate routing, capacity, connectivity or fee-budget constraints.",
            "Before paying, read the invoice amount, recipient information available in the wallet and the maximum fee. If a payment fails, inspect its status before trying again. Do not create a second payment while the first remains unresolved merely because the interface feels slow."
          ],
          "bullets": []
        },
        {
          "heading": "Choose for the next six months",
          "paragraphs": [
            "Use a small working balance while learning. Test receiving as well as sending, because an app that pays successfully may still need a different arrangement to receive the amounts you expect. Observe what happens when the phone has been offline and when a payment cannot find a route.",
            "Choose the setup whose maintenance you can explain and perform. Someone who enjoys running a node may value control over liquidity and connectivity. Someone else may prefer a managed experience and its stated dependencies. There is no benefit in adopting a more demanding configuration and then neglecting its backups."
          ],
          "bullets": [
            "Name the custody model.",
            "Identify the exact wallet mode.",
            "Read the matching recovery procedure.",
            "Understand receiving and sending constraints.",
            "Recheck fees and service conditions at the point of use."
          ]
        }
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">The same screen can hide different responsibilities</h2>\n<p>Two apps can both show a Lightning balance and a pay button while working very differently. One may represent money held by a service. Another may run a node on your phone. A third may control a node somewhere else. Start with where the spending authority lives, then consider convenience.</p>\n<p>Write a one-sentence description of your setup before funding it. Include who holds the keys, which device needs to be available and what you would need after losing that device. If that sentence is difficult to write, spend more time with the project documentation.</p>\n<h2 id=\"section-1\">A remote control is not the node</h2>\n<p>ZEUS supports several connection types, including remote LND and Core Lightning connections as well as local wallet options. When it controls a separate node, losing the phone does not mean the node itself has vanished. Conversely, saving the phone configuration is not a replacement for maintaining the node and its recovery material.</p>\n<p>Treat connection credentials as sensitive. A QR code used to connect a wallet may grant capabilities, not merely identify a server. Before sending a screenshot for help, establish what it contains and redact anything that could authorise access.</p>\n<h2 id=\"section-2\">An embedded wallet brings the node with you</h2>\n<p>Blixt describes itself as a Lightning node on the device, rather than a remote control for a home node. Its documentation distinguishes on-chain funds from channel funds and sets out specific backup and migration procedures. Read those procedures before treating a phone replacement like an ordinary app reinstall.</p>\n<p>Do not run a casual recovery rehearsal by cloning an active Lightning wallet onto another device. Follow the implementation’s documented migration or disaster-recovery path. A generic phone backup is not evidence that channel state can safely be restored.</p>\n<h2 id=\"section-3\">Backup instructions belong to the implementation</h2>\n<p>Even within ZEUS, the embedded LND and LDK documentation describe different recovery arrangements. The LND documentation discusses encrypted backup and channel recovery; the LDK documentation describes Versioned Storage Service for channel state. A familiar app logo is therefore not enough to choose the correct guide.</p>\n<p>Record the wallet mode, backup method and any server configuration required for recovery. Keep those notes separate from public troubleshooting messages. Review them after a major change or migration, rather than assuming a seed phrase makes every Lightning implementation interchangeable.</p>\n<h2 id=\"section-4\">Usable balance is a practical question</h2>\n<p>ZEUS explains that its displayed Lightning balance can differ from sending capacity because channel reserves and channel status matter. A failed payment is not automatically a loss of funds. It can indicate routing, capacity, connectivity or fee-budget constraints.</p>\n<p>Before paying, read the invoice amount, recipient information available in the wallet and the maximum fee. If a payment fails, inspect its status before trying again. Do not create a second payment while the first remains unresolved merely because the interface feels slow.</p>\n<h2 id=\"section-5\">Choose for the next six months</h2>\n<p>Use a small working balance while learning. Test receiving as well as sending, because an app that pays successfully may still need a different arrangement to receive the amounts you expect. Observe what happens when the phone has been offline and when a payment cannot find a route.</p>\n<p>Choose the setup whose maintenance you can explain and perform. Someone who enjoys running a node may value control over liquidity and connectivity. Someone else may prefer a managed experience and its stated dependencies. There is no benefit in adopting a more demanding configuration and then neglecting its backups.</p>\n<ul><li>Name the custody model.</li><li>Identify the exact wallet mode.</li><li>Read the matching recovery procedure.</li><li>Understand receiving and sending constraints.</li><li>Recheck fees and service conditions at the point of use.</li></ul>",
      "words": 602
    },
    {
      "id": "transaction-troubleshooting",
      "title": "A calm guide to a stuck transaction",
      "category": "Foundations",
      "description": "Work out whether a payment is unsent, pending or confirmed before changing anything.",
      "minutes": 5,
      "sections": [
        {
          "heading": "First, name the state",
          "paragraphs": [
            "A transaction can be created without being signed, signed without being broadcast, seen by one node without being widely relayed, or included in a block. Those are different situations. Start with what your wallet actually reports, rather than treating every missing payment as the same problem.",
            "Write down the transaction identifier, the time you attempted the payment and whether the wallet reports confirmations. Keep private keys and recovery words out of your notes. If the payment came from a service account, also distinguish its withdrawal request from an actual Bitcoin transaction."
          ],
          "bullets": []
        },
        {
          "heading": "Check the wallet before checking the internet",
          "paragraphs": [
            "Confirm that the wallet is connected to the intended network and has finished synchronising. Compare the destination and amount with your own payment record. A watch-only wallet, an offline signer and an exchange account each expose different information; use the view that corresponds to the payment.",
            "A public explorer can help inspect a transaction, but querying it discloses an interest in that transaction to its operator. Prefer your own node or wallet’s transaction view when available. Do not paste an extended public key or seed phrase into a website to investigate a missing balance."
          ],
          "bullets": []
        },
        {
          "heading": "Understand what waiting means",
          "paragraphs": [
            "Confirmation depends on inclusion in a block. Blocks arrive irregularly and fee estimates change as demand changes. A displayed target is not a guarantee that your transaction will confirm after a particular number of minutes.",
            "If the payment is unconfirmed, inspect its fee rate and whether its inputs depend on another unconfirmed transaction. Compare against current conditions instead of a screenshot from an old tutorial. If there is no deadline, waiting may be a reasonable choice; establish the recipient’s expectations before paying extra."
          ],
          "bullets": []
        },
        {
          "heading": "Use the wallet’s supported fee tools",
          "paragraphs": [
            "Replace-by-fee creates a replacement transaction paying a higher fee. Bitcoin Core’s bumpfee documentation requires the transaction to be in the wallet and describes conditions that can prevent replacement. The additional fee may reduce change or require another input, so re-read the resulting transaction rather than approving it blindly.",
            "Child-pays-for-parent spends an output of the pending transaction with enough fee to make the combined package attractive. It requires control of a suitable output and software that supports the operation. Sparrow documents both approaches. Neither is a universal button that works for any transaction you can see."
          ],
          "bullets": []
        },
        {
          "heading": "Keep the original payment in view",
          "paragraphs": [
            "A fee replacement can produce a different transaction identifier. Save the new identifier with the original payment record so that you and the recipient are discussing the same event. Check the amount, destination and fee again on the signing device where applicable.",
            "Do not send a separate payment to the merchant as a substitute for understanding the first one. Both may eventually confirm. Equally, a transaction disappearing from one explorer does not prove it is cancelled everywhere. Ask the wallet or service for its documented resolution path before creating a conflicting payment."
          ],
          "bullets": []
        },
        {
          "heading": "Ask for help with useful, limited information",
          "paragraphs": [
            "A good support request says which wallet and network you use, whether it is synchronised, whether the transaction is confirmed, and what action you already tried. Share the transaction identifier only if you accept the associated privacy disclosure. Redact balances and unrelated addresses from screenshots.",
            "Anyone requesting a recovery phrase to accelerate a transaction is asking for spending authority, not diagnostic information. Pause when a proposed fix requires access you cannot explain. The objective is to resolve one payment while preserving control of the rest of the wallet."
          ],
          "bullets": []
        }
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        },
        {
          "title": "Bitcoin Core: bumpfee RPC reference",
          "url": "https://bitcoincore.org/en/doc/30.0.0/rpc/wallet/bumpfee/"
        },
        {
          "title": "Sparrow: Frequently asked questions",
          "url": "https://sparrowwallet.com/docs/faq.html"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">First, name the state</h2>\n<p>A transaction can be created without being signed, signed without being broadcast, seen by one node without being widely relayed, or included in a block. Those are different situations. Start with what your wallet actually reports, rather than treating every missing payment as the same problem.</p>\n<p>Write down the transaction identifier, the time you attempted the payment and whether the wallet reports confirmations. Keep private keys and recovery words out of your notes. If the payment came from a service account, also distinguish its withdrawal request from an actual Bitcoin transaction.</p>\n<h2 id=\"section-1\">Check the wallet before checking the internet</h2>\n<p>Confirm that the wallet is connected to the intended network and has finished synchronising. Compare the destination and amount with your own payment record. A watch-only wallet, an offline signer and an exchange account each expose different information; use the view that corresponds to the payment.</p>\n<p>A public explorer can help inspect a transaction, but querying it discloses an interest in that transaction to its operator. Prefer your own node or wallet’s transaction view when available. Do not paste an extended public key or seed phrase into a website to investigate a missing balance.</p>\n<h2 id=\"section-2\">Understand what waiting means</h2>\n<p>Confirmation depends on inclusion in a block. Blocks arrive irregularly and fee estimates change as demand changes. A displayed target is not a guarantee that your transaction will confirm after a particular number of minutes.</p>\n<p>If the payment is unconfirmed, inspect its fee rate and whether its inputs depend on another unconfirmed transaction. Compare against current conditions instead of a screenshot from an old tutorial. If there is no deadline, waiting may be a reasonable choice; establish the recipient’s expectations before paying extra.</p>\n<h2 id=\"section-3\">Use the wallet’s supported fee tools</h2>\n<p>Replace-by-fee creates a replacement transaction paying a higher fee. Bitcoin Core’s bumpfee documentation requires the transaction to be in the wallet and describes conditions that can prevent replacement. The additional fee may reduce change or require another input, so re-read the resulting transaction rather than approving it blindly.</p>\n<p>Child-pays-for-parent spends an output of the pending transaction with enough fee to make the combined package attractive. It requires control of a suitable output and software that supports the operation. Sparrow documents both approaches. Neither is a universal button that works for any transaction you can see.</p>\n<h2 id=\"section-4\">Keep the original payment in view</h2>\n<p>A fee replacement can produce a different transaction identifier. Save the new identifier with the original payment record so that you and the recipient are discussing the same event. Check the amount, destination and fee again on the signing device where applicable.</p>\n<p>Do not send a separate payment to the merchant as a substitute for understanding the first one. Both may eventually confirm. Equally, a transaction disappearing from one explorer does not prove it is cancelled everywhere. Ask the wallet or service for its documented resolution path before creating a conflicting payment.</p>\n<h2 id=\"section-5\">Ask for help with useful, limited information</h2>\n<p>A good support request says which wallet and network you use, whether it is synchronised, whether the transaction is confirmed, and what action you already tried. Share the transaction identifier only if you accept the associated privacy disclosure. Redact balances and unrelated addresses from screenshots.</p>\n<p>Anyone requesting a recovery phrase to accelerate a transaction is asking for spending authority, not diagnostic information. Pause when a proposed fix requires access you cannot explain. The objective is to resolve one payment while preserving control of the rest of the wallet.</p>",
      "words": 577
    },
    {
      "id": "privacy-beyond-the-wallet",
      "title": "Your phone is part of your Bitcoin setup",
      "category": "Privacy",
      "description": "A maintenance-first approach to operating systems, app permissions and recovery.",
      "minutes": 5,
      "sections": [
        {
          "heading": "Start with the device you actually use",
          "paragraphs": [
            "A careful wallet setup can still sit on a phone filled with sensitive screenshots, old applications and account sessions. Begin by listing the jobs that phone performs: payments, messaging, authentication, photography and recovery. The list reveals which failures would affect more than one part of your life.",
            "You do not need to replace everything in an afternoon. Choose one improvement you can maintain: installing available updates, removing an unused application, reviewing a permission or making sure an essential account can be recovered without the phone."
          ],
          "bullets": []
        },
        {
          "heading": "Support lifetime matters more than the label",
          "paragraphs": [
            "GrapheneOS documents why full device security depends on maintained firmware and other device-specific components. A phone that still boots is not necessarily receiving complete security updates. Check the exact model and support category, especially when buying an inexpensive older device.",
            "CalyxOS also publishes device support information. Its November 2026 update shows why old reports of a development pause should not be treated as a permanent description of the project. At the same time, an update announcement for the project is not proof that every supported model receives identical firmware or installation support."
          ],
          "bullets": []
        },
        {
          "heading": "Treat installation as a migration",
          "paragraphs": [
            "Installing an operating system can erase the phone. Before starting, identify your wallet’s documented migration process, export necessary account recovery material securely and check that you can access essential services from another device. Do not begin while that phone is your only route to the instructions or authentication.",
            "Use the project’s current installation guide for your exact device. GrapheneOS recommends its web installer for most users and includes bootloader locking and installation verification in the process. Skipping the final security steps because the home screen appears is not a complete installation."
          ],
          "bullets": []
        },
        {
          "heading": "Read warnings before borrowing a command",
          "paragraphs": [
            "CalyxOS publishes a device-specific anti-rollback notice for affected Motorola models. That is an example of why a generic flashing command from an old article can be inappropriate even when it once worked. Follow the project’s current notice rather than trying to force an installation through a mismatch.",
            "Keep the original guides in this library as background explanations. For supported models, image downloads, bootloader requirements and exact commands, the project documentation is the operational reference. Stop when the model or state differs from what the guide expects."
          ],
          "bullets": []
        },
        {
          "heading": "Reduce the amount of sensitive material on the phone",
          "paragraphs": [
            "Review wallet screenshots, clipboard history, cloud photo uploads and files exported while seeking help. Ask whether each item still needs to exist on this device. Keep recovery material according to the wallet’s documented backup model, not wherever a convenient share sheet happens to send it.",
            "Permissions deserve the same attention. Give an app the access required for the task you intend, then revisit that access when your use changes. Separating activities can help you reason about exposure, but a different profile or operating system does not erase identity information you voluntarily submit to a service."
          ],
          "bullets": []
        },
        {
          "heading": "Make maintenance a small recurring habit",
          "paragraphs": [
            "Choose a regular moment to check the OS update state, important app updates and the recovery notes for your payment setup. Read major release notes before relying on a changed workflow. If you use Lightning, consult the exact wallet’s migration instructions before replacing or restoring the phone.",
            "The best setup is one you can keep supported, recover deliberately and understand under pressure. A privacy-focused operating system can be one part of that arrangement; the daily choices around applications, accounts and records still matter."
          ],
          "bullets": [
            "Know the device’s support status.",
            "Keep a recovery route outside the device.",
            "Use current installation instructions.",
            "Finish boot verification and locking steps.",
            "Review applications and sensitive files regularly."
          ]
        }
      ],
      "sources": [
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        },
        {
          "title": "GrapheneOS: Official web installation",
          "url": "https://grapheneos.org/install/web"
        },
        {
          "title": "CalyxOS: Device support",
          "url": "https://calyxos.org/docs/guide/device-support/"
        },
        {
          "title": "CalyxOS: November 2026 security update",
          "url": "https://calyxos.org/news/2026/11/10/november-security-updates/"
        },
        {
          "title": "CalyxOS: Device-specific anti-rollback installation notice",
          "url": "https://calyxos.org/install/antirollback-update-pending/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "status": "reviewed",
      "language": "en",
      "listed": true,
      "html": "<h2 id=\"section-0\">Start with the device you actually use</h2>\n<p>A careful wallet setup can still sit on a phone filled with sensitive screenshots, old applications and account sessions. Begin by listing the jobs that phone performs: payments, messaging, authentication, photography and recovery. The list reveals which failures would affect more than one part of your life.</p>\n<p>You do not need to replace everything in an afternoon. Choose one improvement you can maintain: installing available updates, removing an unused application, reviewing a permission or making sure an essential account can be recovered without the phone.</p>\n<h2 id=\"section-1\">Support lifetime matters more than the label</h2>\n<p>GrapheneOS documents why full device security depends on maintained firmware and other device-specific components. A phone that still boots is not necessarily receiving complete security updates. Check the exact model and support category, especially when buying an inexpensive older device.</p>\n<p>CalyxOS also publishes device support information. Its November 2026 update shows why old reports of a development pause should not be treated as a permanent description of the project. At the same time, an update announcement for the project is not proof that every supported model receives identical firmware or installation support.</p>\n<h2 id=\"section-2\">Treat installation as a migration</h2>\n<p>Installing an operating system can erase the phone. Before starting, identify your wallet’s documented migration process, export necessary account recovery material securely and check that you can access essential services from another device. Do not begin while that phone is your only route to the instructions or authentication.</p>\n<p>Use the project’s current installation guide for your exact device. GrapheneOS recommends its web installer for most users and includes bootloader locking and installation verification in the process. Skipping the final security steps because the home screen appears is not a complete installation.</p>\n<h2 id=\"section-3\">Read warnings before borrowing a command</h2>\n<p>CalyxOS publishes a device-specific anti-rollback notice for affected Motorola models. That is an example of why a generic flashing command from an old article can be inappropriate even when it once worked. Follow the project’s current notice rather than trying to force an installation through a mismatch.</p>\n<p>Keep the original guides in this library as background explanations. For supported models, image downloads, bootloader requirements and exact commands, the project documentation is the operational reference. Stop when the model or state differs from what the guide expects.</p>\n<h2 id=\"section-4\">Reduce the amount of sensitive material on the phone</h2>\n<p>Review wallet screenshots, clipboard history, cloud photo uploads and files exported while seeking help. Ask whether each item still needs to exist on this device. Keep recovery material according to the wallet’s documented backup model, not wherever a convenient share sheet happens to send it.</p>\n<p>Permissions deserve the same attention. Give an app the access required for the task you intend, then revisit that access when your use changes. Separating activities can help you reason about exposure, but a different profile or operating system does not erase identity information you voluntarily submit to a service.</p>\n<h2 id=\"section-5\">Make maintenance a small recurring habit</h2>\n<p>Choose a regular moment to check the OS update state, important app updates and the recovery notes for your payment setup. Read major release notes before relying on a changed workflow. If you use Lightning, consult the exact wallet’s migration instructions before replacing or restoring the phone.</p>\n<p>The best setup is one you can keep supported, recover deliberately and understand under pressure. A privacy-focused operating system can be one part of that arrangement; the daily choices around applications, accounts and records still matter.</p>\n<ul><li>Know the device’s support status.</li><li>Keep a recovery route outside the device.</li><li>Use current installation instructions.</li><li>Finish boot verification and locking steps.</li><li>Review applications and sensitive files regularly.</li></ul>",
      "words": 600
    }
  ],
  "legacyUpdates": [
    {
      "slugs": [
        "whirlpool",
        "wpfees",
        "mobilecoinjoin",
        "doxxic",
        "paynym",
        "samourai",
        "rdmigrate",
        "dojo",
        "ronindojo"
      ],
      "status": "Historical guide",
      "notice": "This article preserves the original workflow. Do not assume the original Samourai/Whirlpool services or integrations are available. Sparrow removed its Whirlpool client in version 1.9.0. Use current project documentation before following software-specific steps.",
      "reviewed": "2026-11-12",
      "sources": [
        {
          "title": "Sparrow 1.9.0 release notes",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ]
    },
    {
      "slugs": [
        "blue"
      ],
      "status": "Updated context",
      "notice": "BlueWallet’s hosted Lndhub.io Lightning service was sunset in 2023. Its ordinary on-chain wallets and self-hosted LNDHub are separate. Historical hosted-Lightning instructions are not a current setup path.",
      "reviewed": "2026-11-12",
      "sources": [
        {
          "title": "BlueWallet: sunsetting Lndhub.io",
          "url": "https://bluewallet.io/sunsetting-lndhub/"
        }
      ]
    },
    {
      "slugs": [
        "coldcard",
        "sparrow",
        "passport",
        "csimplications",
        "multisig"
      ],
      "status": "Security context",
      "notice": "Some original examples reference COLDCARD. Read Coinkite’s 2026 seed-generation advisory and current migration guidance before following those examples. Updating firmware alone does not repair an existing affected seed. Preserve the original article’s security notices.",
      "reviewed": "2026-11-12",
      "sources": [
        {
          "title": "Coinkite security advisory",
          "url": "https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/"
        }
      ]
    },
    {
      "slugs": [
        "agora",
        "zap",
        "mynode",
        "specter",
        "node",
        "bisq",
        "hodlhodl",
        "hodlhodloffer",
        "peach",
        "robosats",
        "azteco",
        "grapheneos",
        "calyxos",
        "staging1234"
      ],
      "status": "Historical guide · review required",
      "notice": "Original article retained. Product availability, interface steps, fees and system requirements have not received a complete 2026 review. Check the project’s current official documentation before acting.",
      "reviewed": null,
      "sources": []
    }
  ],
  "editorialPolicy": {
    "reviewLabel": "Sources checked 12 November 2026",
    "legacyLabel": "Original guide · technical review pending",
    "claims": "Do not label the entire library fully verified. Dated, linked source reviews and targeted corrections do not certify every original step; no hardware or wallet transactions were performed.",
    "criticalPreservation": "Keep existing security warnings visible. Preserve all article text, dates, credit, images and downloads. Never silently promote historical workflows as current."
  },
  "originalReviews": [
    {
      "id": "404",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "about",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "advanced",
      "status": "review-required",
      "summary": "This directory contains a mix of enduring learning topics and time-sensitive product recommendations. Individual entries are not all certified current.",
      "corrections": [
        "Remove Whirlpool onboarding from current learning paths while retaining its archive.",
        "Avoid ranking products as best without a current, stated comparison.",
        "Availability and maintenance of every external project require individual checks."
      ],
      "sources": [
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        },
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "agora",
      "status": "historical",
      "summary": "The original AgoraDesk announced a 2024 wind-down. This walkthrough is an archive, not an available buying route.",
      "corrections": [
        "Do not direct readers to create new trades using this walkthrough.",
        "A different domain using the same brand has not been verified as a continuation of the original operator."
      ],
      "sources": [
        {
          "title": "AgoraDesk: Original service winding-down announcement",
          "url": "https://web.archive.org/web/20260620191832/https://agoradesk.com/blog/announcements/winding-down?language=en"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "articles",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "azteco",
      "status": "current-context",
      "summary": "Voucher workflows depend on the retailer, voucher type, fees and redemption conditions.",
      "corrections": [
        "Check on-chain versus Lightning redemption before purchasing.",
        "Do not state that every retailer requires no personal information.",
        "Protect the voucher code and inspect expiry and the actual payout quote."
      ],
      "sources": [
        {
          "title": "Azteco: Commission fees",
          "url": "https://help.azte.co/article/27-what-are-the-commission-fees"
        },
        {
          "title": "Azteco: Voucher redemption",
          "url": "https://azte.co/redeem"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "beginner",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "bisq",
      "status": "current-context",
      "summary": "The archived walkthrough describes a particular Bisq generation; product and security context has changed.",
      "corrections": [
        "Distinguish Bisq v1 from Bisq 2/Bisq Easy.",
        "Read the official May 2026 v1 incident postmortem and current release instructions.",
        "Deposits, fee rates, limits and screenshots must be checked against the exact installed product."
      ],
      "sources": [
        {
          "title": "Bisq: Getting started",
          "url": "https://bisq.network/getting-started/"
        },
        {
          "title": "Bisq: May 2026 security incident postmortem",
          "url": "https://bisq.network/blog/security-incident-post-mortem/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "blixt",
      "status": "current-context",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "calyxos",
      "status": "current-context",
      "summary": "Device support, firmware and installation requirements have changed since the archived screenshots.",
      "corrections": [
        "Use the current official supported-device list and installer for the exact device.",
        "Installation can wipe data; recovery and migration planning come first.",
        "An unlocked bootloader or unsupported firmware is not a completed secure setup.",
        "Check the current anti-rollback notice for affected Motorola models; do not repeat an old project-pause report as current."
      ],
      "sources": [
        {
          "title": "CalyxOS: Device support",
          "url": "https://calyxos.org/docs/guide/device-support/"
        },
        {
          "title": "CalyxOS: November 2026 security update",
          "url": "https://calyxos.org/news/2026/11/10/november-security-updates/"
        },
        {
          "title": "CalyxOS: Device-specific anti-rollback installation notice",
          "url": "https://calyxos.org/install/antirollback-update-pending/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-beyond-the-wallet"
    },
    {
      "id": "client-form",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "contact",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "contribute",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "convert",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "convert-new",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "csimplications",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "doxxic",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "fork",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "grapheneos",
      "status": "current-context",
      "summary": "Device support, firmware and installation requirements have changed since the archived screenshots.",
      "corrections": [
        "Use the current official supported-device list and installer for the exact device.",
        "Installation can wipe data; recovery and migration planning come first.",
        "An unlocked bootloader or unsupported firmware is not a completed secure setup."
      ],
      "sources": [
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        },
        {
          "title": "GrapheneOS: Official web installation",
          "url": "https://grapheneos.org/install/web"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-beyond-the-wallet"
    },
    {
      "id": "graphics",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "hodlhodl",
      "status": "current-context",
      "summary": "The general P2P trade idea remains useful, but this is a platform-operated marketplace with a specific escrow and dispute process.",
      "corrections": [
        "Do not equate non-custodial escrow with a fully decentralised operator or guaranteed anonymity.",
        "Bank/payment rails can reveal identity independently of platform registration.",
        "Use current contract terms and displayed fees rather than the archived examples."
      ],
      "sources": [
        {
          "title": "Hodl Hodl: Exchange FAQ",
          "url": "https://hodlhodl.com/pages/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "hodlhodloffer",
      "status": "current-context",
      "summary": "The general P2P trade idea remains useful, but this is a platform-operated marketplace with a specific escrow and dispute process.",
      "corrections": [
        "Do not equate non-custodial escrow with a fully decentralised operator or guaranteed anonymity.",
        "Bank/payment rails can reveal identity independently of platform registration.",
        "Use current contract terms and displayed fees rather than the archived examples."
      ],
      "sources": [
        {
          "title": "Hodl Hodl: Exchange FAQ",
          "url": "https://hodlhodl.com/pages/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "index",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "intermediate",
      "status": "review-required",
      "summary": "This directory contains a mix of enduring learning topics and time-sensitive product recommendations. Individual entries are not all certified current.",
      "corrections": [
        "Remove Whirlpool onboarding from current learning paths while retaining its archive.",
        "Avoid ranking products as best without a current, stated comparison.",
        "Availability and maintenance of every external project require individual checks."
      ],
      "sources": [
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        },
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "lightning",
      "status": "current-context",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "lostbitcoin",
      "status": "current-context",
      "summary": "The practical cautionary themes remain useful, but claims that all risks can be completely mitigated are too absolute.",
      "corrections": [
        "Replace guarantees with risk reduction and tested recovery.",
        "Do not treat every missing or delayed balance as loss.",
        "Distinguish signing authority, backup loss, provider failure and transaction delay."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Core: bumpfee RPC reference",
          "url": "https://bitcoincore.org/en/doc/30.0.0/rpc/wallet/bumpfee/"
        },
        {
          "title": "Sparrow: Frequently asked questions",
          "url": "https://sparrowwallet.com/docs/faq.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "transaction-troubleshooting"
    },
    {
      "id": "mobilecoinjoin",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "nokyconly",
      "status": "current-context",
      "summary": "Acquisition privacy remains a useful topic, but service availability and blanket regulatory statements need qualification.",
      "corrections": [
        "Do not repeat unsupported market-share percentages or universal legal claims.",
        "Original AgoraDesk is historical.",
        "Separate platform identity collection from bank and counterparty records."
      ],
      "sources": [
        {
          "title": "AgoraDesk: Original service winding-down announcement",
          "url": "https://web.archive.org/web/20260620191832/https://agoradesk.com/blog/announcements/winding-down?language=en"
        },
        {
          "title": "Peach: Terms and conditions",
          "url": "https://peachbitcoin.com/terms-and-conditions/"
        },
        {
          "title": "RoboSats: Quick start",
          "url": "https://docs.robosats.org/docs/quick-start/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "paynym",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Distinguish reusable payment codes from reusing a Bitcoin address.",
        "BIP47 support and collaborative features are separate; validate current wallet interoperability.",
        "Sparrow removed Soroban-related features with the Whirlpool client; do not assume every old collaborative screenshot remains available."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "peach",
      "status": "current-context",
      "summary": "Current Peach terms describe jurisdiction-dependent availability and a defined escrow structure; the original universal no-KYC framing needs qualification.",
      "corrections": [
        "Check current jurisdiction restrictions, conditions and limits.",
        "Use current escrow and recovery documentation, including wallet address gap limits where relevant.",
        "Keep promotional claims separate from guarantees about privacy or counterparty risk."
      ],
      "sources": [
        {
          "title": "Peach: Terms and conditions",
          "url": "https://peachbitcoin.com/terms-and-conditions/"
        },
        {
          "title": "Peach: Account and recovery FAQ",
          "url": "https://peachbitcoin.com/faq/account/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "podcasts",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "privacy--get",
      "status": "current-context",
      "summary": "Acquisition privacy remains a useful topic, but service availability and blanket regulatory statements need qualification.",
      "corrections": [
        "Do not repeat unsupported market-share percentages or universal legal claims.",
        "Original AgoraDesk is historical.",
        "Separate platform identity collection from bank and counterparty records."
      ],
      "sources": [
        {
          "title": "AgoraDesk: Original service winding-down announcement",
          "url": "https://web.archive.org/web/20260620191832/https://agoradesk.com/blog/announcements/winding-down?language=en"
        },
        {
          "title": "Peach: Terms and conditions",
          "url": "https://peachbitcoin.com/terms-and-conditions/"
        },
        {
          "title": "RoboSats: Quick start",
          "url": "https://docs.robosats.org/docs/quick-start/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "privacy",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--safeguard",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context.",
        "Cold storage describes keeping spending keys offline; internet-connected watch-only software can still be part of the setup."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--scrutinise",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--secure",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--segregate",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--separate",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--spend",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context.",
        "Do not prescribe making every spend a coinjoin regardless of wallet support, fees or the user’s threat model."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacy--supplementary",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "privacytips",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--coinjoin",
      "status": "current-context",
      "summary": "Core privacy concepts are retained with an updated practical companion; product-specific claims and archived steps remain historical where applicable.",
      "corrections": [
        "Treat privacy as protection against specified observers, not an anonymity guarantee.",
        "Separate network/server privacy from on-chain linkage and payment identity.",
        "Old Samourai/Whirlpool recommendations need historical context."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: Protect your privacy",
          "url": "https://bitcoin.org/en/protect-your-privacy"
        },
        {
          "title": "Sparrow: Connection and wallet setup",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow: Spending privately",
          "url": "https://sparrowwallet.com/docs/spending-privately.html"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--common",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--education",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Retain original assets and text; verify external destinations when converting this into a live service."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "qna--glossary",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--lightning",
      "status": "current-context",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "qna--mistakes",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--myths",
      "status": "current-context",
      "summary": "Foundational concepts have a new companion; the original FAQ remains available and is not relabelled as a fully rewritten current guide.",
      "corrections": [
        "Distinguish wallets, private keys, nodes and miners.",
        "A balance is composed of spendable outputs; an address is not an account or a guaranteed identity.",
        "Avoid guaranteed returns, exact confirmation-time promises and absolute privacy claims."
      ],
      "sources": [
        {
          "title": "Bitcoin.org: How Bitcoin works",
          "url": "https://bitcoin.org/en/how-it-works"
        },
        {
          "title": "Bitcoin.org: Things you need to know",
          "url": "https://bitcoin.org/en/you-need-to-know"
        },
        {
          "title": "Bitcoin Developer Guide: Transactions",
          "url": "https://developer.bitcoin.org/devguide/transactions.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--nodes",
      "status": "current-context",
      "summary": "Deliberately connect a wallet to the node whose validation you want to use.",
      "corrections": [
        "Deliberately connect a wallet to the node whose validation you want to use.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "qna--recommendations",
      "status": "review-required",
      "summary": "This directory contains a mix of enduring learning topics and time-sensitive product recommendations. Individual entries are not all certified current.",
      "corrections": [
        "Remove Whirlpool onboarding from current learning paths while retaining its archive.",
        "Avoid ranking products as best without a current, stated comparison.",
        "Availability and maintenance of every external project require individual checks."
      ],
      "sources": [
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        },
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--wallets",
      "status": "current-context",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "rdmigrate",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "robosats",
      "status": "current-context",
      "summary": "The core Lightning hold-invoice workflow is documented by RoboSats; original screenshots and numerical examples remain version-specific.",
      "corrections": [
        "Check the current coordinator and official documentation.",
        "Distinguish bonds, escrow, fees and on-chain payout options.",
        "No identity-document upload does not mean the fiat payment rail is anonymous."
      ],
      "sources": [
        {
          "title": "RoboSats: Quick start",
          "url": "https://docs.robosats.org/docs/quick-start/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "samourai",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "staging1234",
      "status": "current-context",
      "summary": "Device support, firmware and installation requirements have changed since the archived screenshots.",
      "corrections": [
        "Use the current official supported-device list and installer for the exact device.",
        "Installation can wipe data; recovery and migration planning come first.",
        "An unlocked bootloader or unsupported firmware is not a completed secure setup."
      ],
      "sources": [
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        },
        {
          "title": "GrapheneOS: Official web installation",
          "url": "https://grapheneos.org/install/web"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-beyond-the-wallet"
    },
    {
      "id": "support",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "tips",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "toolkit",
      "status": "review-required",
      "summary": "This directory contains a mix of enduring learning topics and time-sensitive product recommendations. Individual entries are not all certified current.",
      "corrections": [
        "Remove Whirlpool onboarding from current learning paths while retaining its archive.",
        "Avoid ranking products as best without a current, stated comparison.",
        "Availability and maintenance of every external project require individual checks."
      ],
      "sources": [
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        },
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "GrapheneOS: Device support and security FAQ",
          "url": "https://grapheneos.org/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "vote",
      "status": "preserved-reference",
      "summary": "Original page retained. This is a utility, directory, personal or service page; preservation is not a claim that external links, contact details, quoted prices or integrations have been revalidated.",
      "corrections": [
        "Do not add a technical-review badge to personal claims or service availability.",
        "Archived forms and payment controls must not imply a live backend in this local experiment."
      ],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "wallet--lightning",
      "status": "current-context",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "whirlpool",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "wpfees",
      "status": "historical",
      "summary": "This page relies on the original Samourai/Whirlpool ecosystem or its historical migration workflow. Preserve it for context; use current wallet-specific recovery documentation before acting.",
      "corrections": [
        "Samourai infrastructure was seized in April 2024; the original service setup is not a current onboarding path.",
        "Sparrow removed its Whirlpool client in release 1.9.0.",
        "Historical fee diagrams, installation steps and claims of guaranteed unlinkability are not current operational guidance."
      ],
      "sources": [
        {
          "title": "US Department of Justice: April 2024 Samourai infrastructure seizure",
          "url": "https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering"
        },
        {
          "title": "Sparrow 1.9.0: Whirlpool client removed",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "zap",
      "status": "review-required",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually.",
        "Zap maintenance and current app-store availability were not established in this review."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "zeus",
      "status": "current-context",
      "summary": "Lightning wallet roles and recovery differ by implementation; the archived brand list and screen steps are not a current compatibility matrix.",
      "corrections": [
        "Distinguish custody, an embedded node and a remote node controller.",
        "ZEUS supports local wallet modes as well as remote connections.",
        "Use the exact implementation’s backup and migration instructions; do not restore active channel state casually."
      ],
      "sources": [
        {
          "title": "ZEUS: Wallet connection types",
          "url": "https://docs.zeusln.app/for-users/using-zeus/wallets/"
        },
        {
          "title": "ZEUS: Embedded LND FAQ",
          "url": "https://docs.zeusln.app/for-users/local-wallets/embedded-lnd/faq/"
        },
        {
          "title": "ZEUS: LDK backup and recovery",
          "url": "https://docs.zeusln.app/for-users/local-wallets/ldk-node/backup-and-recovery/"
        },
        {
          "title": "Blixt: Wallet, channels and recovery FAQ",
          "url": "https://blixtwallet.github.io/faq"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "blue",
      "status": "historical",
      "summary": "Use current on-chain and watch-only setup instructions.",
      "corrections": [
        "Back up each wallet separately.",
        "Hosted Lndhub.io retired in 2023; do not present it as a current onboarding path."
      ],
      "sources": [
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        },
        {
          "title": "Lndhub retirement",
          "url": "https://bluewallet.io/sunsetting-lndhub/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bluewallet-2026"
    },
    {
      "id": "coldcard",
      "status": "historical",
      "summary": "Historical device tutorial with material 2026 security context.",
      "corrections": [
        "Preserve the original warning.",
        "Consult the vendor advisory for affected firmware and independent-entropy exceptions.",
        "A firmware update does not repair an existing affected seed."
      ],
      "sources": [
        {
          "title": "Coinkite security advisory",
          "url": "https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "recovery-rehearsal"
    },
    {
      "id": "dojo",
      "status": "historical",
      "summary": "Original XPUB rescan steps are backend-specific.",
      "corrections": [
        "Do not assume original hosted backends are available.",
        "Use current backend docs for matching derivation and scan range.",
        "Old rescan commands were not executed."
      ],
      "sources": [
        {
          "title": "RoninDojo docs",
          "url": "https://docs.ronindojo.io/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "multisig--backup",
      "status": "current-context",
      "summary": "Preserve the complete policy alongside independent key backups.",
      "corrections": [
        "Preserve the complete policy alongside independent key backups.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--blue",
      "status": "historical",
      "summary": "Vault coordination exports and signing-key backups serve different roles.",
      "corrections": [
        "Vault coordination exports and signing-key backups serve different roles.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig",
      "status": "current-context",
      "summary": "Multisig needs a recoverable policy and rehearsed independent signers.",
      "corrections": [
        "Multisig needs a recoverable policy and rehearsed independent signers.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--intro",
      "status": "current-context",
      "summary": "Threshold security depends on independent failure domains.",
      "corrections": [
        "Threshold security depends on independent failure domains.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--receive",
      "status": "historical",
      "summary": "Verify policy and receive address on supported signers before funding.",
      "corrections": [
        "Verify policy and receive address on supported signers before funding.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--recover",
      "status": "historical",
      "summary": "Reconstruct and identify the public wallet before restoring signing authority.",
      "corrections": [
        "Reconstruct and identify the public wallet before restoring signing authority.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--shopping",
      "status": "historical",
      "summary": "Product comparisons and prices are historical.",
      "corrections": [
        "Product comparisons and prices are historical.",
        "Context review does not certify every historical screenshot.",
        "Preserve COLDCARD advisory context and check current vendor guidance."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        },
        {
          "title": "Coinkite security advisory",
          "url": "https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--signers",
      "status": "current-context",
      "summary": "Use independent signers with current model-specific instructions.",
      "corrections": [
        "Use independent signers with current model-specific instructions.",
        "Context review does not certify every historical screenshot.",
        "Preserve COLDCARD advisory context and check current vendor guidance."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        },
        {
          "title": "Coinkite security advisory",
          "url": "https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--software",
      "status": "historical",
      "summary": "Check coordinator, signer, policy and PSBT compatibility.",
      "corrections": [
        "Check coordinator, signer, policy and PSBT compatibility.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--spend",
      "status": "historical",
      "summary": "Review recipient, amount, fee and change on signers; broadcast is separate.",
      "corrections": [
        "Review recipient, amount, fee and change on signers; broadcast is separate.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--ssparts",
      "status": "historical",
      "summary": "Use current SeedSigner hardware documentation instead of a historical parts list.",
      "corrections": [
        "Use current SeedSigner hardware documentation instead of a historical parts list.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        },
        {
          "title": "SeedSigner source",
          "url": "https://github.com/SeedSigner/seedsigner"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "multisig--wallet",
      "status": "historical",
      "summary": "Export complete configuration and verify cosigner membership.",
      "corrections": [
        "Export complete configuration and verify cosigner membership.",
        "Context review does not certify every historical screenshot."
      ],
      "sources": [
        {
          "title": "BIP129 multisig setup",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0129.mediawiki"
        },
        {
          "title": "BIP380 descriptors",
          "url": "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "mynode",
      "status": "historical",
      "summary": "MyNode has current documentation; original installation screens remain historical.",
      "corrections": [
        "Check current supported hardware.",
        "Budget for bundled apps as well as Core.",
        "Back up wallet and Lightning state separately from downloadable chain data."
      ],
      "sources": [
        {
          "title": "MyNode introduction",
          "url": "https://docs.mynodebtc.com/intro/introduction.html"
        },
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--about",
      "status": "current-context",
      "summary": "Validation, mining and wallet custody are different responsibilities.",
      "corrections": [
        "Validation, mining and wallet custody are different responsibilities.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--compare",
      "status": "historical",
      "summary": "Hardware and bundle comparisons are dated purchasing information.",
      "corrections": [
        "Hardware and bundle comparisons are dated purchasing information.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--core",
      "status": "historical",
      "summary": "Use current Core downloads and verification instructions.",
      "corrections": [
        "Use current Core downloads and verification instructions.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--diy",
      "status": "historical",
      "summary": "Check current hardware, OS and storage requirements.",
      "corrections": [
        "Check current hardware, OS and storage requirements.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node",
      "status": "current-context",
      "summary": "Deliberately connect a wallet to the node whose validation you want to use.",
      "corrections": [
        "Deliberately connect a wallet to the node whose validation you want to use.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--other",
      "status": "historical",
      "summary": "Alternative distributions have separate maintenance and trust assumptions.",
      "corrections": [
        "Alternative distributions have separate maintenance and trust assumptions.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "node--pap",
      "status": "historical",
      "summary": "Prebuilt nodes still need updates, access controls and backups.",
      "corrections": [
        "Prebuilt nodes still need updates, access controls and backups.",
        "Pruning can limit historical wallet rescans.",
        "Keep administrative RPC private."
      ],
      "sources": [
        {
          "title": "Full node guide",
          "url": "https://bitcoin.org/en/full-node"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "opendime",
      "status": "current-context",
      "summary": "A sealed bearer device has a different recovery model from a seed-backed wallet.",
      "corrections": [
        "Verify address, balance and sealed state.",
        "Physical handover is off-chain; funding and sweeping are on-chain.",
        "Unsealing is irreversible."
      ],
      "sources": [
        {
          "title": "Opendime documentation",
          "url": "https://opendime.com/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "passport",
      "status": "historical",
      "summary": "The original article predates the current Core/Prime documentation split.",
      "corrections": [
        "Choose the exact model before following setup steps.",
        "Core encrypted microSD recovery requires its backup code.",
        "Use Prime-specific recovery instructions for Prime."
      ],
      "sources": [
        {
          "title": "Core setup",
          "url": "https://docs.foundation.xyz/passport/setup/"
        },
        {
          "title": "Prime docs",
          "url": "https://docs.foundation.xyz/prime/home/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "passport-2026"
    },
    {
      "id": "pgp",
      "status": "current-context",
      "summary": "OpenPGP concepts remain useful; verification needs an expected key identity.",
      "corrections": [
        "Distinguish valid signature from trusted identity.",
        "Check full key fingerprints.",
        "Verify the intended data file, not just a similarly named signature."
      ],
      "sources": [
        {
          "title": "GnuPG commands",
          "url": "https://www.gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "verify-downloads-2026"
    },
    {
      "id": "ronindojo",
      "status": "historical",
      "summary": "Use current RoninDojo platform and wallet-integration documentation.",
      "corrections": [
        "Current docs distinguish hardware platforms and installation modes.",
        "Check the chosen wallet and indexer combination.",
        "A node does not make public on-chain activity untraceable."
      ],
      "sources": [
        {
          "title": "RoninDojo docs",
          "url": "https://docs.ronindojo.io/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "seed",
      "status": "review-required",
      "summary": "The preserved Seed Tool is not newly certified by this overhaul.",
      "corrections": [
        "Preserve the signed release unchanged.",
        "Use dummy examples in the redesigned interface.",
        "No new cryptographic audit or latest-version assertion was performed."
      ],
      "sources": [
        {
          "title": "Seed Tool repository",
          "url": "https://github.com/BitcoinQnA/seedtool"
        }
      ],
      "reviewed": "2026-11-12"
    },
    {
      "id": "sentinel",
      "status": "review-required",
      "summary": "Watch-only operation is documented; current distribution and backend operation remain unvalidated.",
      "corrections": [
        "Public exports can reveal financial history.",
        "Watch-only access does not back up spending authority.",
        "Historical screenshots do not establish current service availability."
      ],
      "sources": [
        {
          "title": "Sentinel source",
          "url": "https://github.com/Samourai-Wallet/sentinel-android"
        },
        {
          "title": "Sentinel product documentation",
          "url": "https://web.archive.org/web/20260107174311/https://samouraiwallet.com/sentinel"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bluewallet-2026"
    },
    {
      "id": "sparrow",
      "status": "historical",
      "summary": "Use the current counterpart for setup and transaction review.",
      "corrections": [
        "Verify installer, manifest and signature for the same release.",
        "Choose server connectivity deliberately.",
        "Whirlpool was removed in 1.9.0.",
        "Preserve COLDCARD security context."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "Sparrow releases",
          "url": "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "sparrow-2026"
    },
    {
      "id": "specter",
      "status": "historical",
      "summary": "Specter remains documented as a Core coordinator; old UI steps remain historical.",
      "corrections": [
        "Check device compatibility in the project docs.",
        "Keep Core RPC private.",
        "Preserve complete wallet configuration backups."
      ],
      "sources": [
        {
          "title": "Specter repository",
          "url": "https://github.com/cryptoadvance/specter-desktop"
        },
        {
          "title": "Core RPC security",
          "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "multisig-backup-2026"
    },
    {
      "id": "stack-duo",
      "status": "historical",
      "summary": "The Stack Duo repository was archived on 24 September 2026. This is a historical illustrated walkthrough, separate from Stack Wallet.",
      "corrections": [
        "Do not conflate Stack Duo with the broader Stack Wallet.",
        "Use its specific release channel and backup procedure.",
        "Historical screenshots do not guarantee current compatibility."
      ],
      "sources": [
        {
          "title": "Stack Duo repository",
          "url": "https://github.com/cypherstack/stack_duo"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "verify",
      "status": "current-context",
      "summary": "Supply inspection requires a block height and a clear definition of the amount measured.",
      "corrections": [
        "Use help for the installed Core RPC version.",
        "Record height and chain state with the result.",
        "UTXO total is not a count of coins whose owners can still access them."
      ],
      "sources": [
        {
          "title": "Versioned gettxoutsetinfo reference",
          "url": "https://bitcoincore.org/en/doc/30.0.0/rpc/blockchain/gettxoutsetinfo/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "verifysoftware",
      "status": "current-context",
      "summary": "Use the new verification workflow for a complete trust chain.",
      "corrections": [
        "Authenticate the manifest with the expected signer.",
        "Match the actual installer hash.",
        "Replace obsolete example filenames and check current signing keys."
      ],
      "sources": [
        {
          "title": "GnuPG commands",
          "url": "https://www.gnupg.org/documentation/manuals/gnupg/Operational-GPG-Commands.html"
        },
        {
          "title": "Bitcoin Core downloads",
          "url": "https://bitcoincore.org/en/download/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "verify-downloads-2026"
    },
    {
      "id": "wallet--about",
      "status": "current-context",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "wallet--compare",
      "status": "historical",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "wallet--desktop",
      "status": "historical",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "wallet--hardware",
      "status": "historical",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "wallet",
      "status": "current-context",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "wallet--mobile",
      "status": "historical",
      "summary": "Choose by custody, recovery, verification and compatibility rather than a dated ranking.",
      "corrections": [
        "Historical product lists are not a current endorsement.",
        "Distinguish software signing, hardware signing and watch-only access.",
        "Match backup requirements to the actual wallet."
      ],
      "sources": [
        {
          "title": "Sparrow quick start",
          "url": "https://sparrowwallet.com/docs/quick-start.html"
        },
        {
          "title": "BlueWallet docs",
          "url": "https://bluewallet.io/docs/"
        }
      ],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "lightning--de",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "lightning--fr",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "nokyconly--de",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "nokyconly--es",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "nokyconly--fr",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "nokyconly--it",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "peer-to-peer-first-trade"
    },
    {
      "id": "qna--de--coinjoin",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--de--common",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de--education",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "qna--de--glossary",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de--lightning",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "qna--de--mistakes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de--myths",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de--nodes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "qna--de--recommendations",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--de--wallets",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "qna--es--coinjoin",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--es--common",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es--education",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "qna--es--glossary",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es--lightning",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "qna--es--mistakes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es--myths",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es--nodes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "qna--es--recommendations",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--es--wallets",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "qna--fr--coinjoin",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--fr--common",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr--education",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "qna--fr--glossary",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr--lightning",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "qna--fr--mistakes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr--myths",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr--nodes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "qna--fr--recommendations",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--fr--wallets",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "qna--it--coinjoin",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "privacy-as-a-routine"
    },
    {
      "id": "qna--it--common",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it--education",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12"
    },
    {
      "id": "qna--it--glossary",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it--lightning",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "lightning-wallet-map"
    },
    {
      "id": "qna--it--mistakes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it--myths",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it--nodes",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "qna--it--recommendations",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-in-plain-english"
    },
    {
      "id": "qna--it--wallets",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "first-self-custody"
    },
    {
      "id": "verify--de",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "verify--es",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    },
    {
      "id": "verify--fr",
      "status": "translation-pending",
      "summary": "Original translation preserved. Product-specific instructions and screenshots have not been revalidated in this language.",
      "corrections": [],
      "sources": [],
      "reviewed": "2026-11-12",
      "successorId": "bitcoin-core-2026"
    }
  ],
  "limits": [
    "Historical screenshots remain, explicitly separated from current guidance.",
    "Translations have localized update summaries and retain translation-pending status; not a complete language review.",
    "Private offers, author biography, payment endpoints and external services were not exercised or invented.",
    "No hardware, seed recovery, live trades, payments or real-fund transactions were performed.",
    "Not every external resource has been substantively re-reviewed.",
    "Seed Tool cryptographic implementation was preserved, not independently audited."
  ],
  "targetedRevision": {
    "date": "2026-11-12",
    "correctionRules": 82,
    "currentContextModules": 53,
    "translatedUpdateSummaries": [
      "lightning--de",
      "lightning--fr",
      "nokyconly--de",
      "nokyconly--es",
      "nokyconly--fr",
      "nokyconly--it",
      "qna--de",
      "qna--es",
      "qna--fr",
      "qna--it",
      "verify--de",
      "verify--es",
      "verify--fr"
    ],
    "applications": [
      {
        "document": "verify",
        "subject": "verify",
        "revision": 1,
        "title": "What this audit measures"
      },
      {
        "document": "verify",
        "subject": "verify",
        "revision": 2,
        "title": "Use the block height, not the publication date"
      },
      {
        "document": "verify",
        "subject": "verify",
        "revision": 3,
        "title": "The fourth era is historical"
      },
      {
        "document": "verify",
        "subject": "verify",
        "revision": 4,
        "title": "Read the result precisely"
      },
      {
        "document": "node--core",
        "subject": "node--core",
        "revision": 5,
        "title": "Plan storage for today’s workload"
      },
      {
        "document": "node",
        "subject": "node--core",
        "revision": 5,
        "title": "Plan storage for today’s workload"
      },
      {
        "document": "node--core",
        "subject": "node--core",
        "revision": 6,
        "title": "Budget for the complete node"
      },
      {
        "document": "node",
        "subject": "node--core",
        "revision": 6,
        "title": "Budget for the complete node"
      },
      {
        "document": "mynode",
        "subject": "mynode",
        "revision": 7,
        "title": "Current myNode storage guidance"
      },
      {
        "document": "ronindojo",
        "subject": "ronindojo",
        "revision": 8,
        "title": "Use the current installation path"
      },
      {
        "document": "node--pap",
        "subject": "node--pap",
        "revision": 9,
        "title": "Check availability before shopping"
      },
      {
        "document": "node",
        "subject": "node--pap",
        "revision": 9,
        "title": "Check availability before shopping"
      },
      {
        "document": "lostbitcoin",
        "subject": "lostbitcoin",
        "revision": 10,
        "title": "Reduce risk; do not promise its elimination"
      },
      {
        "document": "lostbitcoin",
        "subject": "lostbitcoin",
        "revision": 11,
        "title": "Recovery words need the right wallet context"
      },
      {
        "document": "lostbitcoin",
        "subject": "lostbitcoin",
        "revision": 12,
        "title": "A passphrase is not another checksum word"
      },
      {
        "document": "lostbitcoin",
        "subject": "lostbitcoin",
        "revision": 13,
        "title": "Start with a maintainable setup"
      },
      {
        "document": "opendime",
        "subject": "opendime",
        "revision": 14,
        "title": "A physical handoff does not erase the chain"
      },
      {
        "document": "opendime",
        "subject": "opendime",
        "revision": 15,
        "title": "Verify the bearer instrument before accepting it"
      },
      {
        "document": "privacytips",
        "subject": "privacytips",
        "revision": 16,
        "title": "Separate encryption from routing privacy"
      },
      {
        "document": "privacytips",
        "subject": "privacytips",
        "revision": 17,
        "title": "Coinjoin creates uncertainty, not a guarantee"
      },
      {
        "document": "csimplications",
        "subject": "csimplications",
        "revision": 18,
        "title": "Deletion cannot undo earlier exposure"
      },
      {
        "document": "csimplications",
        "subject": "csimplications",
        "revision": 19,
        "title": "Do not run the old deletion commands as a setup step"
      },
      {
        "document": "rdmigrate",
        "subject": "rdmigrate",
        "revision": 20,
        "title": "Keep the working wallet until recovery is established"
      },
      {
        "document": "rdmigrate",
        "subject": "rdmigrate",
        "revision": 21,
        "title": "Historical coordinator connection"
      },
      {
        "document": "dojo",
        "subject": "dojo",
        "revision": 22,
        "title": "Rescan public wallet data, not your seed"
      },
      {
        "document": "multisig--backup",
        "subject": "multisig--backup",
        "revision": 23,
        "title": "Back up the wallet map as well as the keys"
      },
      {
        "document": "multisig",
        "subject": "multisig--backup",
        "revision": 23,
        "title": "Back up the wallet map as well as the keys"
      },
      {
        "document": "multisig--recover",
        "subject": "multisig--recover",
        "revision": 24,
        "title": "Rehearse reconstruction before relying on it"
      },
      {
        "document": "multisig",
        "subject": "multisig--recover",
        "revision": 24,
        "title": "Rehearse reconstruction before relying on it"
      },
      {
        "document": "multisig--ssparts",
        "subject": "multisig--ssparts",
        "revision": 25,
        "title": "Match the exact SeedSigner components"
      },
      {
        "document": "multisig",
        "subject": "multisig--ssparts",
        "revision": 25,
        "title": "Match the exact SeedSigner components"
      },
      {
        "document": "multisig--shopping",
        "subject": "multisig--shopping",
        "revision": 26,
        "title": "Choose supported models and firmware together"
      },
      {
        "document": "multisig",
        "subject": "multisig--shopping",
        "revision": 26,
        "title": "Choose supported models and firmware together"
      },
      {
        "document": "passport",
        "subject": "passport",
        "revision": 27,
        "title": "Know which backup you are restoring"
      },
      {
        "document": "paynym",
        "subject": "paynym",
        "revision": 28,
        "title": "Payment codes and app support are separate"
      },
      {
        "document": "hodlhodl",
        "subject": "hodlhodl",
        "revision": 29,
        "title": "Read the current contract and fees"
      },
      {
        "document": "hodlhodloffer",
        "subject": "hodlhodloffer",
        "revision": 30,
        "title": "Set the full offer terms"
      },
      {
        "document": "azteco",
        "subject": "azteco",
        "revision": 31,
        "title": "Match the voucher to the payment network"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 32,
        "title": "Android Auto support has changed"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 32,
        "title": "Android Auto support has changed"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 33,
        "title": "SimpleX now has desktop clients"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 33,
        "title": "SimpleX now has desktop clients"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 34,
        "title": "Proton Drive has native desktop support"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 34,
        "title": "Proton Drive has native desktop support"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 35,
        "title": "Skiff has closed"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 35,
        "title": "Skiff has closed"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 36,
        "title": "Signal can separate contact from number sharing"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 36,
        "title": "Signal can separate contact from number sharing"
      },
      {
        "document": "grapheneos",
        "subject": "grapheneos",
        "revision": 37,
        "title": "Check support lifetime before buying"
      },
      {
        "document": "staging1234",
        "subject": "staging1234",
        "revision": 37,
        "title": "Check support lifetime before buying"
      },
      {
        "document": "toolkit",
        "subject": "toolkit",
        "revision": 38,
        "title": "andOTP is unmaintained"
      },
      {
        "document": "toolkit",
        "subject": "toolkit",
        "revision": 39,
        "title": "The Pixel 5 listing is historical"
      },
      {
        "document": "toolkit",
        "subject": "toolkit",
        "revision": 40,
        "title": "Telegram group chat is not end-to-end encrypted"
      },
      {
        "document": "wallet--mobile",
        "subject": "wallet--mobile",
        "revision": 41,
        "title": "On-chain wallets continue; hosted Lightning changed"
      },
      {
        "document": "wallet",
        "subject": "wallet--mobile",
        "revision": 41,
        "title": "On-chain wallets continue; hosted Lightning changed"
      },
      {
        "document": "wallet--lightning",
        "subject": "wallet--lightning",
        "revision": 42,
        "title": "Historical application"
      },
      {
        "document": "wallet",
        "subject": "wallet--lightning",
        "revision": 42,
        "title": "Historical application"
      },
      {
        "document": "qna--common",
        "subject": "qna--common",
        "revision": 43,
        "title": "Supply is a height-based calculation"
      },
      {
        "document": "qna",
        "subject": "qna--common",
        "revision": 43,
        "title": "Supply is a height-based calculation"
      },
      {
        "document": "qna--common",
        "subject": "qna--common",
        "revision": 44,
        "title": "The 2024 halving is already in the past"
      },
      {
        "document": "qna",
        "subject": "qna--common",
        "revision": 44,
        "title": "The 2024 halving is already in the past"
      },
      {
        "document": "qna--common",
        "subject": "qna--common",
        "revision": 45,
        "title": "Validation and block selection are different powers"
      },
      {
        "document": "qna",
        "subject": "qna--common",
        "revision": 45,
        "title": "Validation and block selection are different powers"
      },
      {
        "document": "fork",
        "subject": "fork",
        "revision": 46,
        "title": "Use the repository’s declared toolchain"
      },
      {
        "document": "whirlpool",
        "subject": "whirlpool",
        "revision": 47,
        "title": "These pool fees are historical"
      },
      {
        "document": "doxxic",
        "subject": "doxxic",
        "revision": 48,
        "title": "Review the output before choosing a technique"
      },
      {
        "document": "wpfees",
        "subject": "wpfees",
        "revision": 49,
        "title": "A worked example from the original service"
      },
      {
        "document": "mobilecoinjoin",
        "subject": "mobilecoinjoin",
        "revision": 50,
        "title": "The screenshots document the old client"
      },
      {
        "document": "samourai",
        "subject": "samourai",
        "revision": 51,
        "title": "Features here describe the original release"
      },
      {
        "document": "advanced",
        "subject": "advanced",
        "revision": 52,
        "title": "Learn the technique without reviving old setup instructions"
      },
      {
        "document": "beginner",
        "subject": "beginner",
        "revision": 53,
        "title": "Use a current wallet profile"
      },
      {
        "document": "intermediate",
        "subject": "intermediate",
        "revision": 54,
        "title": "Check the current application before the tutorial"
      },
      {
        "document": "blue",
        "subject": "blue",
        "revision": 55,
        "title": "Choose on-chain or LNDHub deliberately"
      },
      {
        "document": "blixt",
        "subject": "blixt",
        "revision": 56,
        "title": "Recover channels using Blixt’s documented process"
      },
      {
        "document": "zeus",
        "subject": "zeus",
        "revision": 57,
        "title": "This chapter is a remote-node example"
      },
      {
        "document": "calyxos",
        "subject": "calyxos",
        "revision": 58,
        "title": "Follow the maintained release for your device"
      },
      {
        "document": "sparrow",
        "subject": "sparrow",
        "revision": 59,
        "title": "Use the current verification flow"
      },
      {
        "document": "coldcard",
        "subject": "coldcard",
        "revision": 60,
        "title": "Match the security advisory to the seed history"
      },
      {
        "document": "sparrow",
        "subject": "sparrow",
        "revision": 60,
        "title": "Match the security advisory to the seed history"
      },
      {
        "document": "specter",
        "subject": "specter",
        "revision": 60,
        "title": "Match the security advisory to the seed history"
      },
      {
        "document": "verifysoftware",
        "subject": "verifysoftware",
        "revision": 61,
        "title": "Match every verification file to one release"
      },
      {
        "document": "bisq",
        "subject": "bisq",
        "revision": 62,
        "title": "This walkthrough covers the original exchange"
      },
      {
        "document": "peach",
        "subject": "peach",
        "revision": 63,
        "title": "Check current availability before onboarding"
      },
      {
        "document": "robosats",
        "subject": "robosats",
        "revision": 64,
        "title": "Use the selected coordinator’s current guide"
      },
      {
        "document": "sentinel",
        "subject": "sentinel",
        "revision": 65,
        "title": "Keep this import watch-only"
      },
      {
        "document": "stack-duo",
        "subject": "stack-duo",
        "revision": 66,
        "title": "Stack Duo is archived"
      },
      {
        "document": "wallet--compare",
        "subject": "wallet--compare",
        "revision": 67,
        "title": "Read this as a historical feature matrix"
      },
      {
        "document": "wallet",
        "subject": "wallet--compare",
        "revision": 67,
        "title": "Read this as a historical feature matrix"
      },
      {
        "document": "privacy--separate",
        "subject": "privacy--separate",
        "revision": 68,
        "title": "A technique is not a live service"
      },
      {
        "document": "privacy",
        "subject": "privacy--separate",
        "revision": 68,
        "title": "A technique is not a live service"
      },
      {
        "document": "privacy--get",
        "subject": "privacy--get",
        "revision": 69,
        "title": "AgoraDesk is no longer a trading option"
      },
      {
        "document": "privacy",
        "subject": "privacy--get",
        "revision": 69,
        "title": "AgoraDesk is no longer a trading option"
      },
      {
        "document": "privacy--secure",
        "subject": "privacy--secure",
        "revision": 70,
        "title": "Record the recovery format and wallet configuration"
      },
      {
        "document": "privacy",
        "subject": "privacy--secure",
        "revision": 70,
        "title": "Record the recovery format and wallet configuration"
      },
      {
        "document": "privacy--safeguard",
        "subject": "privacy--safeguard",
        "revision": 71,
        "title": "Recheck the hardware list"
      },
      {
        "document": "privacy",
        "subject": "privacy--safeguard",
        "revision": 71,
        "title": "Recheck the hardware list"
      },
      {
        "document": "qna--recommendations",
        "subject": "qna--recommendations",
        "revision": 72,
        "title": "Use the present tool directory for new installations"
      },
      {
        "document": "qna",
        "subject": "qna--recommendations",
        "revision": 72,
        "title": "Use the present tool directory for new installations"
      },
      {
        "document": "node--core",
        "subject": "node--core",
        "revision": 73,
        "title": "Pruning is not a fixed 10 GB installation"
      },
      {
        "document": "node",
        "subject": "node--core",
        "revision": 73,
        "title": "Pruning is not a fixed 10 GB installation"
      },
      {
        "document": "node--pap",
        "subject": "node--pap",
        "revision": 74,
        "title": "Historical prices and product configurations"
      },
      {
        "document": "node",
        "subject": "node--pap",
        "revision": 74,
        "title": "Historical prices and product configurations"
      },
      {
        "document": "node--pap",
        "subject": "node--pap",
        "revision": 75,
        "title": "Distinguish the old One from current myNode options"
      },
      {
        "document": "node",
        "subject": "node--pap",
        "revision": 75,
        "title": "Distinguish the old One from current myNode options"
      },
      {
        "document": "node--diy",
        "subject": "node--diy",
        "revision": 76,
        "title": "Match the image to today’s supported hardware"
      },
      {
        "document": "node",
        "subject": "node--diy",
        "revision": 76,
        "title": "Match the image to today’s supported hardware"
      },
      {
        "document": "node--diy",
        "subject": "node--diy",
        "revision": 77,
        "title": "Use the current board-specific instructions"
      },
      {
        "document": "node",
        "subject": "node--diy",
        "revision": 77,
        "title": "Use the current board-specific instructions"
      },
      {
        "document": "node--pap",
        "subject": "node--pap",
        "revision": 78,
        "title": "RaspiBlitz has a WebUI project"
      },
      {
        "document": "node",
        "subject": "node--pap",
        "revision": 78,
        "title": "RaspiBlitz has a WebUI project"
      },
      {
        "document": "node--diy",
        "subject": "node--diy",
        "revision": 79,
        "title": "Use the current RaspiBlitz interfaces"
      },
      {
        "document": "node",
        "subject": "node--diy",
        "revision": 79,
        "title": "Use the current RaspiBlitz interfaces"
      },
      {
        "document": "node--diy",
        "subject": "node--diy",
        "revision": 80,
        "title": "Umbrel is a broader home-server platform"
      },
      {
        "document": "node",
        "subject": "node--diy",
        "revision": 80,
        "title": "Umbrel is a broader home-server platform"
      },
      {
        "document": "node--pap",
        "subject": "node--pap",
        "revision": 81,
        "title": "Back up the services, then check the result"
      },
      {
        "document": "node",
        "subject": "node--pap",
        "revision": 81,
        "title": "Back up the services, then check the result"
      },
      {
        "document": "node--diy",
        "subject": "node--diy",
        "revision": 81,
        "title": "Back up the services, then check the result"
      },
      {
        "document": "node",
        "subject": "node--diy",
        "revision": 81,
        "title": "Back up the services, then check the result"
      },
      {
        "document": "node--compare",
        "subject": "node--compare",
        "revision": 82,
        "title": "Historical feature matrix"
      },
      {
        "document": "node",
        "subject": "node--compare",
        "revision": 82,
        "title": "Historical feature matrix"
      }
    ]
  }
}