2024 06 State of the Testnet

Nomos testnet is deployed and publicly available at http://testnet.nomos.tech (Notice the http, not https).

Testnet uses master branch to build docker images. Images are rebuilt and docker-compose restarted after a new commit in the master branch.

The testnet consists of 4 Nomos nodes. Nodes are assigned predefined identifier that are used across the node configuration.

Before starting the nodes, containers announce their ip addresses and other configuration parameters via etcd. Ideally this step will be removed in the future once the node is able to configure the consensus, DA and network parameters dynamically or using bootstrap nodes.

After the configuration, nodes are started and accessible via these ports on http://testnet.nomos.tech:

3000/tcp # Bootstrap libp2p
3001/tcp # Libp2p-node-1 libp2p
3002/tcp # Libp2p-node-2 libp2p
3003/tcp # Libp2p-node-3 libp2p

18080/tcp # Bootstrap http api
18081/tcp # Libp2p-node-1 http api
18082/tcp # Libp2p-node-2 http api
18083/tcp # Libp2p-node-3 http api

7707/tcp # Mix-node-0 client
7717/tcp # Mix-node-1 client
7727/tcp # Mix-node-2 client

7708/tcp # Mix-node-0 listener
7718/tcp # Mix-node-1 listener
7728/tcp # Mix-node-2 listener

Example endpoint to see if the testnet is accessible:

curl -v <http://testnet.nomos.tech:18081/cryptarchia/info>

*   Trying 65.109.51.37:18081...
* Connected to testnet.nomos.tech (65.109.51.37) port 18081
> GET /cryptarchia/info HTTP/1.1
> Host: testnet.nomos.tech:18081
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< content-type: application/json
< content-length: 102
< date: Mon, 03 Jun 2024 12:54:36 GMT
<
* Connection #0 to host testnet.nomos.tech left intact
{"tip":"6de1135f096734e52e3480f7e379e855d27c699e07b70c1447d8eb58ecb61bd3","slot":71323,"height":39249}

Host Machine

More information about host machine and configuration can be found here: https://github.com/status-im/infra-misc/issues/189

Hetzner AX41-NVMe

Iteration 4 Notes

• Setup testnet infrastructure
  • Docker Compose is used to define the required services
    • I would argue to leave this setup as it is because it’s accessible and convenient for non-devops people to run it locally or change the configuration if new features are added.
  • A host machine for running the testnet is deployed
    • Having one robust machine to run multiple containers allows a simple setup for running a larger number of nodes. As we aim to have a lightweight node, the current host should be able to run 100+ Nomos nodes.
    • If needed, we’ll be able to augment this setup with other host/edge machines running either single or smaller batches of Nomos nodes.
  • The testnet runs the master branch and is restarted after changes in that branch
    • To better coordinate what is running on testnet.nomos.tech, we are planning to have a dedicated branch in the repository, called testnet.
  • Node configurations are prepared using etcd before launch
    • To compensate for some missing features in the node, etcd is used. At the moment, it configures the consensus and network before launching the node.
• Setup a 100 nodes network
  • 4 nodes are currently configured to be spawned in the testnet
    • While we could start working on making sure that the number of nodes can be easily adjusted, I don’t see much value of having a big testnet without a proper debug instrumentation.
    • I’d postpone this step and use current 4 nodes until basic instrumentation is added.