Introduction
Bitcoin transactions are public. Privacy means limiting what particular people and services can learn about you: an exchange, a payment recipient, a wallet server or someone inspecting the blockchain. These observers see different information, so no single tool solves every problem.
Start with fresh receiving addresses, useful labels and a clear backup plan. Add more complex tools only when you understand what they protect. This guide explains the principles; the original Samourai and Whirlpool walkthroughs are historical, not instructions for starting a new wallet today.
Sourcing your bitcoin
An identity-verifying exchange can associate your purchases and withdrawals with your account. Buying without an identity check may reduce one source of records, but a bank transfer, trading partner, delivery address or reused username can still identify you. “No KYC” does not mean anonymous.
For a peer-to-peer trade, check the platform’s current escrow, dispute and payment rules before committing. Allow for premiums, limited liquidity and counterparty risk. Keep records and comply with the rules that apply to you. Do not treat old platform lists or screenshots as evidence that a service still operates.
Securing your bitcoin
Self-custody gives you control of spending keys; it does not hide transactions. Choose a wallet with a recovery process you understand. Obtain software from its official source, verify releases where supported and practise recovery before relying on a backup.
Protect the recovery words and any wallet separately from everyday device access. A PIN or app password is not necessarily a recovery passphrase. Keep labels and wallet configuration backed up too: recovery words alone do not recreate all of that information. The old Samourai Android setup is no longer an onboarding path for its original service.
Keeping activities separate
A wallet balance consists of individual unspent transaction outputs, or UTXOs. Spending several together creates a visible connection between them. For example, combining two 0.5 BTC outputs to pay 0.6 BTC reveals that both inputs participated in the same payment; the remainder becomes change, less the fee.
Use a fresh address for each receipt and label its source. Coin control lets you choose which outputs to spend. Before signing, inspect the selected inputs, payment, change and fee. Keep unrelated activities separate where that matters to you, and protect your labels: they can reveal information that is not public on the blockchain.
Checking your wallet connection
A wallet server may learn the addresses or scripts your wallet asks about. The exact exposure depends on the wallet and its connection method. Tor can help conceal your IP address from the server; it does not conceal the wallet data you send to that server.
Connecting a compatible wallet to your own synced Bitcoin Core node or private Electrum server reduces reliance on a third party for wallet queries. Check that the wallet actually uses that connection. Changing servers does not require moving coins, and cannot erase information already disclosed. A node also needs updates, storage and a secure remote-access setup.
Understanding CoinJoin
CoinJoin combines inputs from multiple participants in one transaction. Equal-output designs make some input-to-output assignments ambiguous, but the transaction remains public. Amounts, timing, counterparties and later spending can narrow that ambiguity. There is no universal number of rounds that guarantees anonymity.
The original Samourai infrastructure was seized in April 2024, and Sparrow removed Whirlpool and Soroban-related features in release 1.9.0. The RoninDojo diagram here explains an earlier stack. A separate implementation or fork needs its own review of custody, coordination, fees, wallet support and recovery; this guide does not certify one.
A map of the original ecosystem. Whirlpool and Soroban integrations shown here are historical. Component roles do not imply that the old services are available.
Reference ↗Safeguarding your bitcoin
A hardware signer can keep spending keys off your everyday computer. It does not hide your addresses from the software or server managing the wallet. Verify the destination and amount on the signer, and keep the recovery material needed for that specific wallet arrangement.
Moving funds to a new wallet creates an on-chain transaction, not a clean privacy slate. Consolidating outputs can join histories you meant to separate. Plan the destination, input selection and backup first; do not follow old menu paths or node installation commands without checking current documentation.
Spending with care
The recipient knows what you paid them and may also know your name, account or delivery address. Inspect change and avoid casually combining identifiable change with outputs whose history you want to keep separate. A lower transaction fee is not the only consideration when consolidating coins.
Collaborative payments such as Payjoin can challenge the assumption that every input belongs to the sender. They require compatible implementations and still reveal information to the parties involved. The older STONEWALL X2, Stowaway and Ricochet examples describe particular Samourai workflows; their names are not promises of anonymity or present availability.
Supporting habits
Tor protects aspects of network privacy when the application is correctly configured to use it. HTTPS protects the connection to a website. Neither hides information you deliberately give that website. A VPN changes who can observe parts of your network traffic; it does not remove the need to trust an operator.
Use a password manager, protect accounts and devices, and avoid unnecessarily linking the same public identity across activities. Start with the protections you can maintain consistently. Review wallet features and service availability before following any software-specific guide.
