Testnet configuration and data for Shentu Chain
This is a fix release that fixes some of the bugs in x/oracle
.
You are recommended to replace running 0.13.x
versions of certikd
and certikcli
with this version.
The replace does NOT require any certikd
or certikcli
environment change. Just direct replace can be done safely, after you close any running certikd
or certikcli
process.
If you are syncing from height 0 in shentu-rts
, boot up your node with 0.13.2
and switch to 0.13.3
after it starts syncing.
Also the attached genesis refers to shentu-incentivized-3 testnet genesis.
For shentu-rts participants, you can use binaries from either 0.13.2 or 0.13.1. The only difference they have is certikd migrate
functionality, which only affects shentu-incentivized
nodes during the upgrade to shentu-incentivized-3
For shentu-incentivized-x participants, you MUST use this version while upgrading. Else, you will have a wrong genesis file.
This patch adds genesis data generation and enables the oracle
module.
Please follow the readme with the binaries below to upgrade from shentu-incentivized-2
to shentu-incentivized-3
https://github.com/certikfoundation/chain/blob/master/shentu-incentivized-3/README.md
Shentu-Incentivized validators: please do not use this version for migration. Use 0.13.2 instead.
For validators intending to maintain their nodes for the current Shentu Incentivized-2 testnet, upgrade instructions will come out early next week to upgrade the binaries, similar with 0.12 upgrade.
Shentu RTS genesis time will be Sep. 7th, 12:00AM EDT (subject to change).
Raise the Stakes will start off new. You should go through the following instructions to submit a genesis transaction if you are selected as one of the participants of the CertiK validator competition program, Raise the Stakes.
Notes: if you are not planning to maintain the node for the current testnet (shentu-incentivized-2) to the validator program testnet (shentu-rts), please unbond your validator before shutting down your node to ensure the current testnet remains healthy.
Caution: make sure you are using the correct certikd binary when following the instructions. from step 3, you should use the new certikd binary. Also, make sure you are using the same account key you submitted for the Raise the Stakes.
The genesis.json file is in the assets section below. You have to download it and place it in the config folder to generate a valid gentx.
NOTE: The gentx collection is on-hold. Please refer to our discord channel announcement https://discord.gg/d6Bfa7 for further announcements
This is a new genesis release. You should go through the following instructions to submit a genesis transaction if you are selected as one of the participants of the CertiK validator competition program, Raise the Stakes.
Notes: if you are switching from the current testnet (shentu-incentivized-2) to the validator program testnet (shentu-rts), please unbond your validator before shutting down your node to ensure the current testnet remains healthy.
Caution: make sure you are using the correct certikd binary when following the instructions. from step 3, you should use the new certikd binary. Also, make sure you are using the same account key you submitted for the Raise the Stakes.
The genesis.json file is in the assets section below. You have to download it and place it in the config folder to generate a valid gentx.
certikd unsafe-reset-all
certikd
directory.certikd init <node_name> --chain-id=shentu-rts
.certikd
directory (~/.certikd/config/genesis.json
by default, replace the existing genesis if you have one).<amount>
.
certikd gentx --name <key_name> --amount <amount>
Genesis transaction written to "/home/ubuntu/.certikd/config/gentx/gentx-4b289001f5578a10420e9d64243fbb09b156bec7.json"
gentx-<some_code>.json
) under the gentx/
directory of this repo.
This is an upgrade release. If you were running a validator or a full node, carefully read the following instructions to upgrade to the v0.11 testnet. If you are new to the CertiK Incentivized Testnet, you can join after we release the genesis file here.
Caution: make sure you are using the correct certikd binary when following the instructions. from step 3, you should use the new certikd binary.
The genesis.json file is in the assets section below. We recommend you to download it instead of migrating from the old chain and skip steps 2~5.
certikd start --halt-height=191300
certikd export --for-zero-height --height 191300 > genesis_old.json
time=$(curl https://certik-shentu-incentivized-vermilionbird.noopsbycertik.com/blocks/191300 | jq -r '.block["header"]["time"]') && TZ=UTC date -d "$time +60 min" +"%Y-%m-%dT%H:%M:%SZ"
jq
to be installed beforehand.curl https://certik-shentu-incentivized-vermilionbird.noopsbycertik.com/blocks/191300 | jq -r '.block["header"]["time"]'|xargs -0 date -v +60M -j -f "%Y-%m-%dT%H:%M:%S" +"%Y-%m-%dT%H:%M:%SZ"
certikd start
, execute the command to get the genesis time, and then kill the certikd process) (tested on WSL)
time=$(certikcli query block 191300 --trust-node=true | jq -r '.block["header"]["time"]') && TZ=UTC date -d "$time +60 min" +"%Y-%m-%dT%H:%M:%SZ"
certikd migrate genesis_old.json --chain-id=shentu-incentivized-2 --genesis-time=”<genesis_time>” > genesis.json
seeds = "9e29e87375a839ac785fed7bcfe8c56866313e18@ec2-3-209-80-51.compute-1.amazonaws.com:26656"
Note that you can skip 3~5 by waiting out and downloading the new official genesis file, planned to be updated here.
The chain will not start until the genesis time. Once you are done setting things up and started certikd process, wait until the genesis time is reached in UTC to see new blocks being produced.
Make sure you are using the new binary after step 2.
Here are the seed nodes you can connect to
# List of seed nodes to connect to
9e29e87375a839ac785fed7bcfe8c56866313e18@ec2-3-209-80-51.compute-1.amazonaws.com:26656
43cf8249245e5df93dc02108bee48e74f2748903@ec2-34-204-190-245.compute-1.amazonaws.com:26656
990a3669b7e21dedd58a02b85726d35a12fb8c09@ec2-3-235-76-135.compute-1.amazonaws.com:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
You can add the seeds using the above list. Separate them by a comma. For example:
seeds = "9e29e87375a839ac785fed7bcfe8c56866313e18@ec2-3-209-80-51.compute-1.amazonaws.com:26656,43cf8249245e5df93dc02108bee48e74f2748903@ec2-34-204-190-245.compute-1.amazonaws.com:26656"
Note that these won't be up until we finish our own upgrade process.
genesis.json shasum
d7b7403d8bba0bed6aeb0e15d351882545d23dc3
sha256sum
bfc140b9e5f020185105c208fb813f2be00308823c0ac1a284e26e727a51a116
The incentivized testnet release comes with a brand new chain with a clean history. Any old history will be discarded in favor of this chain.
shasum
of genesis.json is 44ca3e4049d0ac0e24a5087f7c767ffd01a7d38a
certikd init --chain-id shentu-incentivized <your_moniker>
. Replace <your_moniker>
with a name of your choice.~/.certikd/config/
.config.toml
file. By default, it's located in ~/.certikd/config/config.toml
.minimum gas price
if you are planning to run a validator. Modify persistent_peers and/or seeds list to the provided list.certikd
daemon. You can start through certikd start &> certikd.log
. Any output from the daemon will be written to certikd.logcertikcli keys add <key_name>
command. Replace <key_name>
with a name of your choice.seeds = "[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656"
For further information, you can refer to detailed guide to join certikd testnet
This is a new release for CertiK Chain with various different features and bug fixes. The 0.8 chain data was copied over at height 1343300.
To upgrade to the new binary, there are two options.
Startup from genesis (WARNING: due to high load of data in the genesis file, this method will require more than 8GB of RAM to follow.)
killall certikd
).config/genesis.json
. (by default it is located in ~/.certikd/config/genesis.json
.certikd unsafe-reset-all
.persistent_peers.txt
to config/config.toml
, under persistent_peers = "<paste content here>"
.certikd start
with the new binary.Starting from a pre-loaded state at height 1 (takes up to 2GB of memory)
data/
directory.Note that it might take up to 5 minutes to load and commit the first height when starting off from genesis.
If you were a validator before the update, you will have to unjail yourself using the command certikcli tx slashing unjail
.
It is crucial you run certikd unsafe-reset-all
to prevent any unexpected behavior after you upgrade.
A small enhancement from the 0.8.0 testnet version, with --pruning flag for certikd start command for memory management.
pruning will have 3 options:
This is the first full testnet release.
Major changes in this release.
This is the first open beta testnet release.
Major changes in this release.
CVM execution gas model is consistent with EVM
For beta testnet 3.0