It is true, however, that if a coordinator has more liquidity than Ginger, and is completely free, then I don't see how Ginger competes.
There are several ways Ginger Wallet cannot compete with some coordinators but considering Ginger Wallet is effectively a business and they make their income from selling coinjoin services, it stands to reason they would want to stop/block people from using their
star product with a third party coordinators (and in the process effectively cutting them out of their 0.3% fee).
If there are some exceptional technical advances in their next release, it might appease some of the negative sentiments surrounding their wallet.
It seems that it was a mistake on our side and previously only the backend was fixed to our servers. We never intended to allow other coordinators than the Ginger one from the beginning. Apologies for the misunderstanding.
That is interesting to read, thank you for clarifying. You do realise you would like Wasabi Wallet users to change their coordinator to Ginger Wallet therefore why do you not want to reciprocate the same for Ginger Wallet users?
No, we would like to ask the users to use the Ginger Wallet instead of the Wasabi Wallet if they want to use the Ginger coordinator.
You seem to have the assumption that the two coordinator is totally compatible with both wallet clients, but that's not true.
Short history from the recent releases.
- With the release of Wasabi Wallet v2.0.8.1 (2024-06-08), the maximum coinjoin coordination fee was introduced.
The default was set that all non-free coordinators stopped to work, even if the current one was a non-free one. Also, unfortunately the users didn't understand the error messages and what needs to be done.
- With the release of Wasabi Wallet v2.1.0.0 (2024-07-10), the following changes applied:
The coordinator minimum input count must be at least 21. At that time the malicious coordinator ran with 1 or 2 minimum inputs; all other, but Kruw's coordinator ran with 20 minimum inputs.
All, but Kruw's coordinators instantly failed after a client update (free and non-free).
The maximum fee was set to 0.5% (this might hit the wasabist.io's random fee system, I don't remember). Note, that there was a plan to set it to 0.01%, that's literally generating dust.
Not mentioned downgrade: the fee exemption check was removed, so the Wasabi client asked LESS amount for their input even if they got exemption from the coordinator due to remix.
After this release all other fee based coordinator died as they weren't able to manage the changes on the coordinator side.
- With the release of Wasabi Wallet v2.2.0.0 (2024-09-19), our coordinator is effectively banned by the Wasabi client.
The Ginger coordinator worked with the Wasabi clients till now, because of constant code and setup updates.
On the other hand, you have to understand the Wasabi developers and their goal:
They have limited time to make the Wasabi project "truly" open source.
That means heavy simplification, removing the less used and not needed features (of course they won't advertise it in the release notes, but who would?).
They could have fix the remix issue, but there is no incentive to do so (as they won't get any money from it) and increases the complexity, instead they removed the whole fee concept.
For the same reason they removed the AML system, increases the complexity and it's not their risk to run the coordinator anymore (also there would be no fund to use it anyway due to the above line).
The execution wasn't necessarily nice, but their goal is quite understandable.
They were fair, and told their plan in advance (even if there were some timeline change from 6 months to 3.5 months), so we knew from the beginning that a fork is needed.
Thank you for your understanding.
