tendermint/docs/examples/getting-started.md

Tendermint

Overview

This is a quick start guide. If you have a vague idea about how Tendermint works and want to get started right away, continue. Otherwise, review the documentation.

Install

Quick Install

On a fresh Ubuntu 16.04 machine can be done with this script, like so:

curl -L https://git.io/vpgEI | bash
source ~/.profile

WARNING: do not run the above on your local machine.

The script is also used to facilitate cluster deployment below.

Manual Install

Requires:

• go minimum version 1.10
• $GOPATH environment variable must be set
• $GOPATH/bin must be on your $PATH (see https://github.com/tendermint/tendermint/wiki/Setting-GOPATH)

To install Tendermint, run:

go get github.com/tendermint/tendermint
cd $GOPATH/src/github.com/tendermint/tendermint
make get_tools && make get_vendor_deps
make install

Note that go get may return an error but it can be ignored.

Confirm installation:

$ tendermint version
0.18.0-XXXXXXX

Initialization

Running:

tendermint init

will create the required files for a single, local node.

These files are found in $HOME/.tendermint:

$ ls $HOME/.tendermint

config.toml  data  genesis.json  priv_validator.json

For a single, local node, no further configuration is required. Configuring a cluster is covered further below.

Local Node

Start tendermint with a simple in-process application:

tendermint node --proxy_app=kvstore

and blocks will start to stream in:

I[01-06|01:45:15.592] Executed block                               module=state height=1 validTxs=0 invalidTxs=0
I[01-06|01:45:15.624] Committed state                              module=state height=1 txs=0 appHash=

Check the status with:

curl -s localhost:46657/status

Sending Transactions

With the kvstore app running, we can send transactions:

curl -s 'localhost:46657/broadcast_tx_commit?tx="abcd"'

and check that it worked with:

curl -s 'localhost:46657/abci_query?data="abcd"'

We can send transactions with a key and value too:

curl -s 'localhost:46657/broadcast_tx_commit?tx="name=satoshi"'

and query the key:

curl -s 'localhost:46657/abci_query?data="name"'

where the value is returned in hex.

Cluster of Nodes

First create four Ubuntu cloud machines. The following was tested on Digital Ocean Ubuntu 16.04 x64 (3GB/1CPU, 20GB SSD). We'll refer to their respective IP addresses below as IP1, IP2, IP3, IP4.

Then, ssh into each machine, and execute this script:

curl -L https://git.io/vpgEI | bash
source ~/.profile

This will install go and other dependencies, get the Tendermint source code, then compile the tendermint binary.

Next, cd into docs/examples. Each command below should be run from each node, in sequence:

tendermint node --home ./node0 --proxy_app=kvstore --p2p.persistent_peers="167b80242c300bf0ccfb3ced3dec60dc2a81776e@IP1:46656,3c7a5920811550c04bf7a0b2f1e02ab52317b5e6@IP2:46656,303a1a4312c30525c99ba66522dd81cca56a361a@IP3:46656,b686c2a7f4b1b46dca96af3a0f31a6a7beae0be4@IP4:46656"
tendermint node --home ./node1 --proxy_app=kvstore --p2p.persistent_peers="167b80242c300bf0ccfb3ced3dec60dc2a81776e@IP1:46656,3c7a5920811550c04bf7a0b2f1e02ab52317b5e6@IP2:46656,303a1a4312c30525c99ba66522dd81cca56a361a@IP3:46656,b686c2a7f4b1b46dca96af3a0f31a6a7beae0be4@IP4:46656"
tendermint node --home ./node2 --proxy_app=kvstore --p2p.persistent_peers="167b80242c300bf0ccfb3ced3dec60dc2a81776e@IP1:46656,3c7a5920811550c04bf7a0b2f1e02ab52317b5e6@IP2:46656,303a1a4312c30525c99ba66522dd81cca56a361a@IP3:46656,b686c2a7f4b1b46dca96af3a0f31a6a7beae0be4@IP4:46656"
tendermint node --home ./node3 --proxy_app=kvstore --p2p.persistent_peers="167b80242c300bf0ccfb3ced3dec60dc2a81776e@IP1:46656,3c7a5920811550c04bf7a0b2f1e02ab52317b5e6@IP2:46656,303a1a4312c30525c99ba66522dd81cca56a361a@IP3:46656,b686c2a7f4b1b46dca96af3a0f31a6a7beae0be4@IP4:46656"

Note that after the third node is started, blocks will start to stream in because >2/3 of validators (defined in the genesis.json) have come online. Seeds can also be specified in the config.toml. See this PR for more information about configuration options.

Transactions can then be sent as covered in the single, local node example above.