Skip to content

Joining the beta network

Testing is currently ongoing on the beta network for Version 21

Read through this page if you would like to participate, and find the currently selected test cases at the end.

A few common reasons for joining the beta network include:

  • Learning node setup and management
  • Testing out integrations for services build on Nano before running on the main network
  • Assisting in testing new node releases and features
  • Contributing to a network testing various behaviors and patterns with the protocol

Running a beta node is a great way to join in and help the network grow stronger.

Differences from the main network

Parameter Main Network Beta Network Comment
Proof of Work Difficulty Threshold 0xffffffc000000000 0xfffff00000000000 64 times lower on the beta network

Node release testing

The beta network is also used to coordinate the testing of Nano node releases. The Nano Foundation maintains a few beta nodes on the network and various community members also setup nodes to help provide an environment more similar to the main network. Ahead of each release builds are published as Release Candidates (RC). Starting with RC1 and incrementing with each published build (RC2, RC3, etc.), these are intended for use on the beta network to help identify issues not discovered earlier in the development process.

We invite anyone interested in contributing to Nano to consider participating on the beta network. Not only is it beneficial to the ecosystem, it is also a great way to learn more about setting up and managing a node.


  • Release candidate builds are only recommended for use on the beta network
  • The fastest and most recommended method of installation is through Docker
  • Binaries and other details can be found at:

Running a beta node

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

Network ports

Beta Network Ports Overview

  • 54000 UDP: For live network activity (fallback since V19.0)
  • 54000 TCP: For live network activity (since V19.0) and bootstrap network activity
  • 55000 TCP: For communication with RPC server. Anyone with access to this port can control your node's RPC.
  • 57000 TCP: For communication with websocket server. Depending on configuration, data throughput can be very high.

UDP disabled by default, deprecated

As of V21 peering and communicating via UDP has been disabled by default and is deprecated. The ability to use UDP will be removed from the node in a future release yet to be determined.

Folder locations

OS Location
Windows C:\Users\<user>\AppData\Local\NanoBeta\
macOS /Users/<user>/Library/NanoBeta/
Linux /home/<user>/NanoBeta/


Directory names for extracting builds downloaded from GitHub or will be updated with RC versions for V19 and later.

Pulling the Docker image

Docker Pulls

Pulls the latest release of the Nano Node:

docker pull nanocurrency/nano-beta

Pulls a specific version of the Nano node:

docker pull nanocurrency/nano-beta:V19.0RC1

Pulls the latest release which includes any release candidate versions:

docker pull nanocurrency/nano-beta:latest-including-rc

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

Starting the Docker container

docker run --restart=unless-stopped -d \
  -p 54000:54000/udp \
  -p 54000:54000 \
  -p [::1]:55000:55000 \
  -p [::1]:57000:57000 \
  -v ${NANO_HOST_FOLDER_BETA}:/root \
  --name ${NANO_NAME} \


Separate host folders

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

Additional beta resources

URL Description Official beta site and faucet Beta Explorer Beta nodes and Stats

Testing Builds

Release Candidate Builds

During Release Candidate periods the latest build on the GitHub repository Releases page will be tagged with an RC number. Various binaries are available below the changelog there for download (Windows, Linux, macOS, etc.). If building on your own, use the latest tags containing RC.

Additional details for services who wish to test their integrations on the beta network for proper migration between releases can be found in the Release Notes area.

Development Builds

Links for beta testing builds are shared in the #beta_announcements channel on our Discord server. Docker tags are also available on

Ongoing Test Cases

A spreadsheet of some test cases is maintained separately and available for sharing with community members who are involved on the beta network. If you are interested in helping with these test cases, please connect with Zach - ATX#0646 or Dotcom#9351 in the #beta-net channel on our Discord server.