CoinJoin Coordinator

CoinJoin coordinator is the service that orchestrates a collaborative Bitcoin transaction among many users: it collects each participant's registered inputs and outputs, assembles them into a single CoinJoin transaction, and returns it for everyone to sign. The crucial property is that the coordinator is untrusted with funds: it never takes custody and cannot steal coins, because a CoinJoin transaction is invalid until every participant independently signs the inputs they control. Any participant whose expected output is missing or altered simply refuses to sign, and the transaction dies. The coordinator's worst-case abuses are denial of service and attempted deanonymization — real threats, but categorically different from custodial risk, and both are targets of deliberate protocol design.

What the coordinator does

A mixing round runs in phases, and the coordinator is the metronome. During input registration, participants connect and register the UTXOs they want to mix; the coordinator checks them against the chain and against round rules. In output registration, each participant — over a separate network identity — registers where their mixed coins should land. The coordinator then assembles the full transaction, distributes it, collects signatures, and broadcasts. If a participant registers inputs and then disappears or refuses to sign, a blame round identifies the disruptor so the honest remainder can retry without them — the standard defense against cheap denial-of-service griefing.

What it cannot see, and what it could try

In modern protocols such as WabiSabi (used by Wasabi-style wallets), the coordinator issues blinded credentials during registration: it can verify that a participant's outputs are covered by their inputs without being able to link which outputs belong to which inputs, provided participants use fresh Tor circuits or equivalent network separation for each registration. Done correctly, the coordinator ends the round knowing the transaction it built but not the internal mapping — the same blindness any on-chain observer has. What a malicious coordinator can attempt: logging network metadata in hope of correlation, selectively excluding participants, or Sybil-flooding rounds with its own coins to shrink the real anonymity set. These attacks cost the attacker money and are probabilistic, which is why protocol papers treat coordinator honesty as a privacy assumption rather than a security one — your coins are safe regardless; your privacy degrades only if the coordinator cheats and you gave it correlatable metadata.

Centralization pressure and the response

The coordinator is nonetheless a central point — of availability, of policy, and of legal pressure, as the ecosystem learned when prominent coordinators shut down or began filtering under regulatory threat. The response has been structural: multiple independent coordinators, coordinator marketplaces where wallets discover operators, community-run and sometimes fee-free coordinators, and self-hostable implementations that let any group run its own. Spreading coordination across many operators — or removing the dedicated operator entirely — is the same decentralization instinct that drives everything else in the sovereign stack: no single switch anyone can flip.

Why it matters for sovereignty

A non-custodial coordinator means you keep your keys through the entire mix — self-custody is never interrupted, which is what separates CoinJoin from custodial "mixers" that take your coins on faith. What the coordinator restores is fungibility: coins whose histories have been collaboratively blended, so no chain-analysis heuristic can single yours out. Protecting that result afterward is your job, not the coordinator's — see anonymity set for how careless consolidation un-mixes coins, and coin control for the discipline that keeps mixed and identified UTXOs from ever touching.