cosmoshub-test-stargate-e

This doc contains information for setting up the stargate testnet with chain-id cosmoshub-test-stargate-e.

4 Things to do to get ready for cosmoshub-test-stargate-e

  1. Download the new genesis file 👉 https://storage.googleapis.com/stargate-genesis/genesis.json
    and verify sha256sum ~/cosmoshub-test-stargate/config/genesis.json
    4b552ed850946ab43a7025ca6925ddb1a86fc9c78ed50a6762bbb1bd0a5797b0
  2. Gaiad-unsafe-reset-all
  3. Build and deploy new Gaia 👉 https://github.com/cosmos/gaia/releases/tag/cosmoshub-test-stargate-e
  4. Update your seed address

Creating replacement keys (This is already completed)

git clone github.com/cosmos/gaia
cd gaia
git checkout cosmoshub-test-stargate-e
make build
gaiad init [moniker]
gaiad tendermint show-validator
# backup your key
cp ~/.gaiad/config/priv_validator_key.json ~/.gaiad/config/priv_validator_key.bkp.json

Note: Failing to submit your replacement keys will result in your keys being replaced so the chain can be started.

Deploying simulated upgrade keys

  1. You must have either submitted a key to us and come online during cosmoshub-test-stargate-a, cosmoshub-test-stargate-b or cosmoshub-test-stargate-c , cosmoshub-test-stargate-dor submit a new key to us to indicate intent to participate.

  2. You must use your mainnet validator operator key on the testnet.

  3. The keys are cosmosvalconspub1..... keys. They are ed25519 keys from tmkms, gaiad tendermint show-validator or other compatible systems.

  4. Iqlusion is going to replace the keys of non-participating validators and you will not be able to test against the forthcoming mainnet upgrade.

  5. Make a Pull Request to https://github.com/cosmosdevs/stargate
    This is a perfect example -> https://github.com/cosmosdevs/stargate/pull/85
    For non-technical users, you can make a pull request by forking the respository and creating a pull request from the forked repo


{
    "validator_name":"Citadel.one",
    "validator_address":"cosmosvaloper1lzhlnpahvznwfv4jmay2tgaha5kmz5qxerarrl",
    "stargate_consensus_public_key":"cosmosvalconspub1zcjduepquuaszms40adxzwkjr5ew4gj8s49dyjx5zsncar4cqfk4wh07eh8sjxjeaf"
}

Genesis file

Genesis for cosmoshub-test-stargate-e can be found here 👉https://storage.googleapis.com/stargate-genesis/genesis.json

Steps used to re-generate the genesis:

Pull the genesis snapshot mainnet snapshot at block 3924406.

wget https://storage.googleapis.com/stargate-genesis/3924406.cosmoshub-3.json

build/gaiad migrate ~/3924406.cosmoshub-3.json --chain-id=cosmoshub-test-stargate-e --initial-height 3924407 --replacement-cons-keys ~/stargate/validator_replacement.json > migrated_genesis.json

jq . migrated_genesis.json > genesis.json

Adjust the following governance parameters:

{
  "tally_params": {
    "quorum": "0.010000000000000000",
    "threshold": "0.500000000000000000",
    "veto_threshold": "0.334000000000000000"
  },
  "votes": [],
  "voting_params": {
    "voting_period": "172800s"
  }
}
sha256sum ~/cosmoshub-test-stargate/config/genesis.json

4b552ed850946ab43a7025ca6925ddb1a86fc9c78ed50a6762bbb1bd0a5797b0

NOTES

  • gaiad start will preform an extensive audit of the genesis file state that takes > 1 hour. gaiad start --x-crisis-skip-assert-invariants skips the audits and starts a node in 15 min.
  • We manually went in and edited the quorum and voting period for governance to enable faster testing of the IBC related governance functions in this testnet.

Seed nodes

seeds = "c5e186e29d322788b8154723d04e1de018d38475@162.222.177.241:26656"

persistent_peers = "c5e186e29d322788b8154723d04e1de018d38475@162.222.177.241:26656,8ea6c78e6689264de254859785748533fa7650dd@185.144.83.165:26656,56d1ff25fae28dc2cfdb2f93973843e471018875@185.144.83.180:26656,a14d8fb9cc31711674d2e97cea0dd94216cfb434@185.144.83.181:26656,9e7e8641412a942a6a06d06946b0c27cf46297f7@185.144.83.182:26656"

Chain ID

cosmoshub-test-stargate-e

Changes

Testnet plan

  • Custody of keys will be tested (signing, broadcasting, multisig)
  • Legacy amino will be tested
  • Voting to enable IBC and transfers of tokens on the testnet
  • Create IBC tokens on the testnet
  • Testing of the relayer, creating more IBC tokens
  • Simulated cosmovisor upgrade to build experience with
  • Governance proposal with final changes from IBC team
Select a repo