The smartphone doesn't claim to be the ultimate solution for Bitcoin privacy, though.
That's what I meant when I highlighted 2 examples of 'expectation vs reality'.
That is probably your imagined expectation because I can't find anywhere on their website information claiming they are ultimate solution for Bitcoin privacy.
I'm not sure where they first mentioned '
ultimate solution for Bitcoin privacy', but I have confirmation in their reply to my 10th question:
[...]
Such statements make it appear like you believe yours is the only privacy solution and that there is no privacy in Bitcoin without Wasabi. Would you confirm this? Actually, later you admit that LN has better privacy, so this already seems like a contradiction.
Answer: We sincerely see WabiSabi as the best on-chain privacy technology in bitcoin today[emphasis mine]. We are aware of various other projects but in all honesty, they are shooting very low. Once you understand WabiSabi, you’ll see why we think it’s on a completely different level. Lightning is nice but not for on-chain privacy.
So, in this case a screenshot from Wasabi saying the CoinJoin was denied or what?
I am not sure how this works exactly, all I know is when I tried to do coinjoin in Wasabi V2 few months ago it was not working for some unknown reason.
Anyway, I think we can put some presure on Trezor developers to start new coijoin coordinator or use something different for mixing.
I see! I haven't tried it myself, but it would be interesting to know whether blacklisted inputs are marked as such / if there's any GUI for it or whether users just get a (presumably) generic error message. In that case, your experiment may even have been the first case of Wasabi blacklisting reported on the forum.