Skip to content
CUNICULA

Wasabi Wallet

Self-custodial Bitcoin desktop wallet with Tor, Silent Payments and optional third-party coordinated CoinJoin.

wasabiwallet.io

Self-custodial Bitcoin desktop wallet with Tor, Silent Payments and optional third-party coordinated CoinJoin.

Common useWalletWalletOperator dataUnknown
Identity checksNo routine KYCNo document check recorded · identity exposure level 0/4
Evidence and riskVerified evidenceCautionMaterial claims checked against current sources.; those sources show trade-offs worth reading.
Last reviewedReviewed 8 Nov 2026KYC checked 8 Nov 2026 · unknown jurisdiction · Source → official documentationHow to cite this pageSource coverageVerified evidenceRecorded riskCaution
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
39/100Reviewed evidencePrivacy 21/25 · Control 20/20 · Transparency 15/20 · Security 12/25 · Accountability 3/10 · Cap 39 · Method
JURISDICTIONUnknown
CAUTIONThe original zkSNACKs coordinator ended on 1 June 2024; CoinJoin continues through user-selected third parties with their own policies/liquidity. Tor is default but disabling it exposes IP linkage. Coordinator manipulation and metadata risks remain. Maintainers disclosed a replaced Windows installer and exploited coordinator-fee flaw in July 2024, reporting removal/access revocation and a 2.1.0 fix. Current 2.8.5 includes further security updates; update and verify signatures. Older macOS wallets using compatibility passphrases need the documented recovery/migration precautions.
INCIDENTRPC exposure and resource-exhaustion fixes in 2.8.4
monitoring · potential medium · published 2026-10-13
Version 2.8.4 includes RPC authentication hardening and a credential-request CPU bound. RPC changes stop buffering request bodies before authentication and restrict the onion-enabled listener to loopback instead of every interface. Wasabi v2.8.4 release, RPC authentication hardening PR15134
INCIDENTCoinJoin input-validation security fix in 2.8.2
monitoring · potential medium · published 2026-08-29
Version 2.8.2 reports CoinJoin security fixes. Its linked input-validation change checks other participants' input existence, scripts and values; the reviewed implementation uses random sampling. Wasabi v2.8.2 release, Input-verification PR14886, merged 30 July 2026
INCIDENTWindows installer replaced through a compromised repository account
monitoring · potential high · published 2024-07-10
Maintainers reported replacement of the Windows 2.0.8.1 MSI after a GitHub write-access account was compromised. Wasabi security incident disclosure, 10 July 2024
INCIDENTMalicious coordinator exploited fee validation
monitoring · potential high · published 2024-07-10
Maintainers confirmed that wasabicoordinator.io exploited a fee-validation flaw and reported a version 2.1.0 fix. Wasabi security incident disclosure, 10 July 2024
AUDITED BYNo audit listed
OPERATOR DATAUnknown
SOURCE COVERAGE
Verified evidenceTHIRD-PARTY REPORTED8/10Reviewed 8 Nov 2026 · Source → official documentation
LAST CHECKED2026-08-26
LAST UPDATED2026-06-22

Specs

DOCUMENT CHECKNone recorded
IDENTITY EXPOSURELevel 0/4
KYC TRIGGERSNo account or identity KYC to use the wallet. CoinJoin now depends on user-selected third-party coordinators, so coordinator policy/liquidity varies.
FEEFree wallet software; Bitcoin mining fees and third-party CoinJoin/round costs apply.
CATEGORIESWallet
FEATURESBitcoin CoinJoin, Tor built-in; enabled by default, Self-custody, Open source, Desktop, UTXO management, Third-party coordinators, Silent Payment sending
TORYes
REGIONSGlobal availability
Review analysis, source material, related services, and history

Analysis

OVERVIEW

Wasabi is an open-source, self-custodial Bitcoin desktop wallet maintained beyond the original zkSNACKs coordinator. Current 2.8.5 documentation describes Tor, compact-filter synchronization, hardware-wallet support and Silent Payment sending, not receiving.

LIMITS

The original zkSNACKs coordinator stopped on 1 June 2024; third-party CoinJoin continues with independent coordinator policies, costs and metadata risks. A current incorporated operator and direct OFAC-causation claim were not established. Maintainer disclosures and later security releases require current version/signature checks.

USEFUL FOR

Bitcoin desktop-wallet comparison with the chosen third-party coordinator, release security and Tor/metadata settings assessed separately.

Corporate identity

Other cited research; Provider statements. Not audited. Each claim links its own source.

PREVIOUSLY TRADED AS
  • zkSNACKs: company originally behind Wasabi; its coordinator ended2024-06-01.2019 investor disclosure concerns historic shares, not present ownership. Exact historic registry number/jurisdiction/date not independently re-established in this review.
other research ↗
Corporate identity research · reviewed 2026-11-08

We wrote about this

Frequently Asked Questions

Is identity verification required?

No identity verification is recorded for typical use. No account or identity KYC to use the wallet. CoinJoin now depends on user-selected third-party coordinators, so coordinator policy/liquidity varies.

Where is it available?

Recorded availability: GLOBAL.

Is the operator based in a Five Eyes country?

The jurisdiction is not publicly confirmed. Check the provider site for incorporation details.

How are identity, operator, and evidence fields reported?

Identity exposure is level 0 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is verified evidence, last reviewed 2026-11-08, and recorded risk is caution.

Related Services

Compare

Sources and history

Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.