# Quick Start
This is a quick start guide. If you have a vague idea about how Tendermint works and want to get started right away, continue.
# Quick Install
To quickly get Tendermint installed on a fresh Ubuntu 16.04 machine, use this script.
⚠️ Do not copy scripts to run on your machine without knowing what they do.
The script is also used to facilitate cluster deployment below.
# Manual Install
For manual installation, see the install instructions
will create the required files for a single, local node.
These files are found in
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:
kvstoreis a non persistent app, if you would like to run an application with persistence run
and blocks will start to stream in:
Check the status with:
# Sending Transactions
With the KVstore app running, we can send transactions:
and check that it worked with:
We can send transactions with a key and value too:
and query the key:
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.
ssh into each machine, and execute this script:
This will install
go and other dependencies, get the Tendermint source code, then compile the
Next, use the
tendermint testnet command to create four directories of config files (found in
./mytestnet) and copy each directory to the relevant machine in the cloud, so that each machine has
Before you can start the network, you'll need peers identifiers (IPs are not enough and can change). We'll refer to them as ID1, ID2, ID3, ID4.
Finally, from each machine, run:
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.
Persistent peers can also be specified in the
config.toml. See here for more information about configuration options.
Transactions can then be sent as covered in the single, local node example above.