Skip to content

Wasabi Wallet

Wasabi Wallet is a privacy-focused Bitcoin wallet that implements CoinJoin using the WabiSabi protocol. It was one of the most popular desktop CoinJoin wallets until regulatory pressure forced changes to its operation.

Other CoinJoin Implementations

Wasabi is one of several CoinJoin implementations. Others include Whirlpool (5-party, fixed denominations) and JoinMarket (decentralized, maker-taker model). Each has different trade-offs in terms of privacy, convenience, and censorship resistance.

What Is Wasabi Wallet?

Wasabi Wallet is an open-source, non-custodial Bitcoin wallet for desktop that focuses on privacy through CoinJoin. It uses the WabiSabi protocol, which allows for flexible anonymity sets of 50-150 participants.

WabiSabi Protocol

WabiSabi is a CoinJoin protocol that allows participants to mix any amount of bitcoin, not just fixed denominations. This makes it more flexible than Whirlpool but requires more careful analysis to ensure privacy.

How Wasabi CoinJoin Works

Wasabi Wallet is available for Windows, macOS, and Linux. Download it from wasabiwallet.io.

Send bitcoin to your Wasabi wallet. This will be your premix balance.

Click "CoinJoin" and select the amount you want to mix. Wasabi will automatically find a round with other participants.

Wasabi rounds typically take 10-30 minutes to complete. The larger the round, the more privacy you get.

After the round completes, you receive post-mix outputs that are now mixed with other participants' bitcoin.

Wasabi Fees

Wasabi charges a coordination fee for each CoinJoin round:

  • Base fee: 0.3% of the mixed amount
  • Minimum fee: 3,000 sats
  • Maximum fee: No cap

Fee Comparison

Wasabi fees are higher than Whirlpool but the larger anonymity set may provide better privacy per round.

Wasabi Best Practices

  • Do Multiple Rounds

    Like any CoinJoin, multiple rounds increase your anonymity set exponentially.

  • Use Tor

    Wasabi has built-in Tor support. Enable it in settings.

  • Never Spend Post-Mix Together

    Each post-mix output should be spent independently to preserve privacy.

  • Verify the Download

    Always verify the Wasabi download signature before installing.

  • Label Your UTXOs

    Keep track of premix and post-mix UTXOs. Never mix them.

  • Be Patient

    Wasabi rounds can take time. Let the network find enough participants.

Wasabi vs Other CoinJoin Implementations

Feature Wasabi Whirlpool JoinMarket
Coordinator Centralized Centralized P2P
Anonymity Set 50-150 5 Variable
Denominations Flexible Fixed Flexible
Fees 0.3% 1% Variable (earn as maker)
Platform Desktop Mobile CLI
Tor Support Built-in Built-in Optional

In 2024, Wasabi Wallet faced regulatory pressure that led to changes in how the wallet operates. The CoinJoin functionality was modified to comply with certain requirements.

Current Status

Check the current status of Wasabi Wallet before using it. The regulatory situation is evolving and the wallet may have changed.

Common Wasabi Mistakes

Same as any CoinJoin - never spend post-mix outputs together.

Without Tor, your IP is exposed to the coordinator and other participants.

One round gives limited privacy. Do multiple rounds for meaningful privacy.

Do not mix KYC bitcoin with non-KYC bitcoin in Wasabi. Keep them separate.

Post-Mix Management

Like Whirlpool, Wasabi produces post-mix UTXOs that require careful handling. The principles are the same across all CoinJoin implementations:

  • Never spend post-mix UTXOs together - Each output should be spent independently
  • Never mix post-mix with premix - Keep mixed and unmixed coins separate
  • Label your UTXOs - Track which coins have been through CoinJoins
  • Avoid consolidation - Combining post-mix UTXOs reduces your anonymity set

For detailed guidance on managing post-mix coins and handling doxxic change, see the Whirlpool page which covers these topics in depth.

Post-Mix Best Practices

The post-mix management principles from Whirlpool apply equally to Wasabi. Never merge mixed and unmixed UTXOs, prefer spending from post-mix directly, don't reuse addresses, and be cautious with script types and consolidations.