Use case

Your own bootstrap node.

A new peer needs a first address to join the network. By default the libraries use the two public entry nodes that Ciranda runs, free, with no uptime guarantee while Kolo is a beta. For a network of your own, you run a few kolo-node servers on machines of yours and give their addresses to your peers; the public ones are then not used.

The pieces

The libraries this needs. Each has install steps and a compiled example in its docs.

How it goes

  1. One binary, one port

    kolo-node runs a kolo-dht server on one UDP port. It answers queries, stores signed announcements and relays connect requests. It carries no application data.

  2. Keep its key

    The node keeps its kolo-id key in a file it creates on the first run with mode 0600, and keeps the same key across restarts.

  3. Run a few of them

    Run a few on different hosts with a public IPv4 address and list them in each other's config. The docs have the systemd setup for a Linux VPS.

Good to know

The node sees which addresses announce and look up a topic; DHT traffic is not encrypted. Anyone can announce any topic. A node is a server you run and pay for, but your peers' data never goes through it.

Next