- Chaumian CoinJoin (used by some clients) uses blind signatures to reduce what a coordinator can link.
- PSBT (Partially Signed Bitcoin Transaction) workflows let an external coordinator construct unsigned or partially signed transactions that hardware wallets can sign offline.
Standards referenced: BIP-174 (PSBT) — https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki
Tools: Wasabi, Sparrow and desktop coinjoin clients
Two desktop options commonly used with hardware wallets are Wasabi (a dedicated CoinJoin client) and Sparrow (a power-user wallet that supports privacy workflows via PSBT/third-party backends). Each has pros and cons depending on how hands-on you want to be.
Wasabi — quick practical notes
- Purpose: wallet + coordinated CoinJoin rounds with a coordinator using blind signatures.
- Privacy model: coordinator-assisted Chaumian CoinJoin; coordinator cannot trivially map inputs to outputs because of blind signatures (details in Wasabi docs).
- Hardware wallet use: works via PSBT signing flows (you prepare and sign on your hardware wallet).
Docs and reference: Wasabi documentation — https://docs.wasabiwallet.io/
Pros / Cons (short):
| Feature |
Strength |
Caveat |
| Built-in CoinJoin |
Strong user experience for mixing |
Requires waiting for rounds and coin availability |
| Coordinator privacy model |
Blind signatures reduce metadata leaks |
Coordinator still sees some network metadata |
| Hardware wallet signing |
PSBT-compatible; retains private keys on-device |
Requires careful PSBT handling (air-gapped recommended) |
Who might prefer this: users wanting a relatively guided CoinJoin workflow with clear privacy metrics. Who should look elsewhere: users who need fully air-gapped or multisig-first workflows only.
Sparrow — quick practical notes
- Purpose: advanced desktop wallet for power users, strong coin control, PSBT workflows and scripting support.
- Privacy model: excellent coin control; can be used with coinjoin backends (e.g., JoinMarket) or manual PSBT coordination.
- Hardware wallet use: strong PSBT integration, good for multisig setups.
Docs and reference: Sparrow docs — https://sparrowwallet.com/docs/
Pros / Cons (short):
| Feature |
Strength |
Caveat |
| Coin control |
Very granular selection and labeling |
More manual; steeper learning curve |
| Multisig & PSBT |
Friendly for multisig and air-gapped signing |
CoinJoin coordination is more manual |
Who might prefer this: advanced users who want control and multisig. Who should look elsewhere: beginners who want a guided mixing flow.
(And yes, you can use other desktop clients too — pick what you understand.)
How to run a CoinJoin with a hardware wallet — Step by step
This is a generic PSBT-based workflow. Adjust to your chosen desktop client.
- Prepare a fresh receiving address on your hardware wallet account. Use an account dedicated for coinjoin outputs if possible.
- Move funds you intend to mix to one or several UTXOs (avoid tiny dust). Coin denomination norms vary by client; follow the client's guidance.
- Start a CoinJoin round in the desktop client. Let the client build the unsigned transaction(s). This may take time.
- Export the PSBT. For security, prefer an air-gapped signing flow: export the PSBT to an offline machine or USB drive and sign there (see /air-gapped).
- Sign the PSBT on your hardware wallet and import the signed PSBT back into the desktop client.
- Broadcast the final transaction.
Why PSBT matters: PSBT keeps private keys on-device while letting external software construct complex transactions. See BIP-174.
Practical tip: in my testing, rounds sometimes wait hours. Expect delays. But the resulting anonymity set is much better when rounds have many participants.
Sweeping a paper wallet into your hardware wallet (how to)
Sweeping means spending the paper wallet's private key and sending the balance to an address you control (your hardware wallet). Importing a private key into a hot wallet carries risk; sweeping is safer because the paper's private key is used once to send funds to a hardened address.
Step-by-step (safe approach):
- Create a new receiving address on your hardware wallet.
- On an offline or well-audited machine, construct a sweep transaction that spends the paper wallet private key to the device address. Many desktop wallets offer a "sweep" function — use a reputable client and follow its instructions.
- Sign and broadcast the sweep using a network-connected machine. (Alternatively, build the raw transaction on an offline machine and broadcast from a separate online node.)
Warnings:
- Do not type or store the paper-wallet private key on an online device unless you understand the risks.
- If you must use a hot-wallet to sweep, accept that the private key was exposed to that machine.
Reference: Bitcoin paper wallet guidance — https://en.bitcoin.it/wiki/Paper_wallet
Privacy trade-offs, passphrases and multisig
Does a passphrase (25th word) help? Yes, when used correctly a passphrase adds a hidden sub-wallet (plausible deniability in some scenarios). But passphrases also increase recovery complexity and risk of permanent loss if forgotten. See /passphrase-25th-word and /seed-phrase-management for recovery planning.
Multisig + CoinJoin? Possible, but harder. Multisig increases safety for custody but requires co-signer coordination to produce PSBTs for mixing; some coinjoin clients have limited multisig support. See /multisig for setup considerations.
Connectivity risks: USB is the dominant option and generally lower risk than wireless options for signing flows. If your device supports Bluetooth or other wireless connections, assess trade-offs (see /connectivity-usb-bluetooth-nfc). Bluetooth can be convenient. But convenience can add an attack surface.
Common mistakes and security checklist
- Buying random software from untrusted sources. Always verify desktop client hashes and official download pages.
- Exposing your seed phrase while performing mixing or sweeping. Never paste or type your seed phrase.
- Sweeping into an address you won't control (typo squatting). Double-check destination addresses on-device.
- Assuming CoinJoin makes you 'invisible'. Mixes reduce linkability but do not erase on-chain history.
Quick checklist before you start:
- Firmware up to date (see /firmware-updates).
- Backup of seed phrase (metal plate recommended — see /metal-backup-plates).
- Use PSBT/air-gapped signing if possible (/air-gapped).
- Keep a small test amount to validate your workflow.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes — if you have a properly recorded seed phrase or backups (and understand passphrase usage). Follow the recovery steps in /backup-and-recovery and /device-broken.
Q: Will exchanges flag CoinJoined coins?
A: Some custodial services and exchanges may apply additional scrutiny to mixed coins. The industry changes, and policies vary. Consider on-chain reputational cost before sending mixed coins to an exchange.
Q: Is Bluetooth safe for signing?
A: Bluetooth is convenient but increases attack surface. For highest assurance use USB or air-gapped PSBT signing. See /connectivity-usb-bluetooth-nfc for more.
Q: What happens if the company behind a desktop client disappears?
A: CoinJoin and PSBT are open standards; the on-chain Bitcoin you control belongs to your keys (see /company-risk). But loss of client maintenance may affect usability and compatibility over time.
Conclusion & next steps
CoinJoin workflows increase on-chain privacy when run carefully. They pair well with hardware wallets through PSBT and air-gapped signing, and desktop clients like Wasabi and Sparrow offer different balances of convenience and control. In my experience, start small, use a test UTXO, and practice the PSBT export/sign/import loop before mixing large amounts.
Learn more: read our guides on air-gapped signing, seed phrase management, and multisig setup to build a privacy-first strategy that fits your threat model.
If you want step-by-step device setup for signing workflows, check the setup guide and the device model guides for model-specific notes.
(But don't rush it — privacy workflows reward patience.)
![CoinJoin workflow diagram — placeholder]
Sources & further reading
