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.

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. During each development cycle Development Builds (DB) are prepared and shared in the Discord Beta Testing section of channels where early testing is coordinated. Once features are stabilized and included, release builds are published as Release Candidates (RC). Starting with RC1 and incrementing with each published build if needed (RC2, RC3, etc.). Final release of a version typically follows quickly once the RC is observed to be stable.

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.

Directory locations

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

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:V21.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_DIR_BETA}:/root \
  --name ${NANO_NAME} \


Separate host directories

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

Additional beta resources

URL Description Nano Foundation beta site and faucet Beta Explorer Beta node details and stats Beta node details and stats

Differences from the main network

Parameter Main Network Beta Network Comment
Epoch 1 difficulty threshold ffffffc000000000 fffff00000000000 64 times lower on the beta network
Epoch 2 send/change threshold fffffff800000000 fffff00000000000 2 times higher than epoch 1
Epoch 2 receive threshold fffffe0000000000 ffffe00000000000 2 times lower than epoch 1

Testing Builds

In addition to the Docker details above, the latest binary builds of the node for the beta network are shared in the #beta_announcements channel on our Discord server and updated below for easy reference. These assets are also available on the GitHub repository Releases page under RC# and DB# tags, which can also be used to manually build if necessary.

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.

Latest Beta Builds

OS Version Download link/command
Linux V21.0RC1
macOS V21.0RC1
Windows V21.0RC1
Docker V21.0RC1 docker pull nanocurrency/nano-beta:V21.0RC1 or docker pull nanocurrency/nano-beta:latest
See Pulling the Docker Image for more details.

Beta fund distribution

The funds used for testing transactions on the beta network are generated from a new genesis block and distributed in bulk to various testers running nodes on the network. Given the large number of transactions done during testing the ledger can grow quite large and will be restarted from scratch between releases and/or as needed. As a result, previously distributed beta Nano are no longer useful and need to be redistributed again.

For small amounts suitable for most basic integration, you can get beta Nano from the beta faucet here: If you plan to consistently run a node on beta and want to participate in consensus as a Representative, please connect with Zach - ATX#0646 or Dotcom#9351 in the #beta-net channel on our Discord server.

Beta ledger file

To help get beta nodes in sync more quickly it is recommended that an updated ledger file is downloaded and placed into the data directory. Often referred to as a "fast sync", more details around this approach can be found in the Ledger Management guide. Since the beta network contains no value, validating the blocks, voting weights and confirmation heights isn't necessary.

The following command will download and unzip a recent ledger snapshot. Any existing ledger files should be backed up elswhere as this will override them. From within the data directory run:

curl -O; tar -xzvf data.tar.gz; rm -fr data.tar.gz

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.