testnets

Connect to the gaia-7001 Testnet

NOTE: We are aware this documentation is a work in progress. We are actively working to improve the tooling and the documentation to make this process as painless as possible. In the meantime, join the Validator Chat for technical support, and open issues if you run into any! Thanks very much for your patience and support. :)

Setting Up a New Node

These instructions are for setting up a brand new full node from scratch. If you ran a full node on a previous testnet you will need to start from scratch due to some breaking changes in key format.

Install Go

Install go by following the official docs. Go 1.10+ is required for the Cosmos SDK. Remember to properly setup your $GOPATH, $GOBIN, and $PATH variables, for example:

mkdir -p $HOME/go/bin
echo "export GOPATH=$HOME/go" >> ~/.bash_profile
echo "export GOBIN=$GOPATH/bin" >> ~/.bash_profile
echo "export PATH=$PATH:$GOBIN" >> ~/.bash_profile

Install Cosmos SDK

Next, let's install the testnet's version of the Cosmos SDK.

mkdir -p $GOPATH/src/github.com/cosmos
cd $GOPATH/src/github.com/cosmos
git clone https://github.com/cosmos/cosmos-sdk
cd cosmos-sdk && git checkout v0.22.0
make get_tools && make get_vendor_deps && make install

That will install the gaiad and gaiacli binaries. Verify that everything is OK:

$ gaiad version
0.22.0

$ gaiacli version
0.22.0

Node Setup

Create the required configuration files, and initialize the node:

gaiad init --name <your_custom_moniker>

NOTE: Note that only ASCII characters are supported for the --name. Using Unicode renders your node unreachable.

You can also edit this moniker in the ~/.gaiad/config/config.toml file:

# A custom human readable name for this node
moniker = "<your_custom_moniker>"

Your full node has been initialized!

Upgrading From Previous Testnet

These instructions are for full nodes that have ran on previous testnets and would like to upgrade to the latest testnet.

Reset Data

First, remove the outdated files and reset the data.

rm $HOME/.gaiad/config/addrbook.json $HOME/.gaiad/config/genesis.json
gaiad unsafe_reset_all

Your node is now in a pristine state while keeping the original priv_validator.json and config.toml. If you had any sentry nodes or full nodes setup before, your node will still try to connect to them, but may fail if they haven't also been upgraded.

WARNING: Make sure that every node has a unique priv_validator.json. Do not copy the priv_validator.json from an old node to multiple new nodes. Running two nodes with the same priv_validator.json will cause you to double sign.

NOTE: key formats changed between gaia-6002 and gaia-7000. If you're trying to upgrade from gaia-6002, you will also need to delete your priv_validator.json:

rm $HOME/.gaiad/config/priv_validator.json

Software Upgrade

Now it is time to upgrade the software:

cd $GOPATH/src/github.com/cosmos/cosmos-sdk
git fetch --all && git checkout v0.22.0
make update_tools && make get_vendor_deps && make install

Your full node has been cleanly upgraded!

Genesis & Seeds

Copy the Genesis File

Fetch the testnet's genesis.json file and place it in gaiad's config directory.

mkdir -p $HOME/.gaiad/config
curl https://gist.githubusercontent.com/cwgoes/311da6ba05be6e113185a716538a44c3/raw/7b6e784cf29761b5781488006313bd69d164aa6c/chris-final.json > $HOME/.gaiad/config/genesis.json

Add Seed Nodes

Your node needs to know how to find peers. You'll need to add healthy seed nodes to $HOME/.gaiad/config/config.toml. Here are some seed nodes you can use:

# Comma separated list of seed nodes to connect to
seeds = "718145d422a823fd2a4e1e36e91b92bb0c4ddf8e@gaia-7000.coinculture.net:26656,[email protected]:26656,7c8b8fd03577cd4817f5be1f03d506f879df98d8@gaia-7000-seed1.interblock.io:26656,a28737ff02391a6e00a1d3b79befd57e68e8264c@gaia-7000-seed2.interblock.io:26656,987ffd26640cd03d08ed7e53b24dfaa7956e612d@gaia-7000-seed3.interblock.io:26656"

If those seeds aren't working, you can find more seeds and persistent peers on the Cosmos Explorer. Open the the Full Nodes pane and select nodes that do not have private (10.x.x.x) or local IP addresses. The Persistent Peer field contains the connection string. For best results use 4-6.

For more information on seeds and peers, read this.

Run a Full Node

Start the full node with this command:

gaiad start

Check that everything is running smoothly:

gaiacli status

View the status of the network with the Cosmos Explorer. Once your full node syncs up to the current block height, you should see it appear on the list of full nodes. If it doesn't show up, that's ok--the Explorer does not connect to every node.

Generating Keys

A Note on Keys in Cosmos:

There are three types of key representations that are used in this tutorial:

• cosmosaccaddr

  • Derived from account keys generated by gaiacli keys add
  • Used to receive funds
  • e.g. cosmosaccaddr15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

• cosmosaccpub

  • Derived from account keys generated by gaiacli keys add
  • e.g. cosmosaccpub1zcjduc3q7fu03jnlu2xpl75s2nkt7krm6grh4cc5aqth73v0zwmea25wj2hsqhlqzm

• cosmosvalpub

  • Generated when the node is created with gaiad init.
  • Get this value with gaiad tendermint show_validator
  • e.g. cosmosvalpub1zcjduc3qcyj09qc03elte23zwshdx92jm6ce88fgc90rtqhjx8v0608qh5ssp0w94c

Key Generation

You'll need an account private and public key pair (a.k.a. sk, pk respectively) to be able to receive funds, send txs, bond tx, etc.

To generate a new key (default ed25519 elliptic curve):

gaiacli keys add <account_name>

Next, you will have to create a passphrase to protect the key on disk. The output of the above command will contain a seed phrase. Save the seed phrase in a safe place in case you forget the password!

If you check your private keys, you'll now see <account_name>:

gaiacli keys show <account_name>

You can see all your available keys by typing:

gaiacli keys list

View the validator pubkey for your node by typing:

gaiad tendermint show_validator

WARNING: We strongly recommend NOT using the same passphrase for multiple keys. The Tendermint team and the Interchain Foundation will not be responsible for the loss of funds. This is not as important on the testnets, but is good security practice and should be followed.

Fund your account

The best way to get tokens is from the Cosmos Testnet Faucet. If the faucet is not working for you, try asking #cosmos-validators. The faucet needs the cosmosaccaddr from the account you wish to use for staking.

After receiving tokens to your address, you can view your account's balance by typing:

gaiacli account <account_cosmosaccaddr>

Note: When you query an account balance with zero tokens, you will get this error: No account with address <account_cosmosaccaddr> was found in the state. This can also happen if you fund the account before your node has fully synced with the chain. These are both normal. Also, we're working on improving our error messages!

Run a Validator Node

Validators are responsible for committing new blocks to the blockchain through voting. A validator's stake is slashed if they become unavailable, double sign a transaction, or don't cast their votes. If you only want to run a full node, a VM in the cloud is fine. However, if you are want to become a validator for the Hub's mainnet, you should research hardened setups. Please read Sentry Node Architecture to protect your node from DDOS and ensure high-availability. Also see the technical requirements). There's also more info on our website.

Create Your Validator

Your cosmosvalpub can be used to create a new validator by staking tokens. You can find your validator pubkey by running:

gaiad tendermint show_validator

Next, craft your gaiacli stake create-validator command:

NOTE: Don't use more steak thank you have! You can always get more by using the Faucet!

gaiacli stake create-validator \
  --amount=5steak \
  --pubkey=$(gaiad tendermint show_validator) \
  --address-validator=<account_cosmosaccaddr>
  --moniker="choose a moniker" \
  --chain-id=gaia-7001 \
  --from=<key_name>

Edit Validator Description

You can edit your validator's public description. This info is to identify your validator, and will be relied on by delegators to decide which validators to stake to. Make sure to provide input for every flag below, otherwise the field will default to empty (--moniker defaults to the machine name).

The --keybase-sig is a 16-digit string that is generated with a keybase.io account. It's a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.

gaiacli stake edit-validator
  --address-validator=<account_cosmosaccaddr>
  --moniker="choose a moniker" \
  --website="https://cosmos.network" \
  --keybase-sig="6A0D65E29A4CBC8E"
  --details="To infinity and beyond!"
  --chain-id=gaia-7001 \
  --from=<key_name>

View Validator Description

View the validator's information with this command:

gaiacli stake validator \
  --address-validator=<account_cosmosaccaddr> \
  --chain-id=gaia-7001

Your validator is active if the following command returns anything:

gaiacli advanced tendermint validator-set | grep "$(gaiad tendermint show_validator)"

You should also be able to see your validator on the Explorer. You are looking for the bech32 encoded address in the ~/.gaiad/config/priv_validator.json file.

Note: To be in the validator set, you need to have more total voting power than the 100th validator. This is not normally an issue.

Problem #1: My validator has voting_power: 0

Your validator has become auto-unbonded. In gaia-7001, we unbond validators if they do not vote on 50 of the last 100 blocks. Since blocks are proposed every ~2 seconds, a validator unresponsive for ~100 seconds will become unbonded. This usually happens when your gaiad process crashes.

Here's how you can return the voting power back to your validator. First, if gaiad is not running, start it up again:

gaiad start

Wait for your full node to catch up to the latest block. Next, run the following command. Note that <cosmosaccaddr> is the address of your validator account, and <name> is the name of the validator account. You can find this info by running gaiacli keys list.

gaiacli stake unrevoke <cosmosaccaddr> --chain-id=gaia-7001 --from=<name>

WARNING: If you don't wait for gaiad to sync before running unrevoke, you will receive an error message telling you your validator is still jailed.

Lastly, check your validator again to see if your voting power is back.

gaiacli status

You may notice that your voting power is less than it used to be. That's because you got slashed for downtime!

Problem #2: My gaiad crashes because of too many open files

The default number of files Linux can open (per-process) is 1024. gaiad is known to open more than 1024 files. This causes the process to crash. A quick fix is to run ulimit -n 4096 (increase the number of open files allowed) and then restart the process with gaiad start. If you are using systemd or another process manager to launch gaiad this may require some configuration at that level. A sample systemd file to fix this issue is below:

# /etc/systemd/system/gaiad.service
[Unit]
Description=Cosmos Gaia Node
After=network.target

[Service]
Type=simple
User=ubuntu
WorkingDirectory=/home/ubuntu
ExecStart=/home/ubuntu/go/bin/gaiad start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096

[Install]
WantedBy=multi-user.target

Delegating to a Validator

On the upcoming mainnet, you can delegate Atom to a validator. These delegators can receive part of the validator's fee revenue. Read more about the Cosmos Token Model.

Bond Tokens

On the testnet, we delegate steak instead of Atom. Here's how you can bond tokens to a testnet validator:

gaiacli stake delegate \
  --amount=10steak \
  --address-delegator=<account_cosmosaccaddr> \
  --address-validator=<validator_cosmosaccaddr> \
  --from=<key_name> \
  --chain-id=gaia-7001

While tokens are bonded, they are pooled with all the other bonded tokens in the network. Validators and delegators obtain a percentage of shares that equal their stake in this pool.

NOTE: Don't use more steak thank you have! You can always get more by using the Faucet!

Unbond Tokens

If for any reason the validator misbehaves, or you want to unbond a certain amount of tokens, use this following command. You can unbond a specific amount ofshares(eg:12.1) or all of them (MAX).

gaiacli stake unbond \
  --address-delegator=<account_cosmosaccaddr> \
  --address-validator=<validator_cosmosaccaddr> \
  --shares=MAX \
  --from=<key_name> \
  --chain-id=gaia-7001

You can check your balance and your stake delegation to see that the unbonding went through successfully.

gaiacli account <account_cosmosaccaddr>

gaiacli stake delegation \
  --address-delegator=<account_cosmosaccaddr> \
  --address-validator=<validator_cosmosaccaddr> \
  --chain-id=gaia-7001

Governance

Governance is the process from which users in the Cosmos Hub can come to consensus on software upgrades, parameters of the mainnet or on custom text proposals. This is done through voting on proposals, which will be submitted by Atom holders on the mainnet.

Some considerations about the voting process:

• Voting is done by bonded Atom holders on a 1 bonded Atom 1 vote basis
• Delegators inherit the vote of their validator if they don't vote
• Validators MUST vote on every proposal. If a validator does not vote on a proposal, they will be partially slashed
• Votes are tallied at the end of the voting period (2 weeks on mainnet). Each address can vote multiple times to update its Option value (paying the transaction fee each time), only the last casted vote will count as valid
• Voters can choose between options Yes, No, NoWithVeto and Abstain At the end of the voting period, a proposal is accepted if (YesVotes/(YesVotes+NoVotes+NoWithVetoVotes))>1/2 and (NoWithVetoVotes/(YesVotes+NoVotes+NoWithVetoVotes))<1/3. It is rejected otherwise

For more information about the governance process and how it works, please check out the Governance module specification.

Create a Governance proposal

In order to create a governance proposal, you must submit an initial deposit along with the proposal details:

• title: Title of the proposal
• description: Description of the proposal
• type: Type of proposal. Must be of value Text (types SoftwareUpgrade and ParameterChange not supported yet).

gaiacli gov submit-proposal \
  --title=<title> \
  --description=<description> \
  --type=<Text/ParameterChange/SoftwareUpgrade> \
  --proposer=<account_cosmosaccaddr> \
  --deposit=<40steak> \
  --from=<name> \
  --chain-id=gaia-7001

Increase deposit

In order for a proposal to be broadcasted to the network, the amount deposited must be above a minDeposit value (default: 10 steak). If the proposal you previously created didn't meet this requirement, you can still increase the total amount deposited to activate it. Once the minimum deposit is reached, the proposal enters voting period:

gaiacli gov deposit \
  --proposalID=<proposal_id> \
  --depositer=<account_cosmosaccaddr> \
  --deposit=<200steak> \
  --from=<name> \
  --chain-id=gaia-7001

NOTE: Proposals that don't meet this requirement will be deleted after MaxDepositPeriod is reached.

Query proposal

Once created, you can now query information of the proposal:

gaiacli gov query-proposal \
  --proposalID=<proposal_id> \
  --chain-id=gaia-7001

Vote on a proposal

After a proposal's deposit reaches the MinDeposit value, the voting period opens. Bonded Atom holders can then cast vote on it:

gaiacli gov vote \
  --proposalID=<proposal_id> \
  --voter=<account_cosmosaccaddr> \
  --option=<Yes/No/NoWithVeto/Abstain> \
  --from=<name> \
  --chain-id=gaia-7001

Query vote

Check the vote with the option you just submitted:

gaiacli gov query-vote \
  --proposalID=<proposal_id> \
  --voter=<account_cosmosaccaddr> \
  --chain-id=gaia-7001

Other Operations

Send Tokens

gaiacli send \
  --amount=10faucetToken \
  --chain-id=gaia-7001 \
  --from=<key_name> \
  --to=<destination_cosmosaccaddr>

NOTE: The --amount flag accepts the format --amount=<value|coin_name>.

Now, view the updated balances of the origin and destination accounts:

gaiacli account <account_cosmosaccaddr>
gaiacli account <destination_cosmosaccaddr>

You can also check your balance at a given block by using the --block flag:

gaiacli account <account_cosmosaccaddr> --block=<block_height>