Skip to content

Latest commit

 

History

History
150 lines (117 loc) · 5.14 KB

File metadata and controls

150 lines (117 loc) · 5.14 KB

Provider Chain Information

Contents

Status

  • Provider chain
  • Timeline
    • 2022-11-10: New gaiad binary published to bump ICS to v0.2.1.
    • 2022-11-07: Chain started

Chain Data

Current:


  • Binary: gaiad
  • Binary SHA256: d1dc6d31671a56b995cc8fab639a4cae6a88981de05d42163351431b8a6691cf
  • Genesis file: provider-genesis.json
  • Chain ID: provider
  • Denom: uprov
  • Bech32 prefix: cosmos

⛔ ATTENTION ⛔

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
  • Binary SHA256: 02e3d748d851f6ce935f1074307ebfa83f40a417ad6668928f7aa28d4149c671

Endpoints

Upgrading to ICS v0.2.1

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
  • 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

Join via Ansible Playbook

  • 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 and priv_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>"'

Join via Bash Script

On the node machine:

  • Copy the node_key.json and priv_validator_key.json files for your validator.
  • Run one of the following scripts:

Getting Tokens

Testnet coordinators will distribute provider chain tokens to eligible participants.

Creating a Validator

Once you have some tokens in your self-delegation account, you can submit the create-validator transaction.

  1. Obtain the validator public key
gaiad tendermint show-validator
  1. 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'