To implement a coinjoins protocol you must first understand Joinmarket and the risks it mitigates. - You do not need a complex privacy scheme at the network level because there is no centralized coordinator, you are the coordinator or someone else is the coordinator. - Likewise you don't have tagging problems for the same reason as above. The only problem with Joinmarket is knowing how to use it to mitigate other privacy risks and the best way is: - Run as maker until the last mix and freeze the coins, when you go to use it run a coinjoin as payment, this way you have run both taker and maker role mitigating the risks of using both separately and also you have run enough mixes that you will be free being a maker and you will only pay for the last one and also avoid the famous “sudoku” for being taker only once with unmixed coins. On the other hand, /dev/fd0 does understand how joinmarket works and the risks it mitigates so I think #joinstr is a substantial advance and I am sorry that the community is not supporting it enough, one of the main advantages of joinstr over joinmarket is its collaborative nature that makes it cheaper for everyone, there is no extra cost, everyone benefits from the coinjoin and pay the transaction equally. And it is so easy to implement that I can think of thousands of solutions, such as creating automatic pools in the wallets to anonymize by default without user interaction.