bitcoin-privacy-coinjoin

Included with Lifetime

$97 forever

CoinJoin: collaborative tx where multiple users combine inputs to break common-input-ownership heuristic. Wabisabi (Wasabi 2.0), Whirlpool (Samourai), JoinMarket maker/taker. USE WHEN: implementing CoinJoin coordinator/client, evaluating privacy gain, designing post-CoinJoin hygiene.

General

What this skill does


# CoinJoin

A CoinJoin combines inputs from multiple users into a single tx
with multiple equal-amount outputs to defeat the **common-input-
ownership heuristic** that chain analysts use.

## Heuristic broken

Pre-CoinJoin: chain analysts assume "all inputs of a tx belong to
the same wallet". This is true for most txs.

CoinJoin breaks this: 10 users, each contributing 1 input, 10 outputs
of equal size. Analyst can't link any specific input to any
specific output.

## Major implementations

### Wabisabi (Wasabi Wallet 2.0)

- **Coordinator-mediated** with credential-based blinding.
- Users register inputs with the coordinator privately (blind sig).
- Anonymity within the round; coordinator can't link inputs to
  outputs.
- Wasabi 2.0 uses **WabiSabi** protocol — successor to ZeroLink.
- Default round: ~50 participants; output amounts in tiered
  denominations.

### Whirlpool (Samourai Wallet, RIP)

- **Coordinator-mediated** but Samourai shut down 2024 (legal
  action).
- Used 5x equal-output structure.
- Still technically possible but ecosystem is gone.

### JoinMarket

- **Maker/taker** model:
  - Makers offer liquidity passively, earn small fees.
  - Takers initiate CoinJoins, pay makers.
- No central coordinator — IRC + onion services.
- Slower / smaller anonymity sets but censorship-resistant.

## Privacy properties

After CoinJoin, the linked inputs:
- Have equal anonymity-set among the participants.
- Subsequent tx that mixes them can re-cluster (if you spend two
  CoinJoined outputs together, observer infers same wallet).

**Crucial**: maintain post-CoinJoin hygiene:
- Don't combine CoinJoined outputs with non-CoinJoined ones.
- Don't reuse addresses.
- Don't immediately spend (timing analysis).

## CoinJoin types

### Equal-output ZeroLink/Wabisabi
All outputs are equal (or tiered by denomination). Best privacy.

### Variable-output PayJoin (BIP78)
Different mechanism — see [payjoin/SKILL.md](../payjoin/SKILL.md).

## Use cases

- **Privacy-conscious users** wanting on-chain anonymity.
- **Pre-emptive privacy** before storing or spending large amounts.
- **Pre-spend mixing** for high-profile addresses.

## Costs

- Per-round fee to coordinator: small percentage of input.
- On-chain tx fee: shared among participants.
- Time: multiple rounds for full anonymity (hours typical).

## Status (late 2025)

- **Wasabi Wallet 2.0** (zkSNACKs): operational; some legal pressure.
- **Whirlpool**: Samourai shutdown. Some forks attempting to revive.
- **JoinMarket**: niche but operational.
- **Joinstr** (Nostr-based CoinJoin coordination): experimental.

## Limitations

- **Coordinator availability**: Wasabi requires coordinator.
- **Anonymity set size**: small rounds = weak privacy.
- **Post-mix hygiene** required; users often re-link unintentionally.
- **Exchange refusals**: some exchanges (esp. KYC-heavy) refuse
  deposits from CoinJoin outputs.

## See also

- [payjoin/SKILL.md](../payjoin/SKILL.md)
- [silent-payments/SKILL.md](../silent-payments/SKILL.md)
- [bip47-paynyms/SKILL.md](../bip47-paynyms/SKILL.md)
- [../wallets/coin-selection/SKILL.md](../../wallets/coin-selection/SKILL.md)

Files: 1

Size: 3.4 KB

Complexity: 13/100

Category: General

Source: https://github.com/claude-dev-suite/claude-dev-suite/tree/main/skills/bitcoin/privacy/coinjoin

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts