MediBloc Panacea
Comment on page

Join Mainnet/Testnet

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

Port range
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 REST API 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 ~/.panacea/config/config.toml as below.
timeout_commit = "5s"
After that, edit the ~/.panacea/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 ~/.panacea/config/genesis.json.
  • Mainnet:
  • Testnet:

Configure Persistent Peers

MediBloc is not operating seed nodes, but will provide them in near future.
Until then, please use public full nodes provided by MediBloc.
  • Mainnet:
  • Testnet:
Insert those public nodes to the persistent_peers field in the ~/.panacea/config/config.toml.
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.
You can use the following public RPC endpoints provided by MediBloc team.
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.
# The nodes that are providing statesync must be registered as persistent_peers.
persistent_peers = "[email protected]:26656,[email protected]:26656"
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 has block history data previously synced, you need to clear the database of your node first.
The unsafe-reset-all command will erase your node database. If you are running a validator node, be sure you backed up the following files, prior to running the unsafe-reset-all command.
  • ~/.panacea/data/priv_validator_state.json
  • ~/.panacea/config/priv_validator_key.json
  • ~/.panacea/config/node_key.json
And, restore these files after unsafe-reset-all to avoid potential double signing.
panacead tendermint unsafe-reset-all

Run a Full Node

Before Running a Node

Before running full node, it is highly recommended to use state sync.
It is possible to start from scratch but will take a significant amount of time and effort to catch up. To sync full node from scratch, it is important to note that you must start with v2.0.1 and proceed through several upgrades at proper block heights.
Another way is to use a snapshot to recover up to the latest block. We do not currently have an official snapshot download service, so please request a snapshot from the Panacea team or another full node operator.
For bootstrapping full node, state sync would be sufficient.

Launch Node

Start the full node with this command:
panacead start
Check that everything is running smoothly:
panacead status
In production, it is recommended to run the process in background by following the guide below.

Background Process

To run the node in a background process with automatic restarts, you can use a service manager like systemd. This is more reliable way to run a background process in the long term. To set this up, run the following:
sudo tee /etc/systemd/system/panacead.service > /dev/null <<EOF
Description=Panacea Daemon
ExecStart=$(which panacead) start
It is very important to set the LimitNOFILE=4096 since Panacea opens many DB files.
If you're using Cosmovisor, add the following environment variables after the LimitNOFILE line and replace $(which panacead) with $(which cosmovisor).
For more details about those environment variables, please see the Cosmovisor guide.
Then, setup the daemon.
sudo -S systemctl daemon-reload
sudo -S systemctl enable panacead # the process will be started automatically whenever your system is booted.
You can then start the process and confirm that it is running.
sudo -S systemctl start panacead
sudo service panacead status
sudo journalctl -u panacead -f --output cat # See logs from panacead

Monitor the chain using block explorers

View the status of the network with block explorers.
  • Mainnet: or
  • 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: Create your validator.
If you already joined as a validator and if you want to modify your validator details, please see the CLI guide: Edit validator description.