MediBloc Panacea
master
Search…
⌃K

Deploy a Testnet

This document describes 2 ways to setup a network of panacead nodes.

Using multiple machines

Deploy the first node

# Initialize the genesis.json file that will help you to bootstrap the network
panacead init node1 --chain-id=testing
# Create a key to hold your validator account
panacead keys add validator
# Add that key into the genesis.app_state.accounts array in the genesis file
# NOTE: this command lets you set the number of coins. Make sure this account has some coins
# with the genesis.app_state.staking.params.bond_denom denom.
panacead add-genesis-account $(panacead keys show validator -a) 100000000000000umed
# Generate the transaction that creates your validator
panacead gentx validator 1000000000000umed --commission-rate 0.1 --commission-max-rate 0.2 --commission-max-change-rate 0.01 --min-self-delegation 1000000 --chain-id testing
# Add the generated bonding transaction to the genesis file
panacead collect-gentxs
# Now its safe to start `panacead`
panacead start
This setup puts all the data for panacead in ~/.panacea. You can examine the genesis file that you created at ~/.panacea/config/genesis.json.

Deploy the second node

Init the second node using another moniker: node2.
panacead init node2 --chain-id=testing
Overwrite ~/.panacea/config/genesis.json with the first node's genesis.json.
Get a node ID of the first node.
panacead tendermint show-node-id
> 46046c89ec576daa0662613ee0142ab61dd2421e
Set a persistent_peers in the ~/.panacea/config/config.toml of the second node.
# Comma separated list of nodes to keep persistent connections to
persistent_peers = "<first_node_id>@<first_node_ip>:26656"
Start the second node.
panacead start