Join the Network

This tutorial introduces deploying a new node on AWS and join the Panacea Mainnet.

Launch an AWS EC2 Instance

Choose an AMI

Choose Ubuntu Server 20.04 LTS 64-bit (x86) with SSD Volume Type.

Choose the instance type

Choose the m5.large instance type (minimum spec).

Configure instance details



Choose an existing VPC or default one if you don't have any


Choose an existing subnet or default one if you don't have any

Auto-assign Public IP

Enable only if you access a full node from the outside of its VPC

Other fields

Follow default settings

Add a storage



500 GiB

Volume Type

General Purpose SSD (gp3)




125 MB/s

Configure a Security Group

TypeProtocolPort rangeDescription




Custom TCP



P2P with other nodes

Custom TCP




Custom TCP




The P2P 26656 port must be exposed to other Panacea nodes. If your node will be in the VPC guarded by Sentry nodes, expose 26656 to only Sentry nodes (recommended). If not, expose it to anywhere. For details about Sentry nodes, please see the Tendermint guide.

The RPC 26657 and HTTP 1317 ports are for sending transactions/queries to your node. So, expose them to the network where you perform operational actions.

Connect to your EC2 instance and install prerequisites.

ssh ubuntu@<your-ec2-ip> -i <your-key>.pem

Install prerequisites by following the Installation guide.

Setup a New Node

These instructions are for setting up a brand new full node from scratch.

First, initialize the node and create the necessary config files:

panacead init <your_custom_moniker>

The moniker can contains only ASCII characters. Using Unicode characters will render your node unreachable.

Then, modify the timeout_commit in the ~/.panacead/config/config.toml as below.


timeout_commit = "5s"

After that, edit the ~/.panacead/config/app.toml file in order to enable the anti-spam mechanism and reject incoming transactions with less than the minimum-gas-prices:

# Validators reject any tx from the mempool with less than the minimum-gas-prices.
minimum-gas-prices = "5umed"

# NOTE: For the Testnet, please set minimum-gas-prices as "", so that no fee is required.

Now, your full node has been initialized!

Copy the Genesis file

Fetch the genesis.json file of the latest chain from the following links, and place it to ~/.panacead/config/genesis.json.

  • Mainnet:

  • Testnet:

Configure Seed Nodes

Your node needs to know how to find peers.

Seed nodes can be found in:

  • Mainnet:

  • Testnet:

Insert those <node_id>@<ip>s with 26656 port to the persistent_peers field in ~/.panacead/config/config.toml.

# Comma separated list of nodes to keep persistent connections to
persistent_peers = "c238f279c970764d6893ae44bdf5c949dc22b009@,395aead00e99f828e4af92531dcd8c8da1255a8f@,00c57e36559b49ce7d29fa4920b5132584994368@"

For more information on seeds and peers, see the Using Tendermint: Peers.

State Sync

Your node can rapidly sync with the network using state sync without replaying historical blocks. For more details, please refer to this.

To set state sync enabled, RPC servers and trusted block info (height and hash) are required.

trusted block info can be obtained via RPC.

curl -s | jq -r '.result.block.header.height + "\n" + .result.block_id.hash'
# 7700000 (height)
# 0D3E53F02ABCDDA8AAC1520342D37A290DDABE4C28190EE6E2C6B0C819F74D4A (hash)

Then, you need to edit several things in ~/.panacea/config/config.toml file.


enable = true

rpc_servers = "," # rpc addresses
trust_height = <trusted-block-height>
trust_hash = "<trusted-block-hash>"
trust_period = "336h0m0s" # 2/3 of 21 days (unbonding period)

If your node have block history data previously synced, you need to clear the data first.

panacead tendermint unsafe-reset-all

Run a Full Node

Start the full node with this command:

panacead start

Check that everything is running smoothly:

panacead status

View the status of the network with the Block Explorer

  • Mainnet:

  • Testnet:

Join as a validator

If you want to participate in validating blocks as a validator, you can register yourself into the validator set by submitting a transaction.

For more details, see the CLI guide.

Last updated