Contents
- Status
- Chain Data
- Endpoints
- Join via Ansible Playbook
- Join via Bash Script
- Getting Tokens
- Creating a Validator
- Provider chain
- Timeline
- 2022-11-10: New gaiad binary published to bump ICS to
v0.2.1
. - 2022-11-07: Chain started
- 2022-11-10: New gaiad binary published to bump ICS to
Current:
- Binary:
gaiad
- Linux amd64 build
- ICS v0.2.1 fork
- Commit
f729517a4a231a02172df6763c2ffed0524a2804
- Binary SHA256:
d1dc6d31671a56b995cc8fab639a4cae6a88981de05d42163351431b8a6691cf
- Genesis file: provider-genesis.json
- Chain ID:
provider
- Denom:
uprov
- Bech32 prefix:
cosmos
2022-11-10 13:00 UTC
- The gaiad version used to launch the provider chain is now considered to be deprecated. The section below has been kept for reference only.
2022-11-09 21:18 UTC
- We are expecting a new version of the provider chain binary to fix a critical Interchain Security-related bug. New version expected on Nov 10 at the earliest.
Deprecated:
- Binary:
gaiad
- Linux amd64 build
- ICS v0.2.0 fork
- Commit 84a33e4910abcc157f3333a70918a4fd6dc4cf6d
- Binary SHA256:
02e3d748d851f6ce935f1074307ebfa83f40a417ad6668928f7aa28d4149c671
- p2p seeds :
[email protected]:26656,8372500f2d1dfdcfbf9f0eccceb5e98d37f07b80@tenderseed.ccvalidators.com:29009
- Sentry 1
- Sentry 2
- Seed
The binary used to start the provider (ICS v0.2.0
) has been deprecated. You can either build a new binary or download the one in this folder.
- Stand-alone
gaiad
- Stop the service running
gaiad
- Replace the
gaiad
binary in the~/go/bin/
folder - Start the service running
gaiad
- Stop the service running
- Cosmovisor
- Stop the service running Cosmovisor
- Replace the
gaiad
binary in the~/.gaia/cosmovisor/current/bin/
folder - Start the service running Cosmovisor
After upgrading you should see the version below:
gaiad version
glnro/ics-sdk45-f729517a4a231a02172df6763c2ffed0524a2804
- You must have SSH access to the node machine.
- The binary will be set up for the
provider
user. - The binary will run through cosmovisor in the
cv-provider.service
service.
On your local machine:
- Copy the
node_key.json
andpriv_validator_key.json
files from your provider chain validator node. - Clone the cosmos-ansible repo.
- Run the playbook from the Join the Provider Chain section:
ansible-playbook node.yml -i game-of-chains-2022/provider/provider-join.yml -e 'target=<host address> node_key_file=<JSON file path> priv_validator_key_file=<JSON file path>"'
On the node machine:
- Copy the
node_key.json
andpriv_validator_key.json
files for your validator. - Run one of the following scripts:
- Gaia service: provider-join.sh
- Cosmovisor service: provider-join-cv.sh
Testnet coordinators will distribute provider chain tokens to eligible participants.
Once you have some tokens in your self-delegation account, you can submit the create-validator
transaction.
- Obtain the validator public key
gaiad tendermint show-validator
- Sumbit the
create-validator
transaction.
gaiad tx staking create-validator \
--amount 1000000uprov \
--pubkey '<public key from the previous command>' \
--moniker <your moniker> \
--chain-id provider \
--commission-rate 0.10 \
--commission-max-rate 1.00 \
--commission-max-change-rate 0.1 \
--min-self-delegation 1000000 \
--gas auto \
--from <self-delegation-account>
You can verify the validator was created in the block explorer, or in the command line:
gaiad q staking validators -o json | jq '.validators[].description.moniker'