Wasabi Wallet

What Is Wasabi Wallet?

If you hold bitcoin and don’t want every future payment to broadcast your entire financial history, you need two things: (1) good coin control so you don’t accidentally “link” coins together, and (2) a practical way to break on-chain linkability when you do need to spend. Wasabi is built for that problem—helping you manage and spend BTC with fewer privacy leaks than a typical wallet, and (optionally) improve privacy using CoinJoin.

Wasabi is a desktop, non-custodial Bitcoin wallet (you control the keys) focused on privacy-preserving spending and coin management. The project is open-source under the MIT license, and the code is available publicly.

The wallet’s distinctive feature is its CoinJoin implementation based on the WabiSabi protocol—designed so a central coordinator can assemble CoinJoin transactions without being able to steal funds, and with protocol-level privacy properties intended to limit what the coordinator can learn about input/output linkages.

Wasabi Wallet Features and Performance

Wasabi’s core value is privacy-first coin management, not “do everything” crypto support. It’s Bitcoin-focused and built around UTXO handling: labeling, selecting specific coins, and separating “private” coins from non-private ones so you don’t accidentally merge them and undo prior privacy work. Wasabi’s documentation explicitly describes behaviors like avoiding spending non-private “change coins” automatically, instead pushing them back into future CoinJoin rounds.

CoinJoin via WabiSabi (coordinator-based)

Wasabi CoinJoin uses WabiSabi, an anonymous-credential-based design intended for centrally coordinated CoinJoins with variable amounts. The public WabiSabi repository and protocol documentation describe a coordinator-assisted protocol where users register inputs and outputs to build a joint transaction, with the goal that no direct input↔output link is observable to the coordinator or other participants.

In modern Wasabi documentation, CoinJoin operation is heavily “set-and-let-run”: the wallet can coinjoin automatically in the background, driven by a built-in “robot” with user-configurable settings (like when to start, when to stop, and how aggressive to be). Wasabi ships with multiple CoinJoin strategies—documented as “Enhance Privacy,” “Default Strategy,” and “Reduce Costs”—which tune things like anonymity score targets and coin isolation behavior.

Important operational detail: CoinJoin requires a configured coordinator. Wasabi’s own docs say a coordinator must be configured before CoinJoin can be used for the first time, and community support discussions note that the default zkSNACKs coordinator suspended its CoinJoin service as of June 1, 2024—meaning CoinJoin still exists in the wallet, but you must point Wasabi at another coordinator (or run your own).

Fees and speed characteristics (what “performance” really means here)

CoinJoin “performance” isn’t just CPU speed—it’s the time to get rounds, the fee environment, and whether your wallet can reach your privacy target without getting stuck. Wasabi’s docs describe automatic CoinJoin behavior with thresholds (for example, a default stop threshold of 0.005 BTC) and an anonymity score target that determines when funds are treated as private enough. Those settings directly impact how long CoinJoin runs and how many rounds you end up participating in.

On cost behavior: Wasabi’s documentation states that as of Wasabi version 2.2.0.0 the client will only participate in CoinJoin rounds where it pays mining fees for the blockspace it uses, and it will not participate if the coordinator charges a separate “coordination fee.” The docs also note a rare case where leftover change (up to 10,000 sats per CoinJoin) can go to the coordinator because creating tiny outputs would harm privacy and can cost more than forfeiting them.

Wasabi also exposes user controls that indirectly affect speed and cost: users can set a maximum CoinJoin mining fee rate they’re willing to pay and a minimum input count required for a round. The docs give defaults (maximum 50 sat/vByte, minimum 21 inputs), which are practical guardrails for avoiding tiny rounds and runaway fee conditions—but they can also cause CoinJoin to wait longer if your requirements are strict.

PayJoin (P2EP) support

Wasabi includes PayJoin (Pay-to-EndPoint / P2EP) support, which is a different privacy tactic than CoinJoin: it’s a collaborative transaction between sender and receiver that breaks common input ownership heuristics and is designed to be less obviously a CoinJoin on-chain. Wasabi’s docs describe coordination details (receiver reachable via Tor onion or clearnet endpoint and communicated via a BIP21 URI).

RPC automation

For power users and integrators, Wasabi provides an RPC interface. The documentation lists a broad set of wallet and privacy-related methods, including listing coins, sending, building/broadcasting transactions, starting/stopping CoinJoin, and “pay in CoinJoin” flows. That matters if you’re trying to automate wallet operations or integrate Wasabi into a larger privacy workflow.

Platform support and build transparency

Wasabi’s primary distribution is as desktop software (Windows, macOS, Linux). The official GitHub repository describes it as an open-source, non-custodial, privacy-preserving Bitcoin wallet for Windows, Linux, and Mac, and the docs describe downloading from the official website or Tor onion service and verifying PGP signatures.

Pricing and Plans

Wasabi Wallet itself is free to use (no paid plan tiers for the wallet application). This aligns with Wasabi’s own documentation stating anyone can use it free of charge, and the project is distributed as open-source software.

CoinJoin costs are primarily mining fees (and coordinator policies), not a subscription. Current Wasabi docs state the client will only participate when it pays mining fees for the blockspace it uses and will not participate when a coordinator charges a separate coordination fee. Also note the documented edge case where up to 10,000 sats of leftover change can go to the coordinator.

Because Wasabi is free software rather than a paid service, there is no standard refund window to evaluate at the wallet level. Your “costs” are network fees and whatever terms a third-party coordinator might impose (if you choose to use one).

Privacy and Security Assessment

Non-custodial design and open-source posture

Wasabi is explicitly non-custodial (you control keys; the wallet is not holding your BTC for you) and the codebase is open-source under the MIT license, with public repositories for the wallet and the WabiSabi protocol implementation. That’s a real security advantage: the code is inspectable, buildable, and can be scrutinized by third parties.

Coordinator reality: privacy design vs. operational trust

WabiSabi is designed so the coordinator cannot steal funds and (per protocol goals) should not be able to directly map inputs to outputs. However, CoinJoin is still coordinator-based in practice: you depend on some coordinator being available and properly configured. Wasabi’s own documentation makes clear you must configure a coordinator, and community discussions confirm the default zkSNACKs coordinator halted CoinJoin service on June 1, 2024—an operational disruption that mattered for real users.

The wallet now supports “coordinator selection” in the UI (so you can point it somewhere else), but that shift also means privacy outcomes depend on which coordinator you choose and how it behaves. The project documentation warns that older “coordination fee” concepts were removed because they could be abused by malicious coordinators and/or require added trust (for example, “free remixes” not being enforceable in-protocol).

Jurisdiction and U.S. user restrictions (historically significant)

There’s documented fallout from regulatory pressure in 2024 around coin-mixing services. Reporting and secondary documentation around that period describe zkSNACKs sunsetting its CoinJoin coordinator service effective June 1, 2024.

Additionally, public slide material (citing a dated statement) reports zkSNACKs blocking U.S. citizens and residents from visiting its websites, downloading/using Wasabi Wallet, and using the CoinJoin feature, effective April 27, 2024 “until further notice.” This is a big deal for U.S.-based users evaluating operational risk (availability, access, and compliance posture).

Because these restrictions and service changes are time- and entity-specific, you should treat “Wasabi Wallet the open-source app” separately from “zkSNACKs-operated services or infrastructure.” The wallet code can remain usable while a particular provider’s services do not.

Known research criticisms and limits of anonymity

Academic work has examined CoinJoin implementations (including Wasabi) and the realities of measurable privacy. For example, research on input-output mapping in CoinJoin transactions with arbitrary values reports that effective anonymity set sizes can decrease due to fees, implementation constraints, and user behavior, and includes Wasabi 1.x and 2.x among designs analyzed. The takeaway: CoinJoin helps, but it’s not magic—privacy depends on how rounds are constructed and how you behave post-mix.

Incident history and audits

Wasabi publishes code openly and ships signed builds with guidance for PGP verification, but we did not find an authoritative, current claim (in the sources reviewed) of a formal third-party security audit of the full wallet comparable to a paid commercial audit report. If you need audited assurances, you’ll have to independently verify whether any third-party audits exist and what they covered.

Strengths and Limitations

Strengths

• Serious privacy tooling, not just a “send/receive” wallet. Wasabi’s design emphasizes coin labeling/selection and workflows meant to reduce common privacy mistakes (like consolidating mixed and unmixed coins).
• Modern CoinJoin protocol work. WabiSabi is documented publicly as an anonymous-credential scheme for centrally coordinated CoinJoin, with protocol docs available for scrutiny.
• Coordinator fee model tightened. Wasabi docs state the wallet will not join rounds that charge a coordination fee, and focuses on mining-fee-only participation (with a small documented leftover edge case).
• Automation options. CoinJoin can run automatically, with strategy presets and configurable thresholds, which reduces friction for users who actually follow through on privacy hygiene.
• Power-user features. RPC support is real and documented, enabling scripted workflows and deeper control.

Limitations / trade-offs

• CoinJoin depends on a coordinator you choose and trust operationally. You need a working coordinator configured; the historical default service shutdown shows this isn’t theoretical.
• Not hardware-wallet CoinJoin. Wasabi’s CoinJoin docs state it’s not possible to CoinJoin from a hardware wallet; keys must be hot on your computer for CoinJoin participation.
• Privacy is conditional. Research indicates effective anonymity can degrade depending on fees, design details, and user post-mix behavior.
• Regulatory pressure has had real product impact. zkSNACKs shutting down its coordinator (and reported U.S. blocks) created friction and uncertainty for users relying on default infrastructure.

Who Should Use Wasabi Wallet?

Good fit

1. Bitcoin users who care about day-to-day privacy hygiene. If you want coin labeling, deliberate coin selection, and guardrails against merging “private” and “non-private” funds, Wasabi is built for that.
2. Users willing to run (or select) a CoinJoin coordinator and tune parameters. Wasabi is workable if you understand that CoinJoin is coordinator-based and you’re prepared to configure one rather than relying on a default forever.
3. Power users and developers needing automation. The RPC interface and documented commands make Wasabi more scriptable than many consumer wallets.

Not a great fit

1. People who want a “set it and forget it” default mixing service run by the wallet vendor. The historical shutdown of the default coordinator shows that assumption can break.
2. Users who insist on hardware-wallet-only signing for everything, including CoinJoin. Wasabi’s docs say CoinJoin requires hot keys on the computer.
3. Anyone who expects anonymity guarantees. CoinJoin meaningfully improves privacy for many use cases, but published research suggests anonymity can degrade with real-world constraints and behavior.