Truths about coinjoins:
- Wabisabi has a superior architecture to Whirpool.
- Including change in the coinjoin as in Wasabi 1.0 is in any case an advantage, not a disadvantage. If you don't understand this, it's simply because you don't understand the math.
- There is no such thing as isolated change in Whirpool; changes are traceable.
- With Wabisabi, you can forget about change problems and Postmix tools.
- Wabisabi is not free as they sell it to you; the coordinator continues to make money from decomposition.
- Wabisabi does manage Tor circuits well; I checked the code myself (Nothingmuch says no, and I have to trust him because he knows much more than I do).
- Whirpool does not manage Tor circuits well, and the coordinator can find out who is on each side of the mix (I have not reviewed the Ashigaru code that they say has mitigated this, proving me right, which I was denied at the time).
- Whirpool and Wabisabi are vulnerable to tagging attacks.
- In Whirpool and Wasabi, you have to trust the coordinator; you don't know if they are really executing the published code.
- Joinmarket is complex for someone who doesn't know what they are doing, but it can mitigate the problems described above.
- Joinstr, in my opinion, is the most promising; it mitigates most of the problems described in centralized coordinators and is easy to use.
I think the community should throw its weight behind supporting #Joinstr
