Wasabi Wallet
Wasabi Wallet is an open-source, non-custodial, privacy-focused Bitcoin wallet for desktop, implementing trustless CoinJoin.
What you should know about Wasabi Wallet
- Privacy-First Focus: Advanced Bitcoin-only wallet using CoinJoin technology and built-in Tor routing to maximize transaction anonymity.
- Non-Custodial Control: Users maintain full ownership of their private keys, ensuring funds are secure and independent of third-party control.
- BIP-158 Block Filters: Enhances privacy by downloading only relevant block information without leaking address data to network nodes.
- Intuitive Interface: Offers a modern, user-friendly desktop experience suitable for both privacy advocates and regular Bitcoin users.
Facts about the Wasabi Wallet
Why use Wasabi Wallet
Wasabi Wallet stands out from competitors like Sparrow or Samourai through its WabiSabi protocol, which enables more efficient and flexible CoinJoin transactions with varying amounts. Unlike traditional implementations that require fixed-size denominations, Wasabi 2.0 allows users to consolidate or split coins more naturally while maintaining high privacy standards.
A key advantage over Ledger or basic software wallets is its automated privacy-by-default approach. Wasabi handles Tor integration and CoinJoin orchestration in the background, making advanced Bitcoin privacy accessible without the manual 'mixing' steps or technical overhead often required by other specialized privacy wallets.
Wasabi Wallet FAQ
How does the WabiSabi CoinJoin protocol improve upon earlier iterations of trustless mixing in terms of block space efficiency and anonymity sets?
Unlike older protocols that relied on identical output amounts to provide anonymity, the WabiSabi protocol enables transactions with arbitrary output amounts. It achieves this by utilizing keyed-verification anonymous credentials and homomorphic commitments. This means users can combine various inputs and request distinct outputs in a single, block-space-efficient CoinJoin round without exposing linkages to observers.
What are the specific implications of Wasabi Wallet's default Tor integration for node operators and users routing transactions through clearnet vs onion networks?
By routing all traffic over the Tor network by default, Wasabi Wallet ensures that the user's IP address is hidden from the backend coordinator and the broader Bitcoin network. This prevents network-level surveillance from associating specific UTXOs with physical locations or identities. Users connecting to their own full nodes via onion services gain an additional layer of isolation against ISP monitoring and clearnet traffic analysis.
How does the wallet handle unconfirmed UTXOs (CPFP/RBF) during a CoinJoin round, and what are the associated fee implications?
When participating in a CoinJoin, Wasabi generally avoids using unconfirmed inputs to prevent chain-of-custody complications and fee estimation errors. If a user needs to prioritize a transaction constructed with unmixed or partially mixed funds, they can leverage Replace-By-Fee (RBF) or Child-Pays-For-Parent (CPFP) outside of the mixing rounds. Within the CoinJoin itself, fees are coordinated to ensure the transaction propagates efficiently without leaking data through anomalous fee rates.
In the context of hardware wallet integrations, how does Wasabi maintain privacy when verifying addresses directly on a Trezor or Ledger device without leaking xpubs to external servers?
Wasabi Wallet is designed as a non-custodial, client-side application that downloads block filters rather than querying central servers for address balances. When connected to a hardware wallet, Wasabi derives addresses locally and checks them against these downloaded filters. If a match is found, only the necessary blocks are retrieved over Tor. This architecture ensures that the device's extended public keys (xpubs) are never transmitted to third-party infrastructure.
What mechanisms prevent Sybil attacks or malicious disruptions during the output registration phase of a Wasabi CoinJoin transaction?
The coordinator mitigates Sybil attacks and Denial of Service (DoS) attempts by imposing a combination of cryptographic proofs and economic penalties. Participants must commit inputs and prove ownership before they are allowed to register outputs. If a participant disrupts the protocol by failing to sign the final transaction, their UTXOs are temporarily banned from participating in future rounds. This economic friction discourages malicious actors from halting the mixing process.