Skip to content

Test network

The test network exists primarily for the purpose of conducting general integration and node upgrade testing in light volumes. By providing a network with similar parameters to the main network (work difficulty, etc.) this is the best environment for connecting test or staging versions of services and applications to for small scale tests. In order to keep the network as stable as possible, the Nano Foundation will maintain nodes on this network on the latest Release Candidate (RC) or release version, it will not be updated with beta or development features.

For load testing and new node releases and features testing, head over to the beta network page where details on how to conduct those types of network-wide testing exist.

Running a test node

Setting up a node on the test network is similar to the beta network. To start you should install docker and be familiar with the general setup and Docker management processes.

Network ports

Port Protocol Required? Purpose
17075 TCP Yes, open to all traffic For live network activity and bootstrap network activity.
17076 TCP No, recommended For communication with RPC server. Do not expose this outside of your production environment. Anyone with access to this port can control your node's RPC.
17077 TCP No, optional For communication via IPC (advanced). See IPC integration guide for more details.
17078 TCP No, optional For communication with websocket server. Depending on configuration, data throughput can be very high.

Directory locations

OS Location
Windows C:\Users\<user>\AppData\Local\NanoTest\
macOS /Users/<user>/Library/NanoTest/
Linux /home/<user>/NanoTest/
Docker As defined by the -v flag in the docker run command

Binaries

In addition to the Docker details above, the latest binary builds of the node for the test network can be found below. These will only change when Release Candidates (RC) builds are ready, or when final releases are done. However, the first build available today is actually a development build since the changes to enable this network were recently introduced.

OS Download link/command
Universal Linux https://repo.nano.org/test/binaries/nano-node-V22.1-Linux.tar.bz2
Debian https://repo.nano.org/test/binaries/nano-node-V22.1-Linux.deb
macOS https://repo.nano.org/test/binaries/nano-node-V22.1-Darwin.dmg
Windows (exe) https://repo.nano.org/test/binaries/nano-node-V22.1-win64.exe
Windows (zip) https://repo.nano.org/test/binaries/nano-node-V22.1-win64.zip
Docker docker pull nanocurrency/nano-test:V22.1
RHEL/CentOS rpm Not available for the test network

If manual builds are needed, see the build options page for details.

Pulling the Docker image

Docker Pulls

Pulls the latest test release of the nano Node:

docker pull nanocurrency/nano-test

Pulls a specific test version of the nano node:

docker pull nanocurrency/nano-test:<tag>

A list of test tags can be found at the official Nano Currency Docker Hub

Starting the Docker container

docker run --restart=unless-stopped -d \
  -p 17075:17075 \
  -p [::1]:17076:17076 \ # (1)
  -p [::1]:17078:17078 \ # (2)
  -v ${NANO_HOST_DIR}:/root \
  --name ${NANO_NAME} \
  nanocurrency/nano-test:${NANO_TAG}
  1. Port 17076 is optional, but recommended, for querying via RPC
  2. Port 17078 is optional for connecting via WebSockets

Tip

Separate host directories

Be sure to use a different host directory for main network, beta network and test network Docker node setups. Attempting to use the same directory will result in issues.

Getting test funds

One you have a node up and running the ledger should bootstrap from the network quickly, and then you just need some test network specific Nano funds. We are currently working on a faucet setup to enable self-service options, but for now please reach out to argakiig#1783 on Discord or email infrastructure@nano.org with the account number you would like funds distributed to for the test network.

Back to top