Whirlpool

Whirlpool is a Chaumian CoinJoin implementation built on the ZeroLink framework, originally developed by the Samourai Wallet team. Its goal is to maximize the ambiguity of which input maps to which output by mixing coins in fixed denominations and uniform transaction shapes, so an outside analyst cannot follow a specific coin through a mix. It is one of the most studied designs in Bitcoin privacy, and understanding it — both its mechanics and its history — is core education for anyone who takes self-custody seriously.

Equal pools, equal outputs

Whirlpool organizes mixing into pools of fixed denominations, with each round structured as exactly five inputs and five identical outputs — the equal-output CoinJoin discipline taken to its cleanest form. Because every output in a round is the same amount, there is no way to distinguish outputs by value, and a single mix yields many equally plausible input-to-output interpretations. Each round mixes fresh entrants with remixers from earlier rounds, so repeated participation compounds the ambiguity and grows a coin's effective anonymity set over time. Remixing was free after the initial pool fee, which encouraged coins to keep cycling. A coordinator schedules rounds and assembles the transaction, but because the design is a Chaumian CoinJoin using blinded registration, it remains non-custodial: the coordinator never holds user funds and cannot link a user's inputs to their outputs.

Entry into a pool goes through a preparatory transaction the design calls Tx0, which splits an arbitrary-sized UTXO into pool-denomination premix outputs (plus change that deliberately never mixes). Fees were charged once at Tx0 per entry rather than per round, which is what made indefinite remixing economically sensible — the longer a coin cycled, the deeper its ambiguity grew at no extra cost.

One honest caveat completes the picture: CoinJoins are unlinkable, not invisible. The rigid five-in, five-out, equal-amount structure is easy for chain analysts to recognize, so mixing announces that privacy was sought even while hiding which coin went where. Users should understand both halves of that sentence — the strength of the ambiguity and the visibility of the technique — before deciding how mixed coins fit their threat model.

The coordinator lesson

Whirlpool's history is now inseparable from its architecture. In April 2024, U.S. authorities indicted the Samourai Wallet founders and seized the project's infrastructure, and the Whirlpool coordinator went offline. No user funds were taken — the non-custodial design held — but mixing stopped, because the coordinator was a single, centralized scheduling point. The episode is the clearest real-world demonstration of the trade-off between coordinator-based mixing and the market-based, decentralized approach of JoinMarket, which has no central coordinator to seize. Coordinator software derived from the design has since been continued by other groups, but the structural lesson stands: a privacy protocol is only as censorship-resistant as its most centralized component.

What Whirlpool teaches

Three durable lessons survive regardless of any particular deployment. First, uniformity is strength: equal denominations and identical transaction shapes are what defeat amount-based clustering, and that discipline costs convenience — users mix in set denominations, not arbitrary amounts. Second, the mix is only half the job: post-mix spending hygiene decides whether the ambiguity survives, since carelessly consolidating mixed outputs re-links everything the rounds worked to separate. Third, independent research matters — analysts have probed how anonymity-set quality varies across pools and over time, and honest privacy tooling welcomes that scrutiny.

For the sovereign Bitcoiner, Whirlpool is best understood as a landmark design in an ongoing engineering conversation: a demonstration that strong, non-custodial transaction privacy is achievable, and a caution about where centralization hides. Study the mechanism, learn the post-mix discipline, and weigh coordinator trust as carefully as you weigh cryptography.