๐ปRunning a Full Node
This is a detailed documentation for setting up a Full node on HeliChain.
REMARKS:
The following is the minimal setup to join HeliChain. If running a validator node, you should research validator security.
Prerequisitesโ
Go 1.18+
GCC/G++ compiler
Supported OSโ
We officially support Linux only. Other platforms may work, but there is no guarantee. We will extend our support to other platforms after we have stabilized our current architecture.
Commonly used portsโ
helichaind
uses the following TCP ports. Toggle their settings to fit your environment.
26656: The default port for the P2P protocol. This port is used to communicate with other nodes and must be open to join a network. However, it does not have to be open to the public. For validator nodes, we recommend configuring
persistent_peers
and closing this port to the public.
Additional ports:
1317: The default port for the Lite Client Daemon (LCD), which can be executed by
helichaind rest-server
. The LCD provides an HTTP RESTful API layer to allow applications and services to interact with yourhelichaind instance
through RPC. You donโt need to open this port unless you have use for it.26657: The default port for the
Tendermint RPC protocol
. Because this port is used for querying and sending transactions, it must be open for serving queries fromhelichaind
.
Networks informationโ
Specify the network details for the network you want to participate in by selecting the corresponding genesis file and seeds.
Setup a full-nodeโ
This guide completes the following actions:
Download the latest release corresponding to the chosen network from Helichaind repository
Compile
helichaind
Give your node a moniker and configure it
Configure genesis state
Example:
Start your full-node:
FOR OPTIMIZED NODE PERFORMANCE, SET minimum-gas-prices
TO ENABLE THE ANTI-SPAM MECHANISM AND REJECT INCOMING TRANSACTIONS WITH LESS THAN THE MINIMUM GAS PRICES.
After starting your full-node, wait until it completely sync transactions to your local to start create your validator.
Optional Configuration: State Syncโ
State sync rapidly bootstraps a new node by discovering, fetching, and restoring a state machine snapshot from peers instead of fetching and replaying historical blocks
Visit a explorer to get a recent block height and corresponding hash. The recommended snapshot period is 1000 blocks, it is advised to choose something close to current height - 1000.
Set these parameters in the code snippet below <block_height>, <block_hash>, <rpc_server>
Optional Configuration: Change RPC port
Last updated