[FAQ] how to change coordinator hidden service

[MaxHillebrand]

This adds a quick FAQ about how to change the coordinator onion.

[yahiheb]

Why should we add this to the docs?

[DanGould]

@yahiheb because it answers a question that is asked frequently

[MaxHillebrand]

@yahiheb because Wasabi =/ zkSNACKs.

although this repository ships a package that by default connects to the zkSNACKs coordinator, there are already and will continue to be other coordinators operated. That's a feature, not a bug!!

Users can and will connect to different coordinators, so it ought to be explained how to do it properly, so to not mess up.

[RiccardoMasutti]

@yahiheb because Wasabi =/ zkSNACKs.

although this repository ships a package that by default connects to the zkSNACKs coordinator, there are already and will continue to be other coordinators operated. That's a feature, not a bug!!

Users can and will connect to different coordinators, so it ought to be explained how to do it properly, so to not mess up.

I agree on explaining how to change the coordinator variable, but I believe that the lack of liquidity in the current other coordinators can be a privacy issue and I would advise against most users to change it.

[MaxHillebrand]

yes Riccardo, this is a concern, and notice that's the reason why I do not link to the onion of a different coordinator, as this would be a recommendation, and thus carefully ought to be considered.

Nevertheless, changing the coordinator onion, even if it's for your own setup on regtest, is useful information worthy to be in the docs.

[yahiheb]

Yes Wasabi =! zkSNACKs, but the docs are about Wasabi stuff mainly, so why should we add anything not really related to Wasabi? I mean does Wasabi have any other coordinator that users should manually connect to? AFAIK no, so there is no need for this addition.

@yahiheb because it answers a question that is asked frequently

But that question is not related to Wasabi. Don't get me wrong I am all in for chaincase but I don't think we should add this here just because people want to use Wasabi to connect to chaincase's coordinator.

[MaxHillebrand]

why should we add anything not really related to Wasabi?

Because changing the coordinator is a feature in the Wasabi client.

This is not the zkSNACKs documentation [although it's of course in the zkSNACKs repo, lol], but the Wasabi documentation. And the Wasabi client, is designed in such a way to connect to different than the default coordinator.

imho such a core architecture feature ought to be documented, specifically when there are real use cases for changing it.

I mean does Wasabi have any other coordinator that users should manually connect to?

Yes, for example the mainchain coordinator of chaincase, and I know several users who connect to it with their Wasabi desktop client.

I think it's a reasonable assumption to see in the future new coordinators with unique round parameters.

[RiccardoMasutti]

@MaxHillebrand @yahiheb What if we add a :::warning explaining that by changing the default coordinator, the user expose himself to a series of problems not related to the default coordinator? (eg. low liquidity, less privacy/anonset per round, etc.)

[yahiheb]

Users willing to connect to a different coordinator should really know what they are doing and I guess it won't be difficult for them to know how to do that. Let's close this.