Different networks are active.

EnvironmentDescriptionManaged byGenesis Block
betanetNetwork which will receive live traffic and will evolve into live production networkToken HoldersNJV4Y2MEVZSZSYCTMORA53ZUB6SRTYE2VW6IB3GT3DLG3TJK3V5A
testnetOnline testnet which can break due to developer changesAttrace Team6PYHXBHFOTQZ3GE6JQRA2OYDCU6WTLHLF3JID6JZI6TRKUMWEYPQ
devnetDevelopment network developers run locally during developmentDevelopersee code

Discovery manifest#

When booting a new node, it's required to give the node some hints how to discover the network. It needs at least a single witness to start discovery.

When you use any of the clients, by default they will discover the requested network by querying for a manifest.
The Attrace Project, hosts an up-to-date witness manifest for every network. It refreshes every 15 minutes.

This is the url pattern for the manifest:{{ network }}/manifest.json


curl -s | jq
"SnapshotTime": 1578953766399,
"Witnesses": [
"ApiPort": 0,
"Host": "",
"Port": 443,
"Signature": "ZVBJ2mo797W9xcfNPLNJ/3nctVJ6jzwYShluBWTW0H7CN8NKxSNuxb7mlhJyeSgsCqXZkbz523cEqpuUQvD7CA==",
"Time": 1578953673105

Custom manifest#

If you prefer your run your own public node, or want to use a custom manifest, you can always pass in --discovery-manifest=URL on all executables.

Every public node exposes the manifest on GET /api/v1/manifests/network.

Example request:

curl 'https://YOURNODE/api/v1/manifests/network' | jq

Custom seeds#

If you don't want to use a manifest, you can also use --seeds=host:port,,... to discover from specific hosts.