At least 2 separate Haveno networks have launched as of today. One is called Reto and the other is called HardenedSteel. Those are the only ones I'm aware of right now, and things are happening pretty fast.
The haveno software was designed with the assumption that only a single network would be operated. People could fork it and run their own networks, but they wouldn't interact directly at all. But it looks to me as of this moment this is not how it is going to play out.
The client has the network info hard coded. So to use more than one, you need two copies of the client. This means that for most people they have to pick one. And, users might not understand this, just google "haveno" and pull the first git repo they see. This has significant, fast moving and quickly ossifying network effects with big repercussions.
We need to be very vigilant right now, as we are about to witness the very swift rise of a major power broker in our community. We don't want to start using a Haveno network run by scammers or authoritarians. Each network is it's arbitrators, and soon, the merchants on each one.
I think it's probably a good idea to figure out a way to connect to multiple networks, and to show listings with details about which network/arbitrator set a user is trusting when taking up a listing.
I'm cautiously optimistic, Monero has gotten rid of powerful people without a hitch before. But it is a bigger community now and that will be much harder to do. If we are vigilant during this time and we get through this successfully I think we become unbeatable, but the road directly ahead of us is treacherous, the next few days are going to move very fast.
Only thing that really needs to be done would be to put some sort of patch into the client that automatically brings up a dialogue box when the client starts up asking to which network you want to connect or please input an onion seed address.
Edit: That way one executable can cover all networks without having to install multiple instances of the application.
I’m currently working on a pull request that reads the public keys from a file instead of being hard coded. Distributing those files with a custom haveno.properties file could allow people to join separate networks using the same codebase unless there is some functional difference