Skip to content

Latest commit

 

History

History
148 lines (107 loc) · 7.4 KB

README.md

File metadata and controls

148 lines (107 loc) · 7.4 KB
Raw

Interchain Security Private Testnet

Joining the Provider Chain

To join the provider chain, you can

Starting Consumer Chains

The genesis file of the consumer chain must be updated with the CCV states from the provider chain before the consumer chain binary can start. This can only be done after the SpawnTime specified in the create-consumer-chain proposal has been reached.

See the Consumer Chain Start Process page for more details.

sugar Consumer Chain

Status

  • 2022-10-31: The genesis file has been updated with the CCV states from the provider chain
  • 2022-10-29: Proposal 15 (Create the sugar consumer chain) has passed in the provider chain
  • 2022-10-27: The genesis file has been initialized

Details

  • Fresh genesis file: fresh-sugar-genesis.json
  • Fresh genesis hash: a0ceff8881b7c96778231df64e19a32c0ba9347cb8e83b6f847869fe79a3436d
  • Binary: neutrond (Linux amd64 build, interchain-security-with-governance branch)
  • Binary hash: 170da8c01aefc1772447fbb3c9d76661ad568b3ab16e93e6a0996f999c5d8ae5
  • Denom: grain
  • Bech32 prefix: neutron
  • Spawn time: 2022-10-31T14:00:00Z
  • Modified genesis file: ccv-sugar-genesis.json
  • Persistent peer: [email protected]:26656

❗ The following instructions require a genesis file that has already been updated with the CCV states. This file will not be available until after the SpawnTime is reached.

Join via Ansible Playbook

  • You must have SSH access to the node machine.
  • The binary will be set up for the sugar user.
  • The binary will run through cosmovisor in the cv-sugary.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 sugar Consumer Chain example: 
    ansible-playbook node.yml -i examples/inventory-join-sugar.yml -e 'target=<host address> node_key_file=<JSON file path> priv_validator_key_file=<JSON file path>"'

Join via Bash Script

  • The binary will run through cosmovisor in the cv-sugary.service service.

On the node machine:

salt Consumer Chain

Status

  • 2022-10-12: The salt chain was started and connected to the provider chain over IBC.
  • 2022-10-11: The genesis file has been updated with the CCV states from the provider chain
  • 2022-10-07: Proposal 12 (Create the salt consumer chain) has passed in the provider chain
  • 2022-10-05: The genesis file has been initialized

Details

  • Fresh genesis file: fresh-salt-genesis.json
  • Fresh genesis hash: 831133e22d00a9fcbac551decfd89555c52ae0f038a37f4d88e9479911f1d97a
  • Binary: salt-interchain-security-cd
  • Binary hash: 5ae76b4206c0bb8f87208c6ab2b68545fde4cf2c27d53041e24218cab4b3e925
  • Spawn time: 2022-10-11T14:00:00Z
  • Modified genesis file: ccv-salt-genesis.json
  • Persistent peer: [email protected]:26656

❗ The following instructions require a genesis file that has already been updated with the CCV states. This file will not be available until after the SpawnTime is reached.

Join via Ansible Playbook

  • You must have SSH access to the node machine.
  • The binary will be set up for the salt user.
  • The binary will run through cosmovisor in the cv-salty.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 salt Consumer Chain example: 
    ansible-playbook node.yml -i examples/inventory-join-salt.yml -e 'target=<host address> node_key_file=<JSON file path> priv_validator_key_file=<JSON file path>"'

Join via Bash Script

  • The binary will run through cosmovisor in the cv-salty.service service.

On the node machine:

  • Copy the node_key.json and priv_validator_key.json files from your provider chain validator node.
  • You can run join-salt.sh as root, or join-salt-non-root.sh otherwise.

pepper Consumer Chain

Status

  • 2022-10-26: The IBC relayer between the pepper and provider chain has been stopped.
  • 2022-10-12: The pepper chain was started and connected to the provider chain over IBC.
  • 2022-10-11: The genesis file has been updated with the CCV states from the provider chain
  • 2022-10-07: Proposal 13 (Create the pepper consumer chain) has passed in the provider chain
  • 2022-10-05: The genesis file has been initialized

Details

  • Fresh genesis file: fresh-pepper-genesis.json
  • Fresh genesis hash: a2b1a669f55c583034303ad6a16bd7ff571c42523b3c4bb75dfa8ea4502412d9
  • Binary: pepper-interchain-security-cd
  • Binary hash: 2911bd87cb3ecad2574d82f3874c1f8955856bf80d568f86700905d827c7d41b
  • Spawn time: 2022-10-11T15:00:00Z
  • Modified genesis file: ccv-pepper-genesis.json
  • Persistent peer: [email protected]:26656

❗ The following instructions require a genesis file that has already been updated with the CCV states. This file will not be available until after the SpawnTime is reached.

Join via Ansible Playbook

  • You must have SSH access to the node machine.
  • The binary will be set up for the pepper user.
  • The binary will run through cosmovisor in the cv-peppy.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 pepper Consumer Chain example: 
    ansible-playbook node.yml -i examples/inventory-join-pepper.yml -e 'target=<host address> node_key_file=<JSON file path> priv_validator_key_file=<JSON file path>"'

Join via Bash Script

  • The binary will run through cosmovisor in the cv-peppy.service service.

On the node machine: