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. If you plan to consistently run a node on beta and want to participate in consensus as a Representative, please connect with argakiig#1783 in the #beta-net channel on our Discord server.
For small amounts suitable for most basic integration, you can get beta Nano from the #beta-faucet channel on Discord. 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. 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. 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. As much of the discussion, planning and engagement happens here, all participants are highly encouraged to join there. Most of the resources needed to participate on the beta network can be found within the #beta-xxxxxxx channels on our Discord server. Additional beta resources ¶ URLĭifferences from the main network ¶ Parameter Attempting to use the same directory will result in issues. Pulls the latest release of the Nano Node:īe sure to use a different host directory for main network and beta network Docker node setups. Depending on configuration, data throughput can be very high.Īs defined by the -v flag in the docker run command See IPC integration guide for more details.įor communication with websocket server. Anyone with access to this port can control your node's RPC.įor communication via IPC (advanced).
Do not expose this outside of your production environment. Network ports ¶ Portįor live network activity and bootstrap network activity.įor communication with RPC server.
#DOCKER FOR MAC BETA CHANNEL INSTALL#
To start you should install docker and be familiar with the general setup and Docker management processes. Setting up a node on the beta network is similar to the main network.
Final release of a version typically follows quickly once the RC is observed to be stable.ĭevelopment Builds (DBs) are only recommended for use on the beta network, and Release Candidate builds (RCs) are only recommended for use on the test and beta networks Running a beta node ¶ Starting with RC1 and incrementing with each published build if needed (RC2, RC3, etc.). Once features are stabilized and included, release builds are published as Release Candidates (RC). During each development cycle Development Builds (DB) are prepared and shared in the Discord Beta Testing section of channels where early testing is coordinated. 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. With those things in consideration, if you are interested in helping with testing on the beta network we are excited to help you out - so keep reading! Node release testing ¶ As a result, an alternative test network is also available which will be more stable and is a better fit for learning node setup and management, and testing out upgrades and other activities for Nano before moving to production. These activities can cause the network to become unstable or inaccessible at times due to heavy traffic, occasional resetting of the genesis/ledger or the introduction of bugs due to new features. The beta network exists for the purpose of conducting certain network-wide activites including load testing and new node releases and features testing.
0 kommentar(er)
