Wasabi Wallet - Total Privacy For Bitcoin

[Kruw]

Why not just make every client have an encrypted indexer?

Wasabi is a light client, you need a full node to build an indexer.

(Unless I'm misunderstanding your post, the rest of the context confuses me)

[NotATether]

Why not just make every client have an encrypted indexer?

Wasabi is a light client, you need a full node to build an indexer.

(Unless I'm misunderstanding your post, the rest of the context confuses me)

Basically I'm assuming that the output of an indexer is just a list of silent payment addresses that it is aware of, along with some supplementary metadata.

The rest of the post is just a design idea on how to encrypt that list so that it can be saved on to light clients without compromising privacy.

[Kruw]

Bump.

[alani123]

I kinda understand why so many Devs supporting bitcoin's decentralisation quit or disappear from the public eye.

Here's some DeFi idiots trying to frame wasabi wallet as supposedly being implicated in DPRK hacks.



 These defi idiots want to ruin decentralisation for everyone.

[Coinjoiner21]

It is not inherently bad to publicly post your analysis.  Chain analysis companies already know those bitcoin have been coinjoined through Kruw's coordinator. 

Bitcoin privacy should not be at stake just because one entity ever might shutdown.  God willing, future releases of Wasabi Wallet will come with a coordinator list that allows you to select any coordinator advertised over Nostr, without leaving the app.  I am working on this.

[BlackHatCoiner]

One problem with this wallet is that an observer can examine all the coinjoins of a coordinator and de-anonymize people based on timing patterns.

For example, Bob receives his weekly payout on an address, and Alice receives her monthly payment on another address. If across 1000 coinjoins, we notice that Alice and Bob coinjoin at the same coinjoins, there is a high probability that Alice is Bob.

I know about the coin isolation feature, but I'm afraid this does not fully address the problem. It is certainly better if those two addresses coinjoin at different rounds, but it is still trivial to detect how close their rounds are and still arrive at the same conclusion. For example, if across 1000 coinjoins, Alice coinjoins at rounds 401, 405, 750, 753 and 890 while Bob coinjoins at rounds 402, 406, 751, 752 and 889, there is strong correlation between those two identities.

Wouldn't it be better if Wasabi allowed the user to randomly schedule when the coins will join? The user would have to leave the app running for a lot longer, though.