What was Whirlpool?
Whirlpool was the Samourai ecosystem’s equal-output CoinJoin system. This guide describes its original service and clients. Samourai infrastructure was seized in April 2024; Sparrow removed its Whirlpool client and Soroban-related features in 1.9.0. Old installation steps, pool fees and screenshots are historical. A separate fork must be evaluated on its own terms. For current guidance, see Your balance is a collection of stories and Ashigaru.
How the original design worked
The design used five inputs and five equal-value outputs. New entrants supplied premix inputs; outputs from earlier rounds could return as remix inputs. Equal amounts created ambiguity about which output belonged to which participant. That ambiguity was not a guarantee against timing analysis, outside information or links created by later spending.
Five participants contribute to one transaction with five equal outputs. The output order does not identify the owners. Equal amounts alone do not guarantee anonymity; fees are omitted in this schematic.
Reference ↗Historical clients and screenshots
The original stack offered mobile mixing, a desktop graphical interface and an always-on command-line client. The screenshots below record those interfaces. They are not setup instructions, download recommendations or evidence of a working coordinator. Keeping an old client online cannot by itself restore the original service.
FIG. 02Historical clients and screenshots
FIG. 03Historical clients and screenshots
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 ↗What Dojo did
Dojo served wallet data to Samourai. Running a private backend reduced reliance on the shared wallet server, but did not hide on-chain transactions or replace the mixing coordinator. The wallet backend, client and coordinator had different roles; a functioning node alone does not establish that a mixing service is available.
Tx0: preparing outputs
Tx0 was the preparation transaction, not the CoinJoin itself. It created pool-sized outputs with an allowance for mixing miner fees, paid the coordinator where applicable, and returned change. That change was outside the equal-output mix and remained linked to the preparation inputs.
The diagram preserves a historical output example. It does not quote a current fee or a total input amount. Transaction accounting must include every output and the mining fee; the old article’s stated input total did not reconcile with its listed outputs.
The archived example prepares four 0.5 BTC outputs, each with 3,020 sats for its first-round miner fee. Tx0 also pays its own miner fee. The change stays outside the mix.
Reference ↗Historical fees
The original model charged a pool entry fee at Tx0, alongside transaction mining fees. New entrants funded the mining cost of rounds involving remixers. “Free remixing” meant no additional direct fee for that remixer under those rules, not that transactions had no costs or that future rounds were guaranteed.
The diagram illustrates the old fee model, not a live quote. For unit conversion, 0.0025 BTC is 250,000 sats and 0.025 BTC is 2,500,000 sats. Old pool calculators, Whirlbot statistics and SCODE discount fields should not be used to estimate a different service’s charges.
Historical example for the 0.01 BTC pool. The percentage divides the coordinator fee by the mixed amount. Miner fees are additional; these are not current service prices.
Reference ↗FIG. 07Historical fees
- Enter the codeThe original client accepted a promotional SCODE.
- Review the feeThe discount applied to the coordinator fee, not miner fees.
- Start from that clientThe code was applied by the device preparing the Tx0.
This explains the archived interface. It is not an active offer or a setup instruction for a current service.
Reference ↗Timing and remix counts
Rounds depended on available participants, coordinator operation and client connectivity. There was no guaranteed completion time. Nor is there a universal safe number of mixes: repeated rounds do not necessarily add independent participants or remove information an observer already has. A displayed anonymity score is not a personal privacy guarantee.
Change and identity records
Keep identifiable preparation change distinct from postmix outputs when you want to avoid connecting their histories. CoinJoin does not delete exchange identity records, bank payments or a counterparty’s knowledge. Buying without an identity check is not itself proof of anonymity either.
Existing funds and cold storage
For funds in an old wallet, preserve recovery words, any , account information and labels. Confirm that recovery software supports the relevant deposit, premix and postmix accounts. Do not assume that importing a seed into any Bitcoin wallet will discover every account.
Moving to a hardware wallet changes key custody; it does not erase transaction history. Review which outputs a transfer combines and where change goes. Do not leave funds in an obsolete setup solely on the expectation that the original remixing service will resume.
STONEWALL and STONEWALL X2
STONEWALL was a spending pattern built with one wallet’s inputs, intended to resemble a two-person CoinJoin. STONEWALL X2 involved another participant while paying a third party. Their similar shapes did not make their ownership arrangements identical. Construction depended on suitable inputs; spending less than half a balance was not a universal guarantee.
Collaborators learn information during transaction construction. The design sought to make blockchain interpretation less certain, not to make every relationship unobservable. The diagram explains the historical pattern without assuming that the old collaboration service remains available.
The sender funds all inputs. Two equal outputs make the payment less obvious, but this is not a multi-person CoinJoin. Amounts are illustrative.
Reference ↗Stowaway
Stowaway was a collaborative payment in which both sender and recipient contributed inputs. The payment could be the increase in the recipient’s balance rather than the value of one visible output. This challenged the assumption that all inputs had one owner; it did not make amounts invisible to the participants or defeat every form of analysis.
The recipient adds an input and receives it back plus the payment. Here, 479,088 − 279,088 = 200,000 sats. Owner labels explain the example; they are not written on chain.
Reference ↗Reading the historical material
Use the references for the original design and the documented service changes. Old promotional claims, chat groups and coordinator statistics are not substitutes for current implementation documentation. This article explains historical mechanics; it does not endorse a replacement service or certify a recovery procedure.
