Skip to content

Latest commit

 

History

History
118 lines (85 loc) · 5 KB

README.md

File metadata and controls

118 lines (85 loc) · 5 KB
Raw

dungeontest-1 Chain Details

Status: PENDING

The dungeontest-1 chain is launched to test the dungeon chain.

jq -S -c -M '.' genesis.json | sha256sum
309c4878f29866f1f58531d882a1a3a79980f1d24196fe679c77a24c9b1eab8a  -
  • Reference binary: https://github.com/Crypto-Dungeon/dungeonchain/raw/main/network/dungeontest-1/dungeond-0.1.0-amd64.tar.gz
    • tar -xvzf dungeond-0.1.0-amd64.tar.gz
  • Binary sha256sum: e44429f3f67c2c57ced7be208092264aed712e6d7b4140e03878552d50dbb2e8
  • Genesis file without CCV state: genesis.json.tar.gz
    • tar -xvzf genesis.json.tar.gz "./network/dungeontest-1/genesis.json" --one-top-level=genesis.json --strip-components 4
  • SHA256 for genesis file without CCV state: 8ee776b221f6c2440079ed5c5bb440f68741aa31988e00babcfc93ae965adb98

The following items will be included in the consumer addition proposal:

  • Genesis file hash
    • The SHA256 is used to verify against the genesis file (without CCV state) that the proposer has made available for review.
    • The genesis.json.tar.gz file cannot be used to run the chain: it must be updated with the CCV (Cross Chain Validation) state after the spawn time is reached.
    • The genesis file includes funds for a relayer and a faucet account, and signed_blocks_window has been set to 20000.
  • Binary hash
    • The dungeond-linux-amd64 binary is only provided to verify the SHA256. It was built with commit f2325ed0e0d341f4280992ac3cbc61b9a967d578. You can generate the binary following the build instructions in that repo or using one of the scripts provided here.
  • Spawn time
    • Even if a proposal passes, the CCV state will not be available from the provider chain until after the spawn time is reached.

Endpoints

Persistent nodes:

  1. 9c9affab7652c9c5a2898d0dd244840c90bc8ba9@dungeon-cherry.ics-testnet.polypore.xyz:26656
  2. 4c9fe209358b0821fe48be7e449a3ed02af7b740@dungeon.ics-testnet.polypore.xyz:26656

IBC Information

Connections and channels will be posted here shortly after the chain launches.

How to Join

Bash Scripts

Run either one of the scripts provided to set up a dungeon service:

  • setup-dungeon.sh will create a dungeonchain service.
  • setup-dungeon-cv.sh will create a cv-dungeonchain service.
  • Both scripts must be run either as root or from a sudoer account.
  • Both scripts will attempt to build a binary from the Crypto-Dungeon/dungeonchain repo.

Opt in Before Launch

  • You must submit your opt-in transaction before the spawn time is reached to start signing blocks as soon as the chain starts. 
    gaiad tx provider opt-in dungeontest-1 <consumer node public key>

Launch Instructions

After the spawn time is reached:

  • The launch genesis file will be posted in this repo.
  • Copy this file to your consumer chain's home /config/genesis.json.
  • Start your node

Preparing the genesis file

These are the commands we will use to generate the launch genesis file after the spawn time is reached:

  • Obtain CCV state
  • Populate reward denoms
  • Populate provider reward denoms
  • Patch the consumer genesis file
gaiad q provider consumer-genesis dungeontest-1 -o json --node https://rpc.provider-sentry-01.ics-testnet.polypore.xyz:443 > ccv.json
jq '.params.reward_denoms |= ["udgn"]' ccv.json > ccv-denom.json
jq '.params.provider_reward_denoms |= ["uatom"]' ccv-denom.json > ccv-provider-denom.json
jq -s '.[0].app_state.ccvconsumer = .[1] | .[0]' dungeon-genesis-pre-spawn.json ccv-provider-denom.json > genesis.json