{
  "date": "2026-11-12",
  "scope": "Primary-source review and targeted in-place corrections. Original passages, images and links retained. No physical-device or real-fund testing.",
  "pages": {
    "grapheneos": {
      "title": "A current route through installation.",
      "intro": "Use the official installer for your exact device. The original walkthrough remains useful context, but its screenshots are not the current installation interface.",
      "steps": [
        [
          "Check the device",
          "Confirm current support and the remaining support period in the device FAQ. Carrier restrictions can prevent bootloader unlocking."
        ],
        [
          "Prepare the migration",
          "Back up what you need before changing the operating system. Use a supported browser and the installer’s current host requirements."
        ],
        [
          "Install with the official flow",
          "The web installer guides bootloader unlocking, downloading and flashing the factory images. Follow its device-specific instructions."
        ],
        [
          "Finish the security setup",
          "Relock the bootloader and complete post-install verification. Then review app permissions, profiles and compatibility on the new system."
        ]
      ],
      "sources": [
        [
          "Official web installer",
          "https://grapheneos.org/install/web"
        ],
        [
          "Supported devices & FAQ",
          "https://grapheneos.org/faq"
        ]
      ],
      "changes": [
        [
          "Android Auto is supported",
          "The current GrapheneOS release provides an Android Auto integration with explicit permission controls. Wired and wireless modes require different access; follow the current setup instructions.",
          "https://grapheneos.org/usage#android-auto"
        ],
        [
          "Signal can hide your number from new contacts",
          "Usernames let someone initiate contact without you sharing your phone number. A number is still required to register, and existing contacts may already know it.",
          "https://signal.org/blog/phone-number-privacy-usernames/"
        ],
        [
          "SimpleX has desktop apps",
          "Current downloads include macOS, Windows and Linux. The original claim that no desktop client exists is outdated.",
          "https://simplex.chat/downloads/"
        ],
        [
          "Proton Drive has a Mac app",
          "Proton now offers a native macOS download as well as its web application. The Mac-only-through-a-browser limitation in the original article no longer applies.",
          "https://proton.me/drive/download"
        ],
        [
          "Skiff is no longer an available service",
          "Skiff reports that Mail, Pages, Calendar and Drive closed on 9 August 2024. Its original mention below is retained as history, not a current recommendation.",
          "https://skiff.com/data-migration"
        ]
      ]
    },
    "calyxos": {
      "title": "Check the release, not the old screenshot.",
      "intro": "CalyxOS resumed maintained releases in July 2026. The November news lists Android 17 security updates; older installation notes need to be read against the current device release.",
      "steps": [
        [
          "Match the exact model",
          "Use the project’s current device and installation guidance, including firmware and bootloader requirements."
        ],
        [
          "Check the release channel",
          "The November 10 announcement lists 8.0.5.20/21 security updates. A release announcement does not mean every model receives identical firmware."
        ],
        [
          "Review app compatibility",
          "CalyxOS includes microG-related integration. Check the apps you rely on and their current documented behaviour."
        ],
        [
          "Keep maintenance visible",
          "Review system updates and the new CalyxOS App Updater introduced in October. A private setup still needs regular security updates."
        ]
      ],
      "sources": [
        [
          "CalyxOS release news",
          "https://calyxos.org/news/"
        ],
        [
          "CalyxOS documentation",
          "https://calyxos.org/docs/"
        ]
      ]
    },
    "sparrow": {
      "title": "Verify what you install.",
      "intro": "Sparrow’s official download page lists version 2.5.6 at this review. Download verification has a built-in workflow in modern Sparrow releases.",
      "steps": [
        [
          "Get the complete set",
          "Obtain the installer, release manifest and detached signature from the official download page."
        ],
        [
          "Use the verification tool",
          "Sparrow 1.8.3 and later can verify a download through Tools → Verify Download. Keep the associated files together."
        ],
        [
          "Bootstrap trust carefully",
          "For a first installation, follow the GPG instructions and check the signing-key fingerprint through a trusted source. A hash alone does not establish the author."
        ],
        [
          "Check the result",
          "Read the verification result before opening an installer. A valid signature establishes signing-key provenance, not that software is free of bugs."
        ]
      ],
      "sources": [
        [
          "Sparrow download & verification",
          "https://sparrowwallet.com/download/"
        ]
      ]
    },
    "sparrow-2026": {
      "title": "Verify what you install.",
      "intro": "Sparrow’s official download page lists version 2.5.6 at this review. Download verification has a built-in workflow in modern Sparrow releases.",
      "steps": [
        [
          "Get the complete set",
          "Obtain the installer, release manifest and detached signature from the official download page."
        ],
        [
          "Use the verification tool",
          "Sparrow 1.8.3 and later can verify a download through Tools → Verify Download. Keep the associated files together."
        ],
        [
          "Bootstrap trust carefully",
          "For a first installation, follow the GPG instructions and check the signing-key fingerprint through a trusted source. A hash alone does not establish the author."
        ],
        [
          "Check the result",
          "Read the verification result before opening an installer. A valid signature establishes signing-key provenance, not that software is free of bugs."
        ]
      ],
      "sources": [
        [
          "Sparrow download & verification",
          "https://sparrowwallet.com/download/"
        ]
      ]
    },
    "verifysoftware": {
      "title": "Verify what you install.",
      "intro": "Sparrow’s official download page lists version 2.5.6 at this review. Download verification has a built-in workflow in modern Sparrow releases.",
      "steps": [
        [
          "Get the complete set",
          "Obtain the installer, release manifest and detached signature from the official download page."
        ],
        [
          "Use the verification tool",
          "Sparrow 1.8.3 and later can verify a download through Tools → Verify Download. Keep the associated files together."
        ],
        [
          "Bootstrap trust carefully",
          "For a first installation, follow the GPG instructions and check the signing-key fingerprint through a trusted source. A hash alone does not establish the author."
        ],
        [
          "Check the result",
          "Read the verification result before opening an installer. A valid signature establishes signing-key provenance, not that software is free of bugs."
        ]
      ],
      "sources": [
        [
          "Sparrow download & verification",
          "https://sparrowwallet.com/download/"
        ]
      ]
    },
    "verify-downloads-2026": {
      "title": "Verify what you install.",
      "intro": "Sparrow’s official download page lists version 2.5.6 at this review. Download verification has a built-in workflow in modern Sparrow releases.",
      "steps": [
        [
          "Get the complete set",
          "Obtain the installer, release manifest and detached signature from the official download page."
        ],
        [
          "Use the verification tool",
          "Sparrow 1.8.3 and later can verify a download through Tools → Verify Download. Keep the associated files together."
        ],
        [
          "Bootstrap trust carefully",
          "For a first installation, follow the GPG instructions and check the signing-key fingerprint through a trusted source. A hash alone does not establish the author."
        ],
        [
          "Check the result",
          "Read the verification result before opening an installer. A valid signature establishes signing-key provenance, not that software is free of bugs."
        ]
      ],
      "sources": [
        [
          "Sparrow download & verification",
          "https://sparrowwallet.com/download/"
        ]
      ]
    },
    "passport": {
      "title": "Start with the right Passport.",
      "intro": "The current Foundation documentation distinguishes Passport Core and Passport Prime. This original tutorial documents an earlier Passport workflow; keep model-specific instructions separate.",
      "steps": [
        [
          "Identify your model",
          "Use the Core documentation for Core. Prime has a separate setup section and should not be treated as a cosmetic update to the old device."
        ],
        [
          "Validate the device",
          "Follow Foundation’s supply-chain validation and current firmware instructions before creating a wallet."
        ],
        [
          "Understand the backup",
          "Core supports recovery words and encrypted microSD backups. Recovery requirements differ: an encrypted backup also needs its backup code."
        ],
        [
          "Connect and rehearse",
          "Use the current instructions for your chosen companion wallet. Verify receiving addresses on the signing device and test your recovery plan with care."
        ]
      ],
      "sources": [
        [
          "Passport Core setup",
          "https://docs.foundation.xyz/passport/setup/"
        ]
      ]
    },
    "passport-2026": {
      "title": "Start with the right Passport.",
      "intro": "The current Foundation documentation distinguishes Passport Core and Passport Prime. This original tutorial documents an earlier Passport workflow; keep model-specific instructions separate.",
      "steps": [
        [
          "Identify your model",
          "Use the Core documentation for Core. Prime has a separate setup section and should not be treated as a cosmetic update to the old device."
        ],
        [
          "Validate the device",
          "Follow Foundation’s supply-chain validation and current firmware instructions before creating a wallet."
        ],
        [
          "Understand the backup",
          "Core supports recovery words and encrypted microSD backups. Recovery requirements differ: an encrypted backup also needs its backup code."
        ],
        [
          "Connect and rehearse",
          "Use the current instructions for your chosen companion wallet. Verify receiving addresses on the signing device and test your recovery plan with care."
        ]
      ],
      "sources": [
        [
          "Passport Core setup",
          "https://docs.foundation.xyz/passport/setup/"
        ]
      ]
    },
    "blue": {
      "title": "On-chain and Lightning are separate choices.",
      "intro": "BlueWallet’s hosted Lndhub.io service closed in 2023. That change did not shut down ordinary on-chain wallets or privately operated LNDHub instances.",
      "steps": [
        [
          "Choose the wallet type",
          "Know whether you are creating an on-chain wallet, a watch-only wallet or a connection to an LNDHub server."
        ],
        [
          "Keep the backup method straight",
          "A watch-only export is not spending authority. An LNDHub account and an on-chain recovery phrase do not have the same recovery process."
        ],
        [
          "Use the current interface",
          "The original screens document an earlier release. Follow the current BlueWallet documentation for import, fee controls and hardware-wallet workflows."
        ],
        [
          "Understand the server",
          "For Lightning, the server operator and configuration determine the trust relationship. Do not reuse the discontinued hosted-service instructions."
        ]
      ],
      "sources": [
        [
          "BlueWallet documentation",
          "https://bluewallet.io/docs/"
        ],
        [
          "Hosted service retirement",
          "https://bluewallet.io/sunsetting-lndhub/"
        ]
      ]
    },
    "bluewallet-2026": {
      "title": "On-chain and Lightning are separate choices.",
      "intro": "BlueWallet’s hosted Lndhub.io service closed in 2023. That change did not shut down ordinary on-chain wallets or privately operated LNDHub instances.",
      "steps": [
        [
          "Choose the wallet type",
          "Know whether you are creating an on-chain wallet, a watch-only wallet or a connection to an LNDHub server."
        ],
        [
          "Keep the backup method straight",
          "A watch-only export is not spending authority. An LNDHub account and an on-chain recovery phrase do not have the same recovery process."
        ],
        [
          "Use the current interface",
          "The original screens document an earlier release. Follow the current BlueWallet documentation for import, fee controls and hardware-wallet workflows."
        ],
        [
          "Understand the server",
          "For Lightning, the server operator and configuration determine the trust relationship. Do not reuse the discontinued hosted-service instructions."
        ]
      ],
      "sources": [
        [
          "BlueWallet documentation",
          "https://bluewallet.io/docs/"
        ],
        [
          "Hosted service retirement",
          "https://bluewallet.io/sunsetting-lndhub/"
        ]
      ]
    },
    "coldcard": {
      "title": "Firmware fixes and seed recovery are different.",
      "intro": "The 2026 advisory concerns seed generation on affected firmware. Published fixes exist; updating a device does not repair an already affected seed.",
      "steps": [
        [
          "Identify model and track",
          "Standard and Edge use different version lines. Compare your device with the current official security-status matrix."
        ],
        [
          "Distinguish old and new seeds",
          "A securely generated external seed is not weakened just by importing it. A seed generated through an affected flow remains affected after cloning or restoring."
        ],
        [
          "Use the migration guidance",
          "The official guide covers preparation, one-device and two-device workflows, and special wallet types. Preserve working recovery material before changing anything."
        ],
        [
          "Verify the current release",
          "The status page currently recommends Mk4/Mk5 5.6.3 or Q 1.5.3Q on the standard track. Read its current requirements and exceptions rather than relying on this archived tutorial."
        ]
      ],
      "sources": [
        [
          "Current security status",
          "https://coldcard.com/security/status"
        ],
        [
          "Affected-seed migration",
          "https://coldcard.com/security/migrate"
        ]
      ]
    },
    "node": {
      "title": "Verify the chain on your own terms.",
      "intro": "Bitcoin Core’s download page lists 32.1 at this review. Choose the build for your platform and follow its signed-release verification instructions.",
      "steps": [
        [
          "Allow for the initial sync",
          "A new node must download and validate historical data. Budget disk, bandwidth and time before expecting a wallet connection to be ready."
        ],
        [
          "Understand pruning",
          "Pruning reduces retained block storage after validation. It does not remove the need to validate the chain."
        ],
        [
          "Keep your network boundary clear",
          "A wallet connection and public peer-to-peer service are different interfaces. Do not expose administrative RPC credentials or ports unnecessarily."
        ],
        [
          "Connect your wallet deliberately",
          "Sparrow can use Bitcoin Core or a private Electrum server. Check synchronization and the connection before using its balances or transaction history."
        ]
      ],
      "sources": [
        [
          "Bitcoin Core download",
          "https://bitcoincore.org/en/download/"
        ],
        [
          "Sparrow connection options",
          "https://sparrowwallet.com/"
        ]
      ]
    },
    "bitcoin-core-2026": {
      "title": "Verify the chain on your own terms.",
      "intro": "Bitcoin Core’s download page lists 32.1 at this review. Choose the build for your platform and follow its signed-release verification instructions.",
      "steps": [
        [
          "Allow for the initial sync",
          "A new node must download and validate historical data. Budget disk, bandwidth and time before expecting a wallet connection to be ready."
        ],
        [
          "Understand pruning",
          "Pruning reduces retained block storage after validation. It does not remove the need to validate the chain."
        ],
        [
          "Keep your network boundary clear",
          "A wallet connection and public peer-to-peer service are different interfaces. Do not expose administrative RPC credentials or ports unnecessarily."
        ],
        [
          "Connect your wallet deliberately",
          "Sparrow can use Bitcoin Core or a private Electrum server. Check synchronization and the connection before using its balances or transaction history."
        ]
      ],
      "sources": [
        [
          "Bitcoin Core download",
          "https://bitcoincore.org/en/download/"
        ],
        [
          "Sparrow connection options",
          "https://sparrowwallet.com/"
        ]
      ]
    },
    "zeus": {
      "title": "Choose your Lightning mode first.",
      "intro": "ZEUS supports mobile Bitcoin and Lightning use as well as remote management of LND and Core Lightning nodes. The responsibilities depend on how you configure it.",
      "steps": [
        [
          "A node on your phone",
          "An embedded-node workflow puts node operation and recovery responsibilities on the mobile setup."
        ],
        [
          "A remote connection",
          "A remote-node workflow controls a separately operated node. Secure its credentials and understand which permissions they grant."
        ],
        [
          "Plan for liquidity",
          "Sending and receiving depend on channels and available liquidity. A displayed balance is not the only condition for a payment to succeed."
        ],
        [
          "Read mode-specific recovery",
          "Use the current ZEUS documentation for the selected mode; do not assume an old remote-node tutorial describes an embedded wallet."
        ]
      ],
      "sources": [
        [
          "ZEUS official project",
          "https://github.com/ZeusLN/zeus"
        ],
        [
          "ZEUS documentation",
          "https://docs.zeusln.app/"
        ]
      ]
    },
    "blixt": {
      "title": "A Lightning client on your phone.",
      "intro": "Blixt describes its architecture as lnd with Neutrino running directly on the phone. That is a different arrangement from a custodial Lightning balance.",
      "steps": [
        [
          "Let the client synchronize",
          "The wallet needs to obtain the information required to follow the chain and manage its channels."
        ],
        [
          "Understand channel creation",
          "Funding on-chain can trigger channel opening; the project also documents its Dunder liquidity service. Check the selected workflow and costs."
        ],
        [
          "Keep the recovery plan current",
          "Use the project’s current backup guidance. Channel state and an ordinary on-chain wallet are not interchangeable recovery problems."
        ],
        [
          "Start with the official guide",
          "Use the original article to learn the concepts, then compare the current controls and supported platform instructions."
        ]
      ],
      "sources": [
        [
          "Blixt architecture & guides",
          "https://blixtwallet.github.io/"
        ]
      ]
    },
    "bisq": {
      "title": "Which Bisq are you using?",
      "intro": "The current project presents its original desktop exchange and Bisq Easy offerings. Treat them as different trading workflows.",
      "steps": [
        [
          "Identify the application",
          "Match the guide to the exact Bisq application and version before following deposit or offer instructions."
        ],
        [
          "Understand the trade model",
          "Read the security and dispute model for that application. Different versions can rely on different mechanisms."
        ],
        [
          "Check the payment method",
          "Understand timing, reversibility and information shared with a counterparty before agreeing to a trade."
        ],
        [
          "Verify the download",
          "Use the official release links and signature information. The archived screenshots are retained below for the original desktop workflow."
        ]
      ],
      "sources": [
        [
          "Bisq official downloads & documentation",
          "https://bisq.network/"
        ]
      ]
    },
    "peach": {
      "title": "A marketplace with changed availability.",
      "intro": "Peach now presents mobile and web trading. Its current site also includes jurisdiction-specific availability notices, so the original mobile tutorial is not the whole onboarding story.",
      "steps": [
        [
          "Check availability first",
          "Read the current service notice for your location before creating an account or starting a trade."
        ],
        [
          "Choose mobile or web",
          "The web interface can pair with the mobile app. Follow the current pairing instructions instead of guessing from the old screenshots."
        ],
        [
          "Review the offer",
          "Price, payment method, settlement timing and dispute handling matter as much as the headline exchange rate."
        ],
        [
          "Keep the trade in context",
          "Identity-free registration does not make a bank transfer anonymous to the bank or the other party."
        ]
      ],
      "sources": [
        [
          "Peach current service information",
          "https://peachbitcoin.com/"
        ]
      ]
    },
    "robosats": {
      "title": "Keep the trade token and the trade model clear.",
      "intro": "RoboSats uses Tor and Lightning-based bonds and escrow. The current guide is the source for trade timing, coordinator choice and wallet compatibility.",
      "steps": [
        [
          "Understand the token",
          "The robot token is how you return to the trade identity. Keep it private and available for the duration of the trade."
        ],
        [
          "Check Lightning capacity",
          "Bonds and payments require compatible invoice behaviour and sufficient sending or receiving liquidity."
        ],
        [
          "Follow the trade sequence",
          "Use the current coordinator instructions for confirming fiat payment and releasing bitcoin."
        ],
        [
          "Plan for a dispute",
          "Read the coordinator’s process before starting, including evidence requirements and time limits."
        ]
      ],
      "sources": [
        [
          "Official RoboSats learning site",
          "https://learn.robosats.org/"
        ]
      ]
    },
    "zap": {
      "title": "Keep this as a historical walkthrough.",
      "intro": "The official Zap Desktop repository says the application is no longer actively maintained. This tutorial is retained as part of the original collection, not presented as a current setup recommendation.",
      "steps": [
        [
          "Understand what it documents",
          "The article explains the old Zap Desktop interface and node-connection workflow."
        ],
        [
          "Choose maintained documentation",
          "For a new Lightning setup, compare the current ZEUS and Blixt documentation in the tool directory."
        ]
      ],
      "sources": [
        [
          "Zap Desktop project status",
          "https://github.com/LN-Zap/zap-desktop"
        ]
      ]
    },
    "sentinel": {
      "title": "Watch-only does not mean privacy-free.",
      "intro": "The original Sentinel repository describes a watch-only Android wallet and points to a separate code host. This review does not establish a current maintained release.",
      "steps": [
        [
          "Keep signing keys separate",
          "A watch-only wallet uses public wallet information. It should not need your recovery phrase or private keys."
        ],
        [
          "Treat extended public keys carefully",
          "An extended public key can reveal related addresses and activity. Consider who operates the server that receives wallet queries."
        ],
        [
          "Verify the software lineage",
          "Check the exact repository, release and maintainer before installing. Do not treat a similarly named fork as the same application."
        ],
        [
          "Compare current alternatives",
          "The tool directory includes wallets with watch-only capabilities. Compare recovery and connection behaviour before importing public wallet data."
        ]
      ],
      "sources": [
        [
          "Original Sentinel project",
          "https://github.com/Samourai-Wallet/sentinel-android"
        ],
        [
          "BlueWallet watch-only documentation",
          "https://bluewallet.io/docs/"
        ]
      ]
    },
    "stack-duo": {
      "title": "Stack Duo is archived.",
      "intro": "The original Stack Duo repository was archived on 24 September 2026 and is read-only. This illustrated tutorial is preserved as history, not a current installation recommendation.",
      "steps": [
        [
          "Confirm the app identity",
          "Check the name, publisher and repository behind the installer you are considering."
        ],
        [
          "Match backup and network",
          "Use the recovery format and coin/network specified by that application. Similar interfaces do not guarantee identical recovery settings."
        ],
        [
          "Review the current release",
          "Use the official repository and release notes for maintained code. This source review is not a hands-on validation of a current Duo build."
        ]
      ],
      "sources": [
        [
          "Stack Duo repository status",
          "https://github.com/cypherstack/stack_duo"
        ]
      ]
    },
    "seed": {
      "title": "Explore the mechanics with examples.",
      "intro": "The local Seed Tool retains its original calculation scripts and tools. This design pass changes presentation and navigation, not its cryptographic implementation.",
      "steps": [
        [
          "Start with the concept",
          "Use the guided learning tools to understand entropy, checksums and derivation before attempting advanced utilities."
        ],
        [
          "Know what leaves a boundary",
          "Public keys, descriptors and transaction data can disclose wallet information even when they cannot authorize a spend."
        ],
        [
          "Connect the standards",
          "The new BIP explorer explains BIP39 words, BIP32 derivation, account paths and descriptor structure."
        ],
        [
          "Keep learning separate from custody",
          "Use public test vectors or fictional examples for exploration. This local preview is not an independent security audit of the Seed Tool."
        ]
      ],
      "sources": [
        [
          "BIP39 specification",
          "https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki"
        ],
        [
          "BIP32 specification",
          "https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki"
        ]
      ]
    },
    "toolkit": {
      "title": "A clearer route through the collection.",
      "intro": "The original curated links remain below. New tool profiles and the BIP explorer add context to the choices without treating every historical link as a current recommendation.",
      "steps": [
        [
          "Choose by purpose",
          "The tool directory distinguishes wallets, nodes, privacy software, Lightning clients and peer-to-peer marketplaces."
        ],
        [
          "Read the trade-off",
          "Consider maintenance, server trust, recovery, device support and the responsibilities that move to you."
        ],
        [
          "Follow the standards",
          "Start with BIP39 and BIP32 for backups and key derivation; explore BIP174 and BIP380 for signing workflows and wallet descriptions."
        ],
        [
          "Keep the original trail",
          "All original links remain available in their articles and the searchable reference archive, including older or discontinued projects."
        ]
      ],
      "sources": [
        [
          "Official Bitcoin BIP repository",
          "https://github.com/bitcoin/bips"
        ],
        [
          "Bitcoin Core documentation",
          "https://bitcoincore.org/en/download/"
        ],
        [
          "Sparrow documentation",
          "https://sparrowwallet.com/"
        ]
      ],
      "changes": [
        [
          "Authentication app maintenance",
          "andOTP is explicitly unmaintained; review migration and account recovery before retiring an installation.",
          "https://github.com/andOTP/andOTP"
        ],
        [
          "Phone support lifetime",
          "Pixel 5 is end of life in GrapheneOS. An old hardware recommendation should not drive a new security-sensitive purchase.",
          "https://grapheneos.org/faq#supported-devices"
        ],
        [
          "Messaging encryption",
          "Telegram cloud chats and groups are not end-to-end encrypted. Secret Chats have a different, device-specific model.",
          "https://telegram.org/faq#q-how-are-secret-chats-different"
        ]
      ]
    },
    "intermediate": {
      "title": "A clearer route through the collection.",
      "intro": "The original curated links remain below. New tool profiles and the BIP explorer add context to the choices without treating every historical link as a current recommendation.",
      "steps": [
        [
          "Choose by purpose",
          "The tool directory distinguishes wallets, nodes, privacy software, Lightning clients and peer-to-peer marketplaces."
        ],
        [
          "Read the trade-off",
          "Consider maintenance, server trust, recovery, device support and the responsibilities that move to you."
        ],
        [
          "Follow the standards",
          "Start with BIP39 and BIP32 for backups and key derivation; explore BIP174 and BIP380 for signing workflows and wallet descriptions."
        ],
        [
          "Keep the original trail",
          "All original links remain available in their articles and the searchable reference archive, including older or discontinued projects."
        ]
      ],
      "sources": [
        [
          "Official Bitcoin BIP repository",
          "https://github.com/bitcoin/bips"
        ],
        [
          "Bitcoin Core documentation",
          "https://bitcoincore.org/en/download/"
        ],
        [
          "Sparrow documentation",
          "https://sparrowwallet.com/"
        ]
      ]
    },
    "advanced": {
      "title": "A clearer route through the collection.",
      "intro": "The original curated links remain below. New tool profiles and the BIP explorer add context to the choices without treating every historical link as a current recommendation.",
      "steps": [
        [
          "Choose by purpose",
          "The tool directory distinguishes wallets, nodes, privacy software, Lightning clients and peer-to-peer marketplaces."
        ],
        [
          "Read the trade-off",
          "Consider maintenance, server trust, recovery, device support and the responsibilities that move to you."
        ],
        [
          "Follow the standards",
          "Start with BIP39 and BIP32 for backups and key derivation; explore BIP174 and BIP380 for signing workflows and wallet descriptions."
        ],
        [
          "Keep the original trail",
          "All original links remain available in their articles and the searchable reference archive, including older or discontinued projects."
        ]
      ],
      "sources": [
        [
          "Official Bitcoin BIP repository",
          "https://github.com/bitcoin/bips"
        ],
        [
          "Bitcoin Core documentation",
          "https://bitcoincore.org/en/download/"
        ],
        [
          "Sparrow documentation",
          "https://sparrowwallet.com/"
        ]
      ]
    },
    "verify": {
      "title": "Count the right thing.",
      "intro": "A practical audit distinguishes scheduled issuance from unspent outputs. The old block-height example remains in the article, with the current interpretation beside it.",
      "steps": [
        [
          "Synchronize first",
          "Wait for initial validation to complete and confirm the network and tip you are inspecting."
        ],
        [
          "Ask your own node",
          "Run bitcoin-cli gettxoutsetinfo, or gettxoutsetinfo in the Core console. This is a read-only query."
        ],
        [
          "Record the context",
          "Keep height, bestblock and total_amount together. Check help gettxoutsetinfo for your installed version before using optional parameters."
        ],
        [
          "Compare carefully",
          "Lost keys are not identifiable from this total. The theoretical subsidy, issued rewards and UTXO value answer different questions."
        ]
      ],
      "sources": [
        [
          "Bitcoin Core RPC reference (v30; check installed help)",
          "https://bitcoincore.org/en/doc/30.0.0/rpc/blockchain/gettxoutsetinfo/"
        ],
        [
          "Bitcoin Core subsidy calculation",
          "https://github.com/bitcoin/bitcoin/blob/v32.1/src/validation.cpp"
        ]
      ]
    },
    "mynode": {
      "title": "Build for the current image.",
      "intro": "The old myNode One walkthrough remains illustrated below. Current downloads and storage guidance differ from that hardware list.",
      "steps": [
        [
          "Choose the platform",
          "Select the matching Model Two, Pi 4/5, PC or VM image, rather than adapting an old board image."
        ],
        [
          "Verify and flash",
          "Follow myNode’s image-signature instructions and check the target disk before writing it."
        ],
        [
          "Allow room to grow",
          "The current download guide recommends a 2 TB SSD. Extra services and indexes use additional space."
        ],
        [
          "Bring up services deliberately",
          "Finish synchronization before pairing wallets. Enable only the services you intend to maintain; the old Whirlpool listing is historical."
        ]
      ],
      "sources": [
        [
          "myNode current images and requirements",
          "https://mynodebtc.com/download"
        ]
      ]
    },
    "ronindojo": {
      "title": "Connect a wallet to a maintained backend.",
      "intro": "The original screenshots document an earlier RoninDojo release. Use the present hardware and installation documentation as the starting point.",
      "steps": [
        [
          "Match the hardware",
          "Check the project’s board-specific or x86 instructions. The current site lists Rock5b+, Pi 5 and x86 support."
        ],
        [
          "Install the matching image",
          "Verify the OS image and follow the documented storage and power requirements."
        ],
        [
          "Wait for synchronization",
          "A running dashboard does not by itself prove the chain and wallet indexes are ready."
        ],
        [
          "Pair using current instructions",
          "Follow the selected wallet’s connection guide. Keep RPC and administration credentials private."
        ]
      ],
      "sources": [
        [
          "RoninDojo project and supported hardware",
          "https://ronindojo.io/"
        ],
        [
          "RoninDojo installation",
          "https://docs.ronindojo.io/install/manual/"
        ],
        [
          "Connect Sparrow to RoninDojo",
          "https://docs.ronindojo.io/guides-wallet/sparrow/"
        ]
      ]
    },
    "dojo": {
      "title": "Recover visibility without losing the backup.",
      "intro": "These articles document old Samourai and Dojo interfaces. Their useful underlying distinction is between recovery keys, account metadata and the backend’s transaction index.",
      "steps": [
        [
          "Inventory first",
          "Retain the seed, passphrase if used, encrypted backups and known account information before resetting anything."
        ],
        [
          "Check the account",
          "Deposit, premix and postmix accounts can use different paths. An empty account is not proof of an empty wallet."
        ],
        [
          "Check the backend",
          "Verify synchronization and the wallet’s public account data before changing scan ranges."
        ],
        [
          "Use the current connection guide",
          "RoninDojo documents current wallet connections; the original Whirlpool GUI connection is not a current Sparrow feature."
        ]
      ],
      "sources": [
        [
          "Connect Sparrow to RoninDojo",
          "https://docs.ronindojo.io/guides-wallet/sparrow/"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ],
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ]
      ]
    },
    "rdmigrate": {
      "title": "Recover visibility without losing the backup.",
      "intro": "These articles document old Samourai and Dojo interfaces. Their useful underlying distinction is between recovery keys, account metadata and the backend’s transaction index.",
      "steps": [
        [
          "Inventory first",
          "Retain the seed, passphrase if used, encrypted backups and known account information before resetting anything."
        ],
        [
          "Check the account",
          "Deposit, premix and postmix accounts can use different paths. An empty account is not proof of an empty wallet."
        ],
        [
          "Check the backend",
          "Verify synchronization and the wallet’s public account data before changing scan ranges."
        ],
        [
          "Use the current connection guide",
          "RoninDojo documents current wallet connections; the original Whirlpool GUI connection is not a current Sparrow feature."
        ]
      ],
      "sources": [
        [
          "Connect Sparrow to RoninDojo",
          "https://docs.ronindojo.io/guides-wallet/sparrow/"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ],
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ]
      ]
    },
    "samourai": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "whirlpool": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "mobilecoinjoin": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "wpfees": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "doxxic": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "csimplications": {
      "title": "Read this as a historical workflow.",
      "intro": "The original Samourai/Whirlpool setup, coordinator pricing and remix instructions are preserved. They are not a current service recommendation; Sparrow removed its Whirlpool client in 2024.",
      "steps": [
        [
          "Separate the concept from the service",
          "Coinjoin is a transaction technique. A particular coordinator, mobile app or pool can cease operating without changing Bitcoin’s consensus rules."
        ],
        [
          "Preserve recovery information",
          "For an existing wallet, identify the backup format, passphrase and account paths before attempting recovery or deleting software."
        ],
        [
          "Keep output history useful",
          "Retain labels and inspect which inputs a transaction combines. Mixing does not erase records already held by an exchange or counterparty."
        ],
        [
          "Evaluate a replacement independently",
          "Check its actual operators, implementation, fees, recovery and current documentation. Similar branding is not evidence of equivalent security."
        ]
      ],
      "sources": [
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ],
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ]
      ]
    },
    "agora": {
      "title": "AgoraDesk is closed.",
      "intro": "The project’s own site confirms the platform wound down in 2024 and is offline. This article is retained as an illustrated record of the service.",
      "steps": [
        [
          "Do not begin the old signup flow",
          "The buying, selling and advertisement screens below no longer describe an available AgoraDesk service."
        ],
        [
          "Choose another trade model deliberately",
          "Compare current Bisq, Hodl Hodl, Peach or RoboSats documentation. They have different custody, settlement and dispute arrangements."
        ]
      ],
      "sources": [
        [
          "AgoraDesk closure notice",
          "https://agoradesk.com/"
        ],
        [
          "Bisq applications and documentation",
          "https://bisq.network/"
        ],
        [
          "Hodl Hodl trading FAQ",
          "https://hodlhodl.com/pages/faq"
        ],
        [
          "Peach service information",
          "https://peachbitcoin.com/"
        ],
        [
          "RoboSats guides",
          "https://learn.robosats.org/"
        ]
      ]
    },
    "azteco": {
      "title": "Start with the voucher type.",
      "intro": "The original Envoy walkthrough is retained. Current redemption distinguishes an on-chain voucher code from a Lightning QR voucher.",
      "steps": [
        [
          "Check the seller and expiry",
          "Read the voucher’s terms and redemption deadline before buying. Retailer and payment-method records vary."
        ],
        [
          "Match the network",
          "Use a Bitcoin receiving address for the on-chain flow and the supported wallet flow for a Lightning voucher."
        ],
        [
          "Inspect the final quote",
          "Review the bitcoin amount after commission, payment and network fees. Do not infer today’s fees from the screenshots."
        ],
        [
          "Confirm receipt",
          "Check the destination and wallet result. Keep the voucher private until redemption is complete."
        ]
      ],
      "sources": [
        [
          "Azteco voucher redemption",
          "https://azte.co/redeem"
        ]
      ]
    },
    "hodlhodl": {
      "title": "Trade from the contract, not the screenshot.",
      "intro": "Hodl Hodl’s current fee schedule and escrow instructions are the source for a new trade.",
      "steps": [
        [
          "Set the offer clearly",
          "Specify price, limits, payment method and timing. Compare fixed and indexed prices."
        ],
        [
          "Check escrow first",
          "Follow the required funding and confirmation sequence before making the fiat payment."
        ],
        [
          "Read both fee layers",
          "The FAQ lists up to 0.75% per party before qualifying discounts; network fees are separate."
        ],
        [
          "Keep the evidence",
          "Use the contract’s communication and dispute process. Bank transfers can disclose identity even without exchange KYC."
        ]
      ],
      "sources": [
        [
          "Hodl Hodl trading FAQ",
          "https://hodlhodl.com/pages/faq"
        ]
      ]
    },
    "hodlhodloffer": {
      "title": "Trade from the contract, not the screenshot.",
      "intro": "Hodl Hodl’s current fee schedule and escrow instructions are the source for a new trade.",
      "steps": [
        [
          "Set the offer clearly",
          "Specify price, limits, payment method and timing. Compare fixed and indexed prices."
        ],
        [
          "Check escrow first",
          "Follow the required funding and confirmation sequence before making the fiat payment."
        ],
        [
          "Read both fee layers",
          "The FAQ lists up to 0.75% per party before qualifying discounts; network fees are separate."
        ],
        [
          "Keep the evidence",
          "Use the contract’s communication and dispute process. Bank transfers can disclose identity even without exchange KYC."
        ]
      ],
      "sources": [
        [
          "Hodl Hodl trading FAQ",
          "https://hodlhodl.com/pages/faq"
        ]
      ]
    },
    "opendime": {
      "title": "A bearer instrument has bearer risks.",
      "intro": "OPENDIME changes who physically holds the signing secret without creating a transaction at every handoff. That does not make the funding history disappear.",
      "steps": [
        [
          "Verify before accepting",
          "Check the sealed state and confirmed funds using the official process."
        ],
        [
          "Protect the physical device",
          "Plan for loss, damage and theft; this is not an ordinary seed-backed hardware wallet."
        ],
        [
          "Unseal only when ready",
          "Revealing the private key changes the trust model permanently."
        ],
        [
          "Sweep after unsealing",
          "Move the funds into your own wallet rather than treating an exposed key as a fresh sealed instrument."
        ]
      ],
      "sources": [
        [
          "OPENDIME product and instructions",
          "https://opendime.com/"
        ]
      ]
    },
    "paynym": {
      "title": "A payment code is not an address.",
      "intro": "The BIP47 protocol and the PayNym discovery layer are separate. The old Samourai screens remain useful historical illustrations.",
      "steps": [
        [
          "Identify the format",
          "A reusable payment code lets compatible wallets derive payment addresses. It is not an on-chain receiving address or a Lightning Address."
        ],
        [
          "Check both wallets",
          "Look for explicit BIP47 support and the required connection or notification flow."
        ],
        [
          "Understand the privacy boundary",
          "Publishing a code does not remove all transaction metadata or information known to the other party."
        ]
      ],
      "sources": [
        [
          "BIP47 specification",
          "https://github.com/bitcoin/bips/blob/master/bip-0047.mediawiki"
        ],
        [
          "BlueWallet documentation",
          "https://bluewallet.io/docs/"
        ]
      ]
    },
    "lostbitcoin": {
      "title": "Make recovery boring and repeatable.",
      "intro": "Several original statements were too absolute. The corrections below distinguish mnemonic words, passphrases, wallet configuration and the limits of risk reduction.",
      "steps": [
        [
          "List the required pieces",
          "Record the backup format, wallet type, network and any passphrase or multisig configuration."
        ],
        [
          "Test without exposing the secret",
          "Use the device’s documented backup verification or a separate practice wallet. Never paste a real seed into a support chat or this website."
        ],
        [
          "Preserve independence",
          "Avoid a single incident destroying both the working wallet and every backup. More copies also create more places that need protection."
        ],
        [
          "Prepare the handoff",
          "Keep understandable recovery instructions and review them when hardware or software changes."
        ]
      ],
      "sources": [
        [
          "Foundation recovery checklist",
          "https://docs.foundation.xyz/backups/recovery/"
        ],
        [
          "BIP39 specification",
          "https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki"
        ]
      ]
    },
    "specter": {
      "title": "Keep the coordinator and signing keys distinct.",
      "intro": "Specter coordinates Bitcoin Core and signing devices. The original device screenshots and author’s advisory remain, with links to current security and recovery guidance.",
      "steps": [
        [
          "Verify the release",
          "Use the official project and its release-verification instructions."
        ],
        [
          "Connect Core privately",
          "Configure the documented local or remote connection; keep administration off the public internet."
        ],
        [
          "Export wallet configuration",
          "Retain the supported wallet export as well as the required independent signing-key backups."
        ],
        [
          "Check device history",
          "For COLDCARD examples, consult the model/firmware advisory and migration guide. Updating firmware does not repair a seed generated by an affected flow."
        ]
      ],
      "sources": [
        [
          "Specter backup and recovery FAQ",
          "https://docs.specter.solutions/desktop/faq/"
        ],
        [
          "COLDCARD security status",
          "https://coldcard.com/security/status"
        ],
        [
          "COLDCARD migration guidance",
          "https://coldcard.com/security/migrate"
        ]
      ]
    },
    "wallet": {
      "title": "Choose the responsibilities you can maintain.",
      "intro": "The comparison tables preserve a snapshot of older products. Use the updated directory and the corrections in each chapter for present-day choices.",
      "steps": [
        [
          "On-chain custody",
          "Distinguish a wallet holding private keys from a watch-only view and a custodial account."
        ],
        [
          "Hardware signing",
          "Check the exact model, firmware, supported coordinator and recovery format."
        ],
        [
          "Lightning operation",
          "A custodial balance, embedded node and remote-node controller need different backup and liquidity plans."
        ],
        [
          "Maintenance",
          "Check release activity and current documentation. The old Zap and hosted BlueWallet Lightning listings are historical."
        ]
      ],
      "sources": [
        [
          "BlueWallet documentation",
          "https://bluewallet.io/docs/"
        ],
        [
          "Zap Desktop maintenance status",
          "https://github.com/LN-Zap/zap-desktop"
        ],
        [
          "ZEUS documentation",
          "https://docs.zeusln.app/"
        ]
      ]
    },
    "multisig": {
      "title": "Back up the policy, not just the words.",
      "intro": "The original complete walkthrough remains, including all signer screenshots. Current notes address backup completeness, device support and recovery rehearsal.",
      "steps": [
        [
          "Choose the threshold",
          "Decide which failure the extra keys are meant to survive. Keep independent signing keys independent."
        ],
        [
          "Preserve the configuration",
          "Store the threshold, script type, cosigner public keys and derivation information in a supported export."
        ],
        [
          "Verify receiving addresses",
          "Compare the coordinator’s address with the registered wallet on the signing devices."
        ],
        [
          "Rehearse recovery",
          "Reconstruct a practice wallet and verify its addresses before attempting a threshold signing test."
        ]
      ],
      "sources": [
        [
          "Specter multisig guide",
          "https://docs.specter.solutions/desktop/multisig-guide/"
        ],
        [
          "Specter backup and recovery FAQ",
          "https://docs.specter.solutions/desktop/faq/"
        ],
        [
          "BIP380: output descriptors",
          "https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki"
        ]
      ]
    },
    "privacytips": {
      "title": "Privacy depends on the whole workflow.",
      "intro": "The original explanations remain. Read them with the current distinctions between network metadata, transaction links and information already held by other people.",
      "steps": [
        [
          "Keep histories separate",
          "Label receipts and inspect input selection; combining inputs can reveal a relationship."
        ],
        [
          "Choose the network path",
          "A private node, HTTPS, Tor and a VPN solve different parts of the problem."
        ],
        [
          "Understand the trade",
          "A platform without identity collection can still involve a bank or a counterparty who knows you."
        ],
        [
          "Treat old services as history",
          "AgoraDesk is closed and the old Whirlpool workflows are not current setup instructions. Neither a sale nor a mix deletes an existing KYC record."
        ]
      ],
      "sources": [
        [
          "Tor and HTTPS: what observers see",
          "https://support.torproject.org/about-tor/security/https-encryption-and-tor/"
        ],
        [
          "AgoraDesk closure notice",
          "https://agoradesk.com/"
        ],
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ]
      ]
    },
    "privacy": {
      "title": "Privacy depends on the whole workflow.",
      "intro": "The original explanations remain. Read them with the current distinctions between network metadata, transaction links and information already held by other people.",
      "steps": [
        [
          "Keep histories separate",
          "Label receipts and inspect input selection; combining inputs can reveal a relationship."
        ],
        [
          "Choose the network path",
          "A private node, HTTPS, Tor and a VPN solve different parts of the problem."
        ],
        [
          "Understand the trade",
          "A platform without identity collection can still involve a bank or a counterparty who knows you."
        ],
        [
          "Treat old services as history",
          "AgoraDesk is closed and the old Whirlpool workflows are not current setup instructions. Neither a sale nor a mix deletes an existing KYC record."
        ]
      ],
      "sources": [
        [
          "Tor and HTTPS: what observers see",
          "https://support.torproject.org/about-tor/security/https-encryption-and-tor/"
        ],
        [
          "AgoraDesk closure notice",
          "https://agoradesk.com/"
        ],
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ]
      ]
    },
    "nokyconly": {
      "title": "Privacy depends on the whole workflow.",
      "intro": "The original explanations remain. Read them with the current distinctions between network metadata, transaction links and information already held by other people.",
      "steps": [
        [
          "Keep histories separate",
          "Label receipts and inspect input selection; combining inputs can reveal a relationship."
        ],
        [
          "Choose the network path",
          "A private node, HTTPS, Tor and a VPN solve different parts of the problem."
        ],
        [
          "Understand the trade",
          "A platform without identity collection can still involve a bank or a counterparty who knows you."
        ],
        [
          "Treat old services as history",
          "AgoraDesk is closed and the old Whirlpool workflows are not current setup instructions. Neither a sale nor a mix deletes an existing KYC record."
        ]
      ],
      "sources": [
        [
          "Tor and HTTPS: what observers see",
          "https://support.torproject.org/about-tor/security/https-encryption-and-tor/"
        ],
        [
          "AgoraDesk closure notice",
          "https://agoradesk.com/"
        ],
        [
          "Sparrow 1.9.0 release: Whirlpool removal",
          "https://github.com/sparrowwallet/sparrow/releases/tag/1.9.0"
        ]
      ]
    },
    "lightning": {
      "title": "Choose a recovery model before a wallet.",
      "intro": "The channel concepts remain useful, but current mobile wallets and node controllers have different operational responsibilities.",
      "steps": [
        [
          "Identify who operates the node",
          "Distinguish a custodial service, an embedded client and a remote controller."
        ],
        [
          "Plan both directions",
          "Sending balance and receiving liquidity are different constraints. Channel changes and swaps can incur on-chain fees."
        ],
        [
          "Follow implementation-specific backup guidance",
          "A seed, static channel backup and live channel state are not interchangeable. Use your wallet’s documented recovery path."
        ],
        [
          "Keep a way to exit",
          "Understand cooperative and force-close behaviour and the need for chain access before relying on a setup."
        ]
      ],
      "sources": [
        [
          "ZEUS documentation",
          "https://docs.zeusln.app/"
        ],
        [
          "Blixt documentation",
          "https://blixtwallet.github.io/"
        ]
      ]
    },
    "qna": {
      "title": "The fundamentals, with the old numbers corrected.",
      "intro": "The Q&A keeps its original questions and answers. Corrections in the relevant answers update the subsidy era and qualify claims about supply and censorship.",
      "steps": [
        [
          "Follow block height",
          "Subsidy changes are defined by block intervals, not a publication year."
        ],
        [
          "Separate roles",
          "Miners choose transactions for candidate blocks; validating nodes check the rules."
        ],
        [
          "Read recommendations in context",
          "Old wallet and service lists are historical snapshots. Use current official documentation before installing or trading."
        ]
      ],
      "sources": [
        [
          "Bitcoin Core subsidy calculation",
          "https://github.com/bitcoin/bitcoin/blob/v32.1/src/validation.cpp"
        ],
        [
          "Bitcoin Core downloads",
          "https://bitcoincore.org/en/download/"
        ]
      ]
    },
    "fork": {
      "title": "A contribution should be reproducible.",
      "intro": "The original GitHub and Jekyll walkthrough remains. Use the actual repository’s present toolchain and contribution instructions when applying it.",
      "steps": [
        [
          "Make your own working copy",
          "Fork and clone the intended repository; inspect its README and contribution guide."
        ],
        [
          "Change one branch",
          "Use a feature branch with a clear purpose and keep unrelated changes out."
        ],
        [
          "Validate locally",
          "Install the declared dependencies and run the documented build or checks."
        ],
        [
          "Propose and update",
          "Push your branch, open a pull request with the problem and validation, then incorporate review feedback."
        ]
      ],
      "sources": [
        [
          "GitHub contribution workflow",
          "https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project"
        ]
      ]
    },
    "staging1234": {
      "title": "A current route through installation.",
      "intro": "Use the official installer for your exact device. The original walkthrough remains useful context, but its screenshots are not the current installation interface.",
      "steps": [
        [
          "Check the device",
          "Confirm current support and the remaining support period in the device FAQ. Carrier restrictions can prevent bootloader unlocking."
        ],
        [
          "Prepare the migration",
          "Back up what you need before changing the operating system. Use a supported browser and the installer’s current host requirements."
        ],
        [
          "Install with the official flow",
          "The web installer guides bootloader unlocking, downloading and flashing the factory images. Follow its device-specific instructions."
        ],
        [
          "Finish the security setup",
          "Relock the bootloader and complete post-install verification. Then review app permissions, profiles and compatibility on the new system."
        ]
      ],
      "sources": [
        [
          "Official web installer",
          "https://grapheneos.org/install/web"
        ],
        [
          "Supported devices & FAQ",
          "https://grapheneos.org/faq"
        ]
      ],
      "changes": [
        [
          "Android Auto is supported",
          "The current GrapheneOS release provides an Android Auto integration with explicit permission controls. Wired and wireless modes require different access; follow the current setup instructions.",
          "https://grapheneos.org/usage#android-auto"
        ],
        [
          "Signal can hide your number from new contacts",
          "Usernames let someone initiate contact without you sharing your phone number. A number is still required to register, and existing contacts may already know it.",
          "https://signal.org/blog/phone-number-privacy-usernames/"
        ],
        [
          "SimpleX has desktop apps",
          "Current downloads include macOS, Windows and Linux. The original claim that no desktop client exists is outdated.",
          "https://simplex.chat/downloads/"
        ],
        [
          "Proton Drive has a Mac app",
          "Proton now offers a native macOS download as well as its web application. The Mac-only-through-a-browser limitation in the original article no longer applies.",
          "https://proton.me/drive/download"
        ],
        [
          "Skiff is no longer an available service",
          "Skiff reports that Mail, Pages, Calendar and Drive closed on 9 August 2024. Its original mention below is retained as history, not a current recommendation.",
          "https://skiff.com/data-migration"
        ]
      ]
    }
  }
}