Join the Network
Last updated
Last updated
This tutorial introduces deploying a new node on AWS and join the Panacea Mainnet.
Choose Ubuntu Server 20.04 LTS 64-bit (x86) with SSD Volume Type.
Choose the m5.large
instance type (minimum spec).
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.
Install prerequisites by following the Installation guide.
These instructions are for setting up a brand new full node from scratch.
First, initialize the node and create the necessary config files:
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.
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
:
Now, your full node has been initialized!
Fetch the genesis.json
file of the latest chain from the following links, and place it to ~/.panacead/config/genesis.json
.
Mainnet: https://github.com/medibloc/panacea-mainnet
Testnet: https://github.com/medibloc/panacea-testnet
Your node needs to know how to find peers.
Seed nodes can be found in:
Mainnet: https://github.com/medibloc/panacea-mainnet#seed-nodes
Testnet: https://github.com/medibloc/panacea-testnet#seed-nodes
Insert those <node_id>@<ip>
s with 26656 port to the persistent_peers
field in ~/.panacead/config/config.toml
.
For more information on seeds and peers, see the Using Tendermint: Peers.
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.
3.35.82.40:26657
13.124.96.254:26657
52.79.108.35:26657
trusted block info can be obtained via RPC.
Then, you need to edit several things in ~/.panacea/config/config.toml
file.
If your node have block history data previously synced, you need to clear the data first.
Start the full node with this command:
Check that everything is running smoothly:
View the status of the network with the Block Explorer
Mainnet: https://explorer.medibloc.org
Testnet: https://testnet-explorer.medibloc.org https://dev.mintscan.io/hygieia
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.
Configuration | Value |
---|---|
Configuration | Value |
---|---|
Type | Protocol | Port range | Description |
---|---|---|---|
Network
Choose an existing VPC or default one if you don't have any
Subnet
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
Size
500 GiB
Volume Type
General Purpose SSD (gp3)
IOPS
3000
Throughput
125 MB/s
SSH
TCP
22
Custom TCP
TCP
26656
P2P with other nodes
Custom TCP
TCP
26657
RPC
Custom TCP
TCP
1317
HTTP