Privacy Score Dashboard in Wasabi: What the Metrics Mean and How to Improve Your Privacy

A Bitcoin user receives funds into their wallet and immediately sees a privacy score of 45%. The number raises a question: what does that score measure, and more importantly, what should the user do about it? Wasabi Wallet displays privacy metrics intended to give users insight into how well their transaction history resists blockchain analysis. The dashboard translates complex cryptographic concepts into a visual report, but only if the user understands what is actually being measured.

Many users assume that a privacy score reflects their true anonymity in absolute terms. That assumption can be misleading. A score is a relative measure of how well specific transactions or addresses have been obscured through Wasabi’s CoinJoin protocol, mixed with the history of how funds entered the wallet and whether they have been consolidated or spent in ways that could leak identifying information. The score is useful as a feedback mechanism, but it should not be mistaken for a guarantee or a final word on whether an observer can determine ownership.

How Wasabi Wallet calculates privacy scores

Wasabi’s privacy scoring system is built on the concept of Anon Set, which attempts to quantify how many other transactions or coins a given UTXO (unspent transaction output) could be confused with after passing through CoinJoin rounds. When a user participates in a CoinJoin transaction, their funds are mixed with other participants’ coins in a way that breaks the obvious connection between a specific input and output. The Anon Set represents how many alternative explanations an outside observer must consider when tracing that coin.

The privacy dashboard in Wasabi Wallet shows this information in two dimensions: Anonset from inputs and Anonset from outputs. The input Anonset measures how many possible sources a coin could have come from before it entered the CoinJoin. The output Anonset indicates how many possible destinations the coin could have been sent to after mixing. A higher number in both dimensions suggests stronger obfuscation. If a coin has an input Anonset of 100, it means a chain analyst would have roughly 100 equally plausible origins when inspecting the transaction on the blockchain.

However, Anon Set size alone does not tell the complete story. A coin with an Anonset of 500 paired with an unusual transaction size, a distinctive time pattern, or an identifiable recipient may still be linkable through clustering techniques. Wasabi’s scoring incorporates these contextual factors, not just the mixing metric. The dashboard also tracks whether a coin’s privacy has been degraded through subsequent consolidation or spending patterns. If a user combines a high-privacy coin with a low-privacy coin in a single transaction, the resulting output’s privacy typically reverts to the lower of the two, because an observer can reason that at least one input is known.

The privacy score displayed to the user is typically expressed as a percentage or a categorical label reflecting the overall quality of a coin’s anonymity set and its transaction history. Coins that have not passed through CoinJoin will show a privacy score of 0% or “not mixed,” indicating no additional obfuscation beyond the natural pseudonymity of Bitcoin addresses. Coins that have undergone multiple CoinJoin rounds and have not been consolidated with untested funds may reach scores in the 70–99% range, depending on the time elapsed and market conditions during mixing.

Understanding Anonset and blockchain privacy

The term Anonset can seem abstract when first encountered. A practical way to think about it is to imagine a sequence of identical coins moving through a mixer simultaneously. After mixing, an observer sees coins appearing in outputs but cannot directly trace which output corresponds to which input. The Anonset size represents how many participants were in the mixing round. If 50 participants joined a CoinJoin, the Anonset starts at 50 for all outputs.

But Anonset is not stable over time. As previous CoinJoin participants spend their coins or those coins are linked to real-world identities through other means, the effective Anonset of coins that have not yet been spent may actually grow. Conversely, if a coin is spent to an exchange or service that performs KYC (know-your-customer) verification, the privacy of the entire transaction history leading to that output can be retroactively compromised. An analyst can then associate earlier transactions with the now-identified participant.

Wasabi Wallet users need to understand this dynamic because it explains why the privacy score can change even when the user has not taken any action. The wallet recalculates Anonset periodically as new information becomes available about how other coins in the same CoinJoin have been spent. This is why even a well-mixed coin should not be treated as permanently private; subsequent behavior and external events can still weaken the anonymity benefit retrospectively. The privacy score is therefore best understood as a current assessment, not an immutable property of the coin.

The distinction between input Anonset and output Anonset matters for specific use cases. A coin’s input Anonset is difficult to improve further without additional CoinJoin participation, but its output Anonset can be strengthened by ensuring that when it is spent, the recipient and observers cannot easily deduce the full transaction history. This is why Wasabi Wallet emphasizes practices like avoiding consolidation before spending and keeping high-privacy coins separate from low-privacy coins during the spending process.

What a low privacy score actually means

A privacy score below 50% typically indicates that a coin has not undergone sufficient CoinJoin mixing or that its history includes consolidations that have degraded its anonymity set. A user receiving funds directly to an address without mixing will see a score near 0%, because the on-chain transaction directly links the sender to the receiver without any obfuscation. This is not necessarily a sign of failure on Wasabi’s part; it simply reflects that the coin has not yet been processed through the wallet’s privacy features.

Low scores become problematic when they persist after the user has intentionally attempted to improve privacy. If a user participates in CoinJoin rounds but then consolidates the resulting outputs with untested coins, the privacy score of the consolidated amount will drop significantly. This is by design: the wallet is warning the user that they have undermined the privacy benefit of mixing by combining it with coins that lack protection. The dashboard serves a practical purpose here by making the consequence visible.

Another reason for low scores is insufficient confirmation age. Wasabi’s privacy calculations take into account how long ago a CoinJoin round occurred and how many blocks have been confirmed since. A coin that was successfully mixed only a few minutes ago may have a lower score than the same coin checked a week later, even though the mixing parameters are identical. This reflects the reality that privacy sometimes improves passively as time passes and more on-chain activity accumulates, making the relative visibility of any single transaction smaller.

Users should also recognize that low scores on newly received coins are normal and expected. The wallet is displaying the starting point, not a failure state. The question is not why the score is low initially, but rather how the user can improve it through their deliberate choices about mixing, consolidation, and spending patterns. A user who receives funds and immediately attempts to spend them to another service without mixing should expect the score to remain low, because Wasabi cannot retroactively improve privacy for coins that are not given the opportunity to be mixed.

Strategies for improving your privacy score in Wasabi Wallet

The most direct path to higher privacy scores is consistent participation in CoinJoin rounds. Wasabi automates much of this process through its queue system, where a user can deposit funds intended for mixing and let the wallet automatically participate in the next available round. Users can set preferences for minimum Anonset targets, and the wallet will continue mixing until those thresholds are met. This automated approach reduces friction compared to manually initiating each CoinJoin round.

However, users must exercise discipline regarding consolidation. If a wallet contains both mixed and unmixed coins, the user should avoid combining them in a single transaction until they have consciously decided that the privacy benefit of mixing is less important than the fee savings of batching. For users who care about privacy, the rule is straightforward: spend mixed coins to unmixed outputs without consolidation, or consolidate only with coins that share similar privacy histories. Wasabi’s coin selection interface encourages this by allowing users to manually choose which coins go into a transaction.

Another tactic is to allow sufficient time between receiving funds and spending them. A coin that has been in the wallet for several weeks and has participated in multiple CoinJoin rounds over that period will have a stronger privacy profile than one that was received and spent immediately. This is not a guarantee against analysis, but it allows additional on-chain activity to accumulate in the background, increasing the computational and temporal distance between the receiving transaction and the spending transaction.

Users can also improve privacy by controlling transaction size. Unusually large or small transactions stand out on the blockchain and can be used as heuristics to trace coins despite CoinJoin participation. Spreading transactions across multiple smaller payments, or batching several ordinary-sized payments together, can reduce the distinctive patterns that analysts use. This requires more planning and potentially higher fees due to multiple transactions, but it acknowledges that Wasabi’s privacy protection is most effective when combined with thoughtful spending discipline.

For users managing larger amounts of Bitcoin, participating in private CoinJoin rounds designed for higher-value coins can provide stronger privacy than standard public rounds. These rounds typically have larger minimum input amounts and produce higher Anonset values due to the size of the mixing pool. The trade-off is higher fees and potentially longer wait times, but the privacy improvement can be substantial. The wasabi wallet features tools to help users identify which CoinJoin pools offer the best combination of privacy and cost for their specific situation.

Privacy score limitations and why you should not over-rely on the metric

The privacy score is a simplified metric applied to a complex threat model. One major limitation is that it reflects only what Wasabi can measure: the Anonset from CoinJoin participation and the user’s coin history within the wallet. It cannot account for external information that an adversary may possess. If a user deposited funds to Wasabi from a tracked exchange account using KYC, an analyst with access to the exchange’s records already knows the identity of the original owner, regardless of the Anonset value. Wasabi’s dashboard cannot and does not measure this pre-existing compromise.

Another limitation concerns the assumption that all coins within a CoinJoin round are truly independent. In practice, some participants may be operated or influenced by surveillance entities, which can enable partial de-anonymization even if the Anonset is high. The privacy score assumes that all participants are honest, which is a strong assumption. Additionally, the score does not account for network-level surveillance such as observing which node broadcasts the transaction, unless the user has configured Wasabi to use Tor or a custom node to mitigate this risk.

Transaction fees and timing patterns can also leak information that the privacy score does not capture. If a user always spends at a certain time of day or always conducts transactions of a particular size, an adversary with sufficient historical data may identify the user’s behavior even if the Anonset is high. Wasabi’s score focuses on the mixing metric and does not penalize these behavioral patterns, but a thoughtful user should consider them separately as part of their operational security strategy.

Users should also understand that a privacy score is point-in-time information. A coin with a score of 85% today might have a lower effective score in six months if many other participants in the same CoinJoin round spend their coins to identifiable addresses. Conversely, it might have an even higher effective score if the blockchain has accumulated enough additional transactions that the relative fingerprint of the original CoinJoin has become smaller. The privacy dashboard shows the current state, not a prediction or guarantee.

Practical workflow: from receipt to high-privacy spending

A typical workflow for a user who prioritizes privacy would begin with receiving Bitcoin into a Wasabi Wallet address. The privacy score will initially be 0% because the coin is not yet mixed. The user should then wait a short time to allow the transaction to confirm, then enable automatic CoinJoin mixing. Wasabi will register the coin for mixing and join the next available CoinJoin round after a brief delay to avoid wallet fingerprinting attacks based on immediate mixing patterns.

After the first CoinJoin round, the privacy score might increase to 30–50%, depending on the pool size and the round parameters. Rather than spending immediately, the user can allow the wallet to participate in additional rounds. Each subsequent round increases the Anonset and the privacy score further. Wasabi’s automation means the user does not need to actively manage this; they can simply leave the wallet running (or set it to auto-start) and let the mixing occur in the background over several days or weeks.

Once the privacy score reaches the user’s target threshold—often 70% or higher for meaningful privacy—the coin is ready to be spent. The critical step is to spend the mixed coin without consolidating it with any unmixed coins. If the user has other funds in the wallet that have not been mixed, they should use Wasabi’s coin selection interface to explicitly choose only the mixed coins for the transaction. This preserves the privacy benefit of mixing by ensuring the spending transaction does not link the mixed output to an unmixed input.

If the recipient is a known service such as an exchange requiring KYC, the privacy benefit may be partially or fully compromised at the point of spending. The Anonset protects against blockchain analysis of the transaction history, but it does not protect against identification by the receiving party if they have regulatory compliance obligations. Users should therefore be realistic about what privacy protection is appropriate for their specific use case. For peer-to-peer payments or withdrawals to services without KYC requirements, the privacy benefits of high-score coins are more meaningful.

Hardware wallet integration and privacy score implications

Wasabi Wallet supports hardware wallet integration with Ledger, Trezor, and Coldcard devices. This combination—non-custodial private key management plus privacy-focused transaction handling—addresses two separate security concerns: protecting against wallet software compromise and protecting against blockchain surveillance. The privacy score applies to coins managed through hardware wallets the same way it applies to coins managed by the wallet’s internal key storage, because the privacy protection is a function of the transaction mixing, not the key management method.

Users employing hardware wallets with Wasabi should understand that the privacy workflow remains identical. Funds are received into an address derived from the hardware wallet’s extended public key. The wallet displays the privacy score for those coins. CoinJoin participation requires the hardware device to sign transactions, which means the hardware wallet must be physically connected during mixing rounds. This adds a minor operational inconvenience compared to mixing with coins stored on the device itself, but it provides stronger isolation of the private keys.

The privacy score benefits from hardware wallet integration because the user’s private keys are never exposed to Wasabi’s software, reducing the risk of private key compromise through wallet application exploits. However, the privacy score itself is not affected by this architectural choice. A coin’s Anonset and privacy metric depend on its mixing history and transaction patterns, not on where the private keys are stored. The privacy dashboard will show identical scores regardless of whether the device is a hardware wallet or an internal key store.

Future improvements and evolving privacy metrics

Wasabi Wallet continues to develop, with planned improvements including faster CoinJoin rounds and enhanced mobile interoperability. These changes will likely influence how privacy scores are calculated and displayed. Faster rounds mean more frequent opportunities for users to improve their Anonset, potentially allowing more users to reach high privacy scores with less waiting time. Enhanced mobile interoperability could enable users to participate in CoinJoin rounds from mobile devices, expanding the pool of participants and potentially increasing Anonset values across the board.

The privacy scoring system itself may evolve. Future versions of Wasabi Wallet might incorporate more sophisticated threat modeling, such as accounting for network-level information, behavioral pattern analysis, or the likelihood of linked accounts. Developers might also introduce more granular scoring that distinguishes between different types of privacy threats rather than reducing everything to a single percentage. Users should periodically review the official Wasabi documentation to stay informed about how the metrics have changed.

One area of ongoing research is the relationship between CoinJoin pool size and real privacy. As the Bitcoin ecosystem develops, larger pools may become common, which would increase Anonset values; or pool sizes might stagnate, limiting privacy improvements. Wasabi’s ability to adapt to market conditions and maintain a healthy pool of participants will directly influence how useful the privacy score remains as a measure of actual anonymity. Users monitoring the wallet’s development should pay attention to updates about pool participation rates and average round sizes.

The broader challenge for privacy-focused Bitcoin wallets is maintaining the balance between user-friendliness and technical accuracy. A privacy score that is too simple may mislead users into a false sense of security; a score that is too complex may discourage adoption. Wasabi’s current dashboard represents one solution to this balance. As threats and techniques evolve, the metric will likely evolve as well, and users should treat the score as a useful feedback mechanism rather than a definitive statement about their true anonymity.