Bitcoin CoinJoin Coordination
This lens is for Bitcoin privacy systems where the decisive mechanism is not just the transaction format, but how participants get coordinated into joint transaction construction, credential issuance, liquidity matching, or interactive state handoff.
Questions worth asking:
- Who coordinates counterparties into a shared transaction, swap, round, or state transfer?
- Where do denial-of-service resistance, sybil resistance, input registration, output registration, or blame rules live?
- Does privacy depend on a central coordinator, a federated service set, or open maker/taker discovery?
- Which wallet defaults quietly decide whether users join a privacy set, reuse change heuristics, or fall back to a weaker path?
Good comparison set
- Coordinator-run baseline: wasabi, wabisabi, and whirlpool
- Market or counterparty-discovered path: joinmarket and payjoin
- State-handoff cousins where the coordination object stops being a classic CoinJoin round: client-side-validation, rgb, ark, and mercury-layer