NexFlow › Is Wasabi safe

Is Wasabi safe? The wallet whose best feature was regulated away

Wasabi's file is a shape the corpus hasn't seen: nothing was breached, nothing was stolen — the company's own regulator-facing shutdown is the incident. In spring 2024, days after the Samourai arrests, zkSNACKs blocked all US users, then killed its CoinJoin coordinator entirely — the feature that made Wasabi Wasabi. What remains is a non-custodial Bitcoin wallet with Tor; what died is the privacy layer that was the point.

Updated September 28, 2026 · By the NexFlow editorial desk · Sources linked throughout; vendor claims labeled.

What Wasabi is

Wasabi Wallet is zkSNACKs' open-source, non-custodial Bitcoin desktop wallet — launched 2018 — built around three privacy technologies: mandatory Tor for all traffic, client-side block filtering (the wallet checks balances against downloaded filters instead of telling a server which addresses it owns), and WabiSabi CoinJoin — a Chaumian-blind coordination protocol that mixed users' inputs into joint transactions without the coordinator ever learning the mapping.

The custody answer is the easy part of the file: keys never leave the device, the code is open and heavily reviewed, and there is no documented theft, breach, or key-layer compromise in eight years. The complicated part is that Wasabi's safety question was never really about custody — it was about the legal standing of the one feature users came for, and that is where the entire incident record lives.

Spring 2024: the shutdown in two acts

Act one was April 27, 2024 — three days after the Samourai Wallet arrests and one day after the SEC's Wells notice to Consensys. zkSNACKs announced it was blocking all US residents and citizens from its sites and services: no downloads, no API, no RPC, no CoinJoin — effective immediately, by IP block. The message was unambiguous: the company read the Samourai indictment as a template aimed at every coordinator.

Act two was May 1–2: zkSNACKs announced it would discontinue CoinJoin coordination entirely effective June 1, 2024 — 'after years of relentless dedication' and citing the need for legal certainty it no longer had. The blast radius extended past Wasabi itself: Trezor Suite and BTCPay Server had built their CoinJoin features on the zkSNACKs coordinator, and both lost the service. The wallet kept working — sends, receives, Tor, the filter architecture — but the flagship feature, and the ecosystem integrations built on it, died by corporate decision rather than by code.

What actually remains

The post-shutdown file is worth stating precisely because the marketing confusion persists. Wasabi the wallet still runs: open-source, non-custodial, Tor-routed, with the client-side filter architecture CEO Max Hillebrand correctly noted still provides real privacy advantages over a naive SPV wallet. What is gone is the default CoinJoin service — the mix itself.

From version 2.0.8 the wallet exposes a Coordinator URI setting: CoinJoin still works if you repoint it at a third-party coordinator, and several community coordinators exist. That is simultaneously the resilience story (the protocol outlived its company — the same property the Jade oracle-design argues for) and the new risk surface: a coordinator chosen by the user is no longer audited by zkSNACKs, and the project's own GitHub record shows coordinator-side abuse already happened — one third-party coordinator exploited fee parameters to drain participants before protections were added. The company's answer — 'we only maintain the integration' — is technically true and exactly the transfer-of-trust the user now owns.

The honest read

Wasabi's incident is the corpus's first pure regulatory amputation: no exploit, no insider theft, no funds frozen — a legal environment that deleted the product's reason to exist while leaving the product standing. The precedent it set is structural: privacy features delivered through a company-operated coordinator are as removable as the company is reachable, no matter how trustless the cryptography between the endpoints.

The counterweight is equally structural. The WabiSabi protocol is open and the coordinator is a replaceable URI — the shutdown proved the architecture could survive its own maker, which is more than most centralized-privacy services could say. Samourai's fate (arrests, forfeiture) is the alternate branch: Wasabi chose the compliant exit and lived; the privacy-maximalist answer argues the choice itself proved the coordinator model was always the weak point.

The residual risks

For a Wasabi user today, the operative risks are the repointed-coordinator set: an unaudited third-party coordinator can misprice fees, selectively deanonymize rounds, or disappear mid-mix — the protections added after the documented abuse cover fee manipulation, not every adversarial posture. The US IP block remains in force, which means US-facing support, downloads, and API access are officially absent. And the ordinary self-custody set applies as always: fake downloads (the block created a scam surface — 'Wasabi for US users' phishing sites were reported), seed handling, and the Bitcoin-only scope that makes the wallet a single-asset answer.

The deeper residual is the one the shutdown itself demonstrated: any feature that requires a live third party — coordinator, server, API — is a feature whose risk model includes that party's lawyers. CoinJoin's cryptography survived intact; its service delivery did not. For a user comparing Wasabi against the rest of the wallet tier, that is the correct frame: the device-side custody is as strong as anything open-source has produced, while the feature side now carries a counterparty no seed phrase can back up.

Where Wasabi stands

In the wallet tier, Wasabi is the regulatory-exposure pole: the cleanest custody record in the family (no breach, no extraction, open source, Tor by default) paired with the corpus's clearest demonstration that a feature's legal surface can be attacked where its code cannot. The verdict the file supports: as a non-custodial Bitcoin wallet it remains one of the most privacy-engineered options that exists — Tor by default, filters that never tell a server your addresses, and a supply chain that is still the project's own. As a CoinJoin service it is now a client in search of a coordinator — the user's safety answer depends on which third-party server they trust, which is exactly the question the original product had abstracted away. Anyone choosing it in 2026 is really choosing twice: once for the wallet, once for whoever runs the mix.

Frequently asked questions