> There is no coin control in Wasabi Wallet 2.
This is correct, but in and of itself can be misleading for those who know that privacy in Bitcoin is near impossible without coin control, because the conclusion would be then that Wasabi 2.0 ruined privacy for no reason, which is obviously not the case, in fact it improves it in many ways.
The idea is that you don't need coin control when you can make your transaction with coinjoined coins. These coins are indistinguishable, so you don't really have a use for coin control in that case. I think this is non-controversial, but what about the case when you cannot make the tx from coinjoined coins?
In that case there still is a mandatory privacy control, which is an improved version of coin control. The insight here is that, in coin control settings, users are differentiating between coins based on their labels. Since Wasabi creates label clusters, it is ok to select the clusters the user wants to make the transaction from instead of individual coins. I know you liked the never released cluster selection page before it got further improved to be a privacy control page, but note the privacy control still uses the same insight, it just further removed unnecessary friction. That being said, coins can also be seen with this super secret developer key combination: CTRL + D + C
> User does not select coins because they are never shared with the user in the first place.
As explained above it is selecting coins indirectly rather than directly. It is selecting clusters of coins that are assumed to belong to the same wallet from an outside observer's point of view instead of individually selecting coins one by one.
>
There are no 'private' coins. Every coin is public in Bitcoin.
Not sure I'd like to engage in bikeshedding on terminology, but in my opinion this terminology is not only true, but also good and useful: Ownership of equalized coinjoin UTXOs is only known by the owner and not by external observers. The owner has control over who it reveals the ownership of these UTXOs. Privacy is your ability to selectively reveal yourself to the world, therefore the terminology of "private coins" naturally makes sense and it's a useful differentiator from non-coinjoined coins.
>
Since, the wallet assumes some coins as 'private' based on certain things it can be misleading for the user. Privacy depends on the things users want to share with others.
The wallet does not assume. The user assumes when selecting the anonymity levels. The wallet works with the user's assumption of its threat model. If a misleading claim can be made here then it's that the user misleads the wallet (and her/himself) rather than the other way around.
>
Privacy involved in using a change or not using it is debatable. Not using a change address makes it easier to understand who might be the recipient in a transaction whereas using a change address same as other outputs would be difficult to analyze for possible recipients.
Although I agree it's debatable, but for different reasons. I'd rather take an issue of its usefulness instead. About the assumption that it's easier to understand who might be the recipient, that's incorrect as the transaction can easily be considered a self spend. In comparison to change generating transactions, there the change and the recipient can most of the times be established.
>
Wasabi wallet does not have different types of addresses to use for a change however [Bitcoin Core][2] recently made some related improvement which would improve privacy.
Yup. Unfortunately this is a hack to make the wallet feel like a light wallet as it greatly reduces the size of the client side filters we have. Although, as the blockchain grows further optimizations are needed. So it's not very helpful if Bitcoin Core gives us 10 GB of filters so we can use all the types of addresses. We had a pull request to Core about creating custom filters, but it was NACK-ed. In order to do this correctly and get merged into Core we'd have to have a more comprehensive modification than our initial PR and that we have no resources to allocate to yet.
>
As far as issues are concerned, there are several things not fixed and shared in different GitHub issues or discussions. These include privacy, security and other things.
I greatly disagree with this assessment, in fact, quite the opposite. Take for example the tremendous activity your pull request about an empty catch block received:
https://github.com/zkSNACKs/WalletWasabi/pull/6791No sane project would allow their best developers to spend more than 5 minutes on this issue, yet 7 developers were discussing if leaving a single empty catch block in the code could be a potential security risk in the future and our resolution was actually contributing to NBitcoin to make sure we aren't getting an exception for incorrect password, but rather a boolean signal.
>
As WW2 is not developed for power users (mentioned by developers working on Wasabi), I am not sure if bitcoin dev mailing list would be the best place to look for newbies.
I do agree that the bitcoin-dev mailing list is not where the target users of Wasabi 2.0 are to be found, however Wasabi 2.0 is a great forward step of Bitcoin development and developers could certainly benefit from knowing about great innovations it comes with.