Launch Multi CVM Node

Following this page provides guidance on setting up a local network using Docker, comprising a 4-node chain. This configuration serves as a valuable tool for developers seeking to test their applications and protocol functionalities within a multi-node environment.

Build & Start

To build start a 4 node testnet using docker, run:

make localnet-start

This command creates a 4-node network using the cvmdnode Docker image. The ports for each node are found in this table:

CosVMnode	P2P Port	RPC PortREST	Ethereum JSON-RPC Port	WebSocket Port
CosVMnode0	26656	26657	85458	8546
CosVMnode1	26659	26660	85478	8548
CosVMnode2	26661	26662	85498	8550
CosVMnode3	26663	26664	85518	8552

To update the binary, just rebuild it and restart the nodes

make localnet-start

The command above command will run containers in the background using Docker compose. You will see the network being created:

...
Creating network "cvm_localnet" with driver "bridge"
Creating cvmdnode0 ... done
Creating cvmdnode2 ... done
Creating cvmdnode1 ... done
Creating cvmdnode3 ... done

Stop Localnet

Once you are done, execute:

make localnet-stop

Configuration

The make localnet-start creates files for a 4-node testnet in ./build by calling the cvmd mainnet command. This outputs a handful of files in the ./build directory:

tree -L 3 build/

build/

├── cvmd

├── cvmd
├── gentxs
│   ├── node0.json
│   ├── node1.json
│   ├── node2.json
│   └── node3.json
├── node0
│   ├── cvmd
│   │   ├── key_seed.json
│   │   └── keyring-test-cosmos
│   └── cvmd
│       ├── config
│       ├── data
│       └── cvmd.log
├── node1
│   ├── cvmd
│   │   ├── key_seed.json
│   │   └── keyring-test-cosmos
│   └── cvmd
│       ├── config
│       ├── data
│       └── cvmd.log
├── node2
│   ├── cvmd
│   │   ├── key_seed.json
│   │   └── keyring-test-cosmos
│   └── cvmd
│       ├── config
│       ├── data
│       └── cvmd.log
└── node3
├── cvmd
│   ├── key_seed.json
│   └── keyring-test-cosmos
└── cvmd
    ├── config
    ├── data
    └── cvmd.log

Each ./build/nodeN directory is mounted to the /cvmd directory in each container.

Logging

In order to see the logs of a particular node you can use the following command:

# node 0: daemon logs
docker exec cvmdnode0 tail cvmd.log

# node 0: REST & RPC logs
docker exec cvmdnode0 tail cvmd.log

The logs for the daemon will look like:

I[2020-07-29|17:33:52.452] starting ABCI with Tendermint                module=main
E[2020-07-29|17:33:53.394] Can't add peer's address to addrbook         module=p2p err="Cannot add non-routable address 272a247b837653cf068d39efd4c407ffbd9a0e6f@51.79.231.20:26656"
E[2020-07-29|17:33:53.394] Can't add peer's address to addrbook         module=p2p err="Cannot add non-routable address 3e05d3637b7ebf4fc0948bbef01b54d670aa810a@51.79.231.20:26656"
E[2020-07-29|17:33:53.394] Can't add peer's address to addrbook         module=p2p err="Cannot add non-routable address cvm1uguepfhe5wj2npcd4kqwzuf63tqqvfaaxljwx2@51.79.231.20:26656"
I[2020-07-29|17:33:58.828] Executed block                               module=state height=88 validTxs=0 invalidTxs=0
I[2020-07-29|17:33:58.830] Committed state                              module=state height=88 txs=0 appHash=90CC5FA53CF8B5EC49653A14DA20888AD81C92FCF646F04D501453FD89FCC791
I[2020-07-29|17:34:04.032] Executed block                               module=state height=89 validTxs=0 invalidTxs=0
I[2020-07-29|17:34:04.034] Committed state                              module=state height=89 txs=0 appHash=0B54C4DB1A0DACB1EEDCD662B221C048C826D309FD2A2F31FF26BAE8D2D7D8D7
I[2020-07-29|17:34:09.381] Executed block                               module=state height=90 validTxs=0 invalidTxs=0
I[2020-07-29|17:34:09.383] Committed state                              module=state height=90 txs=0 appHash=75FD1EE834F0669D5E717C812F36B21D5F20B3CCBB45E8B8D415CB9C4513DE51
I[2020-07-29|17:34:14.700] Executed block                               module=state height=91 validTxs=0 invalidTxs=0

Whereas the logs for the REST & RPC server would look like:

I[2020-07-30|09:39:17.488] Starting application REST service (chain-id: "7305661614933169792")... module=rest-server
I[2020-07-30|09:39:17.488] Starting RPC HTTP server on 127.0.0.1:8545   module=rest-server
...

Follow Logs

You can also watch logs as they are produced via Docker with the --follow (-f) flag, for example:

docker logs -f cvmdnode0

Interact with the Localnet

Ethereum JSON-RPC & Websocket Ports

To interact with the testnet via WebSockets or RPC/API, you will send your request to the corresponding ports:

CVM JSON-RPC	Eth Websocket
8545	8546

You can send a curl command such as:

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[],"id":1}' -H "Content-Type: application/json" 192.162.10.1:8545

Additional instructions on how to interact with the WebSocket can be found on the events documentation.

Keys & Accounts

To interact with cvmd and start querying state or creating txs, you use the cvmd directory of any given node as your home, for example:

cvmd keys list --home ./build/node0/cvmd

Now that accounts exists, you may create new accounts and send those accounts funds!

Special Binaries

If you have multiple binaries with different names, you can specify which one to run with the BINARY environment variable. The path of the binary is relative to the attached volume. For example:

# Run with custom binary
BINARY=cvm make localnet-start