This document explains how to connect to the Testnet of a Cosmos-SDK based blockchain. It can be used to connect to the latest Testnet for the Cosmos Hub.
Follow these instructions to install the Cosmos-SDK and connect to the latest Testnet. This instructions work for both a local machine and a VM in a cloud server.
If you want to run a non-validator full-node, installing the SDK on a Cloud server is a good option. However, if you are want to become a validator for the Hub's mainnet you should look at more complex setups, including Sentry Node Architecture, to protect your node from DDOS and ensure high-availability (see the technical requirements). You can find more information on validators in our website, in the Validator FAQ and in the Validator Chat.
Install Go
Install go following the instructions in the official golang website.
You will require Go 1.9+ for this tutorial.
First, you will need to set up your GOPATH. Make sure that the location $HOME is something like /Users/<username>, you can corroborate it by typing echo $HOME in your terminal.
Go to $HOME with the command cd $HOME and open the the hidden file .barshrc with a code editor and paste the following lines (or .bash_profile if your're using OS X).
export GOPATH=$HOME/go
export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
Save and restart the terminal.
Note: If you can't see the hidden file, use the shortcut Command + Shift + . in Finder.
To update all packages in your GOPATH run:
go get -u all
If you want to update a specific package run:
go get -u <package_name>
Install GNU Wget
MacOS
brew install wget
Linux
sudo apt-get install wget
Note: You can check other available options for downloading wget here.
Cosmos SDK can be installed to $GOPATH/src/github.com/cosmos/cosmos-sdk like a normal Go program:
go get github.com/cosmos/cosmos-sdk
Now we can fetch the correct versions of each dependency by running:
cd $GOPATH/src/github.com/cosmos/cosmos-sdk
git fetch --all
git checkout v0.17.2
make get_tools // run $ make update_tools if already installed
make get_vendor_deps
make install
This will install the gaiad and gaiacli binaries. Verify that everything is OK by running:
gaiad version
You should see:
0.17.2-187be1a
And also:
gaiacli version
You should see:
0.17.2-187be1a
Genesis files are the starting point for the full-node to sync up with the network. In order to sync up with the correct version of the Testnet, be sure to choose the genesis file corresponding to the version of the Testnet you want to connect to.
Now that we have completed the basic SDK setup, we can start working on the genesis configuration for the chain we want to connect to.
Get the genesis transactions
git clone https://github.com/cosmos/testnets
mkdir -p $HOME/.gaiad/config
cp -a testnets/gaia-5001/. $HOME/.gaiad/config/gentx
gaiad unsafe_reset_all
gaiad init --gen-txs -o --chain-id=gaia-5001
Lastly change the moniker string in the config.toml to identify your node.
# A custom human readable name for this node
moniker = "<your_custom_name>"
Until this issue is fixed, also update the fast_sync = true line to fast_sync = false in config.toml.
Start the full node:
gaiad start
Check the everything is running smoothly:
gaiacli status
You'll need a private and public key pair (a.k.a. sk, pk respectively) to be able to receive funds, send txs, bond tx, etc.
To generate your a new key (default ed25519 elliptic curve):
gaiacli keys add <your_key_name>
Next, you will have to enter a passphrase for your key twice. Save the seed phrase in a safe place in case you forget the password.
Now if you check your private keys you will see the <your_key_name> key among them:
gaiacli keys show <your_key_name>
You can see all your other available keys by typing:
gaiacli keys list
The validator pubkey from your node should be the same as the one printed with the command:
gaiad show_validator
Finally, save your address and pubkey into a variable to use them afterwards.
MYADDR=<your_newly_generated_address>
MYPUBKEY=<your_newly_generated_public_key>
IMPORTANT: We strongly recommend to NOT use the same passphrase for your different keys. The Tendermint team and the Interchain Foundation will not be responsible for the lost of funds.
Go to the Riot chat and ask for some coins for your testnet. Be sure to provide the address of your key, as printed out above.
gaiacli send --amount=1000fermion --chain-id=<name_of_testnet_chain> --name=<key_name> --to=<destination_address>
The --amount flag defines the corresponding amount of the coin in the format --amount=<value|coin_name>
Optionally you can manually set the sequence number using the --sequence flag. gaiacli will infer it automatically if you do not.
Now check the destination account and your own account to check the updated balances (by default the latest block):
gaiacli account <destination_address>
gaiacli account <your_address>
You can also check your balance at a given block by using the --block flag:
gaiacli account <your_address> --block=<block_height>
Validators are actors from the network that are responsible from committing new blocks to the blockchain by submitting their votes. In terms of security, validators' stake is slashed in all the zones they belong if they become unavailable, double sign a transaction, or don't cast their votes. We strongly recommend entities intending to run validators in the Cosmos Hub's mainnet to check the technical requirements and take the necessary precautions to ensure high-availability, such as setting a Sentry Node architecture. If you have any question about validators, read the Validator FAQ and join the Validator Chat.
This section covers the instructions necessary to stake tokens to become a testnet validator candidate.
Your pubkey can be used to create a new validator candidate by staking some tokens:
You can find your node pubkey by running
gaiad show_validator
and this returns your public key for the declare-candidate command
gaiacli declare-candidacy --amount=<amount_of_fermions_to_steak>steak --pubkey=<your_node_pubkey> --address-candidate=<your_address> --moniker=<your_moniker> --name=<key_name> --chain-id=<name_of_testnet_chain>
You can add more information of the validator candidate such as --website, --keybase-sig or additional --details. If you want to edit the candidate info:
gaiacli edit-candidacy --details="To the cosmos !" --website="https://cosmos.network"
Finally, you can check all the candidate information by typing:
gaiacli candidate --address-candidate=<your_address>
To check that the validator is active you can find it on the validator set list:
gaiacli validatorset
Note: Remember that to be in the validator set you need to have more total power than the Xnd validator, where X is the assigned size for the validator set (by default X = 100).
You can delegate (i.e. bind) Atoms to a validator to become a delegator and obtain a part of its fee revenue in Photons. For more information about the Cosmos Token Model, refer to our whitepaper.
Bond your tokens to a validator candidate with the following command:
gaiacli delegate --amount=10steak --address-delegator=<your_address> --address-candidate=<bonded_validator_address> --name=<key_name> --chain-id=<name_of_testnet_chain>
If for any reason the validator misbehaves or you just want to unbond a certain amount of the bonded tokens:
gaiacli unbond --address-delegator=<your_address> --address-candidate=<bonded_validator_address> --shares=MAX --name=<key_name> --chain-id=<name_of_testnet_chain>
You can unbond a specific amount of shares (eg: 12.1) or all of them (MAX).
You should now see the unbonded tokens reflected in your balance and in your delegator bond:
gaiacli account <your_address>
gaiacli delegator-bond --address-delegator=<your_address> --address-candidate=<bonded_validator_address> --chain-id=<name_of_testnet_chain>