This provides a streamlined experience for users by ensuring secure and seamless communication with a trusted entity.
Certainly, but isn't the primary appeal of the coinJoin protocol that it's trustless-- that it doesn't require trust in the coordinator to function? Or do you believe there's still some risk involved in choosing a random coordinator for coinjoin?
There's been extensive discussion on this topic, and it would be valuable to read your perspective on it as well.
There seems to be some misunderstanding regarding the topic of trustlessness in the WabiSabi protocol. To clarify, we were not addressing the protocol's trustlessness, as both GingerWallet and Wasabi take this aspect very seriously. Both teams actively research and collaborate whenever a new vulnerability is discovered, ensuring that WabiSabi-based software remains secure. Over the past months, significant improvements have been implemented in both GingerWallet and Wasabi to enhance protocol security.
The Ginger and Wasabi teams remain in contact, alongside BTCPay Server, to share insights and address any issues that arise. If you discover a new vulnerability, we encourage you to report it privately through GitHub's "Privately reporting a security vulnerability" feature. Rest assured, such reports are promptly investigated and resolved across all WabiSabi-based clients as needed.
Our previous response was about the legal risks and responsibilities associated with operating a coordinator, not the trustlessness of the protocol. Historically, zkSNACKs ceased operating its coordinator due to legal risks that were deemed too high. Following this, Wasabi removed its default coordinator and enabled users to select their own, which was a thoughtful and prudent decision to manage risk and protect its developers. For more details, we recommend exploring Wasabi's blog or engaging directly on their forum.
At GingerWallet, we approached this challenge differently. Allowing users to configure their own coordinator in GingerWallet would have exposed us to similar legal risks, which is why we chose to maintain a single default coordinator. This approach allows us to take full responsibility for its operation and maintain a streamlined user experience.
From a technical standpoint, Wasabi and GingerWallet are no longer compatible. Wasabi introduced changes, such as removing the coordinator fee, that broke compatibility with the GingerWallet coordinator. Consequently, GingerWallet cannot connect to Wasabi's protocol, and Wasabi cannot connect to Ginger's coordinator.
We hope this explanation provides clarity and context regarding the differences between the two software approaches. If you have further questions, feel free to reach out!