Walletwasabi: Local Chain Analysis and Visual Privacy Indicator in History

Created on 25 Jul 2019  路  2Comments  路  Source: zkSNACKs/WalletWasabi

Problem

Currently, the History tab shows only rudimentary transaction details, like date, amount, txid, number of confirmation [see #1407 & #1962]. There is no indication and user guiding information about the privacy of the transactions. It is not even clear if this was a coin join or a spending transaction. If the user wants to see extra information, there are some third party block explorers that offer such level of details [esplora, oxt, kycp, blockchair], but this can lead to IP leaking and other privacy fails.

Solution

Add chain analysis tools in the Wasabi GUI History tab that show the privacy nuances of every transaction. This can include several of the tools that are already available, including but not limited to:

  • address reuse warning
  • coin consolidation cluster merging
  • zero link analysis
  • anonset
  • entropy
  • fee overpayment
  • change detection

Advantages

This gives the user more information to make better decision in regards to their privacy. With this visual indicator that the transaction is leaking privacy, this will hopefully reduce the number of privacy breaking user mistakes, or at least educate the user when one has been made.

Because the user does no longer have to leave wasabi to get detailed transaction information, there is less third party risk and fails in the network level privacy.

This also means that every user can check on the zero link transactions, and a potential bug or issue would be noticed sooner.

In general - moar privacy tools = moar better

[Thanks [CryptoNT](https://twitter.com/CryptoN_T) for the feature request in DM]

featurenhancement

Most helpful comment

I approve. I would also recommend that people access these services through tor and exercise some time limit between search queries between utxo searches so that we limit down the possibility for linking them through Tor also. I also asked TDevD to prove that the site exercises a zero log policy, so that it would further enforce log wiping, but I'm not sure how it is possible to enforce that especially on KYCP or OXT.

All 2 comments

I approve. I would also recommend that people access these services through tor and exercise some time limit between search queries between utxo searches so that we limit down the possibility for linking them through Tor also. I also asked TDevD to prove that the site exercises a zero log policy, so that it would further enforce log wiping, but I'm not sure how it is possible to enforce that especially on KYCP or OXT.

Could tack on a similar analysis that blockstream.info does, where it'll tell you if you're overpaying fees, and if you're outputs are distinguishable (ie round values are probably not the change output)

Link to espolra's privacy analysis code: https://github.com/Blockstream/esplora/blob/master/client/src/lib/privacy-analysis.js

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yahiheb picture yahiheb  路  3Comments

nopara73 picture nopara73  路  3Comments

RiccardoMasutti picture RiccardoMasutti  路  3Comments

MaxHillebrand picture MaxHillebrand  路  3Comments

MaxHillebrand picture MaxHillebrand  路  3Comments