Separate folders, receipts and a face-down phone representing the information boundaries around a payment, editorial illustration
Privacy / GUIDE

Bitcoin privacy: 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.

Start reading
1 min read1 imageEnglishOriginal page ↗
READING MODE

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.

01 / RoninDojo
How the components connect.
Historical example
Samourai WalletKeys and payments
DojoWallet queries and broadcast
Bitcoin CoreValidation
Whirlpool GUIDesktop controls
Whirlpool CLIMixing client
DojoWallet queries and broadcast
Explorer + indexerTransaction lookup
Ronin UINode management
Whirlpool Stat ToolHistorical statistics

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 ↗
Continue your path

One question leads to another.

01Your balance is a collection of stories02Make privacy a routine

Find your next answer.

Search the complete field guide · Esc to close