Start the local chains
In this chapter, you will learn how to spawn four Gaia chains, connect them in an arbitrary topology and use Hermes to transfer tokens between them.
flowchart LR
ibc0((ibc-0))
ibc1((ibc-1))
ibc2((ibc-2))
ibc3((ibc-3))
ibc0---ibc1
ibc1---ibc2
ibc2---ibc3
ibc0---ibc3
As for the Local chains tutorial, we will make use of Gaiad Manager gm that we installed in Install Gaiad Manager.
Reset your configuration
First, make sure that no chain is currently running by killing all gaiad processes.
gm stop
Then, make sure that your folder $HOME/.gm does not contain any ibc-* or node-* file. You can remove them with
rm -r $HOME/.gm/node-*
rm -r $HOME/.gm/ibc-*
Copy and paste the configuration below to $HOME/.gm/gm.toml and set Hermes' binary path according to your setup. The following contains the configuration of 4 IBC-enabled chains.
gm.toml
[global]
add_to_hermes = false
auto_maintain_config = true
extra_wallets = 2
gaiad_binary = "~/go/bin/gaiad"
hdpath = ""
home_dir = "~/.gm"
ports_start_at = 27000
validator_mnemonic = ""
wallet_mnemonic = ""
[global.hermes]
binary = "$HOME/hermes/target/release/hermes" # change this path according to your setup
config = "~/.hermes/config.toml"
log_level = "info"
telemetry_enabled = true
telemetry_host = "127.0.0.1"
telemetry_port = 3001
[ibc-0]
ports_start_at = 27010
[ibc-1]
ports_start_at = 27020
[ibc-2]
ports_start_at = 27030
[ibc-3]
ports_start_at = 27040
[node-0]
add_to_hermes = true
network = "ibc-0"
ports_start_at = 27050
[node-1]
add_to_hermes = true
network = "ibc-1"
ports_start_at = 27060
[node-2]
add_to_hermes = true
network = "ibc-2"
ports_start_at = 27070
[node-3]
add_to_hermes = true
network = "ibc-3"
ports_start_at = 27080
NOTE: If you have any
Dockercontainers running that might be using the same ports asgaiad(e.g. port 27010-27012), please ensure you stop them first before proceeding to the next step.
Finally, start the chains with the start command.
gm start
This configures and starts four gaiad instances.
graph TD
A[gm] -->|start| C(start chains)
C -->|gaiad| D[ibc-0]
C -->|gaiad| E[ibc-1]
C -->|gaiad| F[ibc-2]
C -->|gaiad| G[ibc-3]
If the command runs successfully, it should output something similar to:
Creating ibc-0 config...
ibc-0 started, PID: 21330, LOG: $HOME/.gm/ibc-0/log
Creating ibc-1 config...
ibc-1 started, PID: 21888, LOG: $HOME/.gm/ibc-1/log
Creating ibc-2 config...
ibc-2 started, PID: 22443, LOG: $HOME/.gm/ibc-2/log
Creating ibc-3 config...
ibc-3 started, PID: 22999, LOG: $HOME/.gm/ibc-3/log
Creating node-0 config...
node-0 started, PID: 23547, LOG: $HOME/.gm/node-0/log
Creating node-1 config...
node-1 started, PID: 24101, LOG: $HOME/.gm/node-1/log
Creating node-2 config...
node-2 started, PID: 24649, LOG: $HOME/.gm/node-2/log
Creating node-3 config...
node-3 started, PID: 25194, LOG: $HOME/.gm/node-3/log
Run the following command to check the status of the chains:
gm status
If the command is successful, you should see a message similar to:
NODE PID RPC APP GRPC HOME_DIR
ibc-0 21330 27010 27011 27012 $HOME/.gm/ibc-0
node-0 23547 27050 27051 27052 $HOME/.gm/node-0
ibc-1 21888 27020 27021 27022 $HOME/.gm/ibc-1
node-1 24101 27060 27061 27062 $HOME/.gm/node-1
ibc-2 22443 27030 27031 27032 $HOME/.gm/ibc-2
node-2 24649 27070 27071 27072 $HOME/.gm/node-2
ibc-3 22999 27040 27041 27042 $HOME/.gm/ibc-3
node-3 25194 27080 27081 27082 $HOME/.gm/node-3
Hermes' configuration file
Gaiad Manager gm takes care of creating the configuration file. Run the command below to create the $HOME/.hermes/config.toml file:
gm hermes config
NOTE: You can visit the
Configurationsection for more information about the configuration file.
Based on the gm.toml above, your $HOME/.hermes/config.toml file should look like:
config.toml
[global]
log_level = 'info'
[mode]
[mode.clients]
enabled = true
refresh = true
misbehaviour = true
[mode.connections]
enabled = true
[mode.channels]
enabled = true
[mode.packets]
enabled = true
clear_interval = 100
clear_on_start = true
tx_confirmation = true
[telemetry]
enabled = true
host = '127.0.0.1'
port = 3001
[[chains]]
id = 'ibc-0'
type = 'CosmosSdk'
rpc_addr = 'http://localhost:27050'
grpc_addr = 'http://localhost:27052'
event_source = { mode = 'push', url = 'ws://localhost:27050/websocket', batch_delay = '200ms' }
rpc_timeout = '15s'
trusted_node = true
account_prefix = 'cosmos'
key_name = 'wallet'
store_prefix = 'ibc'
gas_price = { price = 0.001, denom = 'stake' }
gas_multiplier = 1.2
default_gas = 1000000
max_gas = 10000000
max_msg_num = 30
max_tx_size = 2097152
clock_drift = '5s'
max_block_time = '30s'
trusting_period = '14days'
trust_threshold = { numerator = '2', denominator = '3' }
[[chains]]
id = 'ibc-1'
type = 'CosmosSdk'
rpc_addr = 'http://localhost:27060'
grpc_addr = 'http://localhost:27062'
event_source = { mode = 'push', url = 'ws://localhost:27060/websocket', batch_delay = '200ms' }
rpc_timeout = '15s'
trusted_node = true
account_prefix = 'cosmos'
key_name = 'wallet'
store_prefix = 'ibc'
gas_price = { price = 0.001, denom = 'stake' }
gas_multiplier = 1.2
default_gas = 1000000
max_gas = 10000000
max_msg_num = 30
max_tx_size = 2097152
clock_drift = '5s'
max_block_time = '30s'
trusting_period = '14days'
trust_threshold = { numerator = '2', denominator = '3' }
[[chains]]
id = 'ibc-2'
type = 'CosmosSdk'
rpc_addr = 'http://localhost:27070'
grpc_addr = 'http://localhost:27072'
event_source = { mode = 'push', url = 'ws://localhost:27070/websocket', batch_delay = '200ms' }
rpc_timeout = '15s'
trusted_node = true
account_prefix = 'cosmos'
key_name = 'wallet'
store_prefix = 'ibc'
gas_price = { price = 0.001, denom = 'stake' }
gas_multiplier = 1.2
default_gas = 1000000
max_gas = 10000000
max_msg_num = 30
max_tx_size = 2097152
clock_drift = '5s'
max_block_time = '30s'
trusting_period = '14days'
trust_threshold = { numerator = '2', denominator = '3' }
[[chains]]
id = 'ibc-3'
type = 'CosmosSdk'
rpc_addr = 'http://localhost:27080'
grpc_addr = 'http://localhost:27082'
event_source = { mode = 'push', url = 'ws://localhost:27080/websocket', batch_delay = '200ms' }
rpc_timeout = '15s'
trusted_node = true
account_prefix = 'cosmos'
key_name = 'wallet'
store_prefix = 'ibc'
gas_price = { price = 0.001, denom = 'stake' }
gas_multiplier = 1.2
default_gas = 1000000
max_gas = 10000000
max_msg_num = 30
max_tx_size = 2097152
clock_drift = '5s'
max_block_time = '30s'
trusting_period = '14days'
trust_threshold = { numerator = '2', denominator = '3' }
Adding private keys to the chains
Next, we will need to associate a private key to every chain which hermes will use to sign transactions. gm will automatically generate and associate them with:
gm hermes keys
If successful, the command should show an output similar to:
SUCCESS Added key 'wallet' (cosmos1qsl5sq48r7xdfwq085x9pnlfu9ul5seufu3n03) on chain ibc-0
SUCCESS Added key 'wallet2' (cosmos1haaphqucg2u9g8gwgv6z8jzegvca85r4d7yqh9) on chain ibc-0
SUCCESS Added key 'wallet1' (cosmos1cgjf7m9txsxf2pdekxk60ll6xusx0heznqsnxn) on chain ibc-0
SUCCESS Added key 'wallet' (cosmos1zp3t2rp7tjr23wchp36lmw7vhk77gtvvc7lc5s) on chain ibc-1
SUCCESS Added key 'wallet2' (cosmos1644x9c8pyfwcmg43ch2u3vr6hl4rkmkz2weq39) on chain ibc-1
SUCCESS Added key 'wallet1' (cosmos1dsrj2uqjvtssenkwperuvfkgkg2xvmydvpzswy) on chain ibc-1
SUCCESS Added key 'wallet' (cosmos1k6c6le34zsmz34yez84a7tquedy3mkc3hy7wg8) on chain ibc-2
SUCCESS Added key 'wallet2' (cosmos1murv55h3utv5ck0a2tk5ue3n88wgglhlhyzyq8) on chain ibc-2
SUCCESS Added key 'wallet1' (cosmos1r8sq88n4k8ajsmq3sscnsd8829lqxvsmue2gf7) on chain ibc-2
SUCCESS Added key 'wallet' (cosmos1eykzqwq20sqdgvhf0tmz6xjq9mlcluwxed77gj) on chain ibc-3
SUCCESS Added key 'wallet2' (cosmos1lz6df9uggl9459z2vusw9tknpy3xn2v7yq60k9) on chain ibc-3
SUCCESS Added key 'wallet1' (cosmos15jxyjskrx7s8yqpfn3xddlrx7qcq0f8r69mp4g) on chain ibc-3
TROUBLESHOOTING:
- If the command does not out output anything, make sure the path to Hermes' binary is set in
$HOME/.gm/gm.toml.
The $HOME/.gm directory
This directory is created when you install gm and the binaries are stored here but when we start the chains, all the related files and folders are stored here as well.
The $HOME/.gm directory has a tree structure similar to:
.gm
├── bin
│ ├── gm
│ ├── lib-gm
│ └── shell-support
├── gm.toml
├── ibc-0
│ ├── config
│ ├── data
│ ├── init.json
│ ├── keyring-test
│ ├── log
│ ├── pid
│ ├── validator_seed.json
│ ├── wallet1_seed.json
│ ├── wallet2_seed.json
│ └── wallet_seed.json
├── ibc-1
│ ├── config
│ ├── data
│ ├── init.json
│ ├── keyring-test
│ ├── log
│ ├── pid
│ ├── validator_seed.json
│ ├── wallet1_seed.json
│ ├── wallet2_seed.json
│ └── wallet_seed.json
├── ibc-2
│ ├── config
│ ├── data
│ ├── init.json
│ ├── keyring-test
│ ├── log
│ ├── pid
│ ├── validator_seed.json
│ ├── wallet1_seed.json
│ ├── wallet2_seed.json
│ └── wallet_seed.json
├── ibc-3
│ ├── config
│ ├── data
│ ├── init.json
│ ├── keyring-test
│ ├── log
│ ├── pid
│ ├── validator_seed.json
│ ├── wallet1_seed.json
│ ├── wallet2_seed.json
│ └── wallet_seed.json
├── node-0
│ ├── config
│ ├── data
│ ├── init.json
│ ├── log
│ └── pid
├── node-1
│ ├── config
│ ├── data
│ ├── init.json
│ ├── log
│ └── pid
├── node-2
│ ├── config
│ ├── data
│ ├── init.json
│ ├── log
│ └── pid
└── node-3
├── config
├── data
├── init.json
├── log
└── pid
Tip: You can use the command
tree $HOME/.gm/ -L 2to view the folder structure above
The $HOME/.hermes directory
By default, hermes expects the configuration file to be in the $HOME/.hermes folder.
It also stores the private keys for each chain in this folder as outlined in the Keys section.
After executing gm start, this is how the folder should look like:
$HOME/.hermes/
├── config.toml
└── keys
├── ibc-0
│ └── keyring-test
│ ├── wallet.json
│ ├── wallet1.json
│ └── wallet2.json
├── ibc-1
│ └── keyring-test
│ ├── wallet.json
│ ├── wallet1.json
│ └── wallet2.json
├── ibc-2
│ └── keyring-test
│ ├── wallet.json
│ ├── wallet1.json
│ └── wallet2.json
└── ibc-3
└── keyring-test
├── wallet.json
├── wallet1.json
└── wallet2.json
Next Steps
The next section describes how to create an arbitrary topology between these chains before relaying packets.