Replying to Avatar Arkad

Tradeoffs to the elimination of non-private change

https://github.com/zkSNACKs/WalletWasabi/issues/10462

I saw this problem since the first version of wasabi 2.0.

A coinjoin must be deterministic.

If it's fully deterministic using "greedy" amount decomposition every time, then an attacker could use that determinism as well to anticipate which values you claim as outputs (but not their specific addresses), which is why there's added client randomness. There's definitely still room for optimization though.

Reply to this note

Please Login to reply.

Discussion

No replies yet.