Join the NEW Community Test Network (Running Now): "community1"

Development
188

I have started a new community network, called “community1”, but it is just sitting there listening. :slight_smile:

Please copy this into your vaults’ and launchers’ configs, and restart. No command-line options necessary. I’m guessing that that is all that’s needed (or not, lol).

Vaults behind NAT should be fine with the latest hole-punching, but anyone who has a vault in the cloud, connecting directly to community1, feel free to send me your IP and I’ll add it:

{
  "hard_coded_contacts": [
    {
      "tcp_acceptors": [
        "91.121.173.204:5483"
      ],
      "tcp_mapper_servers": []
    }
  ],
  "tcp_acceptor_port": 5483,
  "service_discovery_port": null,
  "bootstrap_cache_name": null,
  "tcp_mapper_servers": [],
  "network_name": "community1"
}

I still have a Test 3 vault running on the same Ip and listening on the same port. I don’t know if that will cause conflict. I hope that each vault will simply reject messages intended for the other’s network, until I take the first one down.

Until it builds up a routing table, launchers won’t be able to connect.

I ran it with the --first option, still just listening.

WHOA, it is connecting (to one other vault)! Taking the Test 3 vault down and adding the --first flag did it.

Just to reiterate: don’t use the --first flag, because there can only be one seed. Just replace your config and that’s it.

Two new entries in the routing table!

Don’t forget to use the current distributables. The earlier versions are rejected. the current ones are here:

SAFE Vault binaries
SAFE Launcher binaries
SAFE Demonstration Application binaries

There are seven entries now. Could someone run a launcher and see if they connect?

4 Likes