A geographically sorted list of public peering credentials for joining Hyperboria
jaythespacehound bdf66a6487 deleted: hype.jazzanet.com.k (#143) 1 month ago
af/ng/lagos added peer in lagos (#87) 1 year ago
as/jp Removing @belovachap's dead servers. (#141) 1 month ago
eu deleted: hype.jazzanet.com.k (#143) 1 month ago
na Removing @belovachap's dead servers. (#141) 1 month ago
.gitignore bump package.json because of readme 2 years ago
.travis.yml Use new build system (followed old docs before) 2 years ago
README.md Some tags requiring location (#92) 10 months ago
index.js serialize pub location along with peering data 1 year ago
package.json bump version 1 month ago
tests.js make peerName required in js 6 months ago
tests.py Make peerName a required field (#118) 6 months ago


Build Status

A geographically sorted list of public peering credentials for joining Hyperboria.

Hyperboria uses cjdns to construct an end-to-end-encrypted ipv6 mesh network. Connections between nodes are established manually, and traffic is restricted to the resulting social graph.

This repository exists for those who don't already know somebody on Hyperboria.

Using credentials

First, set up a cjdns node.

To connect your node to one of these public peers, follow the steps in the cjdns README.

Adding your public node's credentials

If you've created a public node, and would like to have it listed here, fork the repo, add a keyfile, and submit a PR.

Filepath conventions

Credentials are sorted geographically, by continent code. Nodes may be classified further, at the discretion of the node operator, and the administrators of the repository.

The suggested format is /continent/country/region/municipality. For example, /na/ca/ontario/toronto/.

Region and municipality codes are based on self identification, not any ISO standard. An operator might prefer to list their node in Cascadia instead of Washington state. For simplicity's sake, we'd prefer that new credentials conform to existing structures.

JSON formatting

We have tried to standardize the structure of the actual credential files, as such, they have the strictest requirements of anything in this repository.

  • Your credentials must be valid JSON.
  • They must contain the necessary fields:
    • ip/port
    • password
    • publicKey
    • contact (a means of contacting the operator)
  • The following fields are not yet required, but are recommended:
    • gpg, listing your 16 character pgp fingerprint (all caps, no spaces)
    • peerName, a human-readable name for the node
  • credentials should be formatted such that:
    • indentation uses four spaces
    • the file ends with a newline character.
  • credentials must use IP:port strings for keys
    • credentials using hostnames will not be accepted
  • If you are hosting it on a major server provider, please provide the name and shorthand for server.

    • On digitalocean, That may be digitalocean sfo2
    • On linode, that may be linode uswest or linode tokyo2
    • On AWS, use the region, followed by the city. Usable Server names are listed can be found on found on the AWS WEBSITE

    EX: useastnorthernvirginia,useastohio,southamericasaopaulo


Naming your entry

Credential files must end with .k. Otherwise, you can name your file whatever you want, but for simplicity's sake, avoid characters which will need to be escaped at the command line (or within the javascript api).

Javascript API

Peering credentials in this repository can be accessed via a simple Javascript API (using Nodejs).

It's available as a module on npm:

npm install hyperboria-peers


var Peers = require("hyperboria-peers");

/*  return a list of public peers located in North America */
Peers.filter(function (creds, path) {
    return path.indexOf('NA') !== -1;

/*  return a list of public keys */
Peers.map(function (creds, path) {
    return creds[Object.keys(creds)[0]].publicKey;

/*  the underlying data is exposed in a nested json structure */