You can copy paste this section to new testnet folder to check you follow the steps correctly.
All scripts rely heavily on environment variables to work correctly.
You will want to source ../<testnetname>/defaults.env as a basis, then
possibly declare a few more variables as desired.
- Checkout to a new branch
- Duplicate latest network directory and rename it to
newnet - Clean genesis account and gentx in genesis file
- Update chain-id
- Update start time in genesis file
- Update staking and fee token
- Update bech32 addresses
- Create a reserve address and add it to genesis, Make sure reserve has enough stake and fee tokens
- Add gen tx for validator node, collect-gentx, save
config/node_key.jsonandconfig/priv_validator.json, delete them on this folder. While setting up validator move these keys to the validator machine. - Merge the branch to master
Infrastructure setup is at devops folder
- Follow node instructions.
- Copy output of
node_id.shthis will give you the node id to use in sentry/seed set up.
- Follow node instructions.
- Setup Public Endpoints: ssl certs and nginx config to serve rpc and lcd endpoints over https.
- RPC endpoint works.
- Update
SEED_NODEin newnet/defaults.env. - Merge the changes to the genesis to testnets repo.
Sentry is optional, brings extra security. Not very important in a testnet env but good to have.
- Follow node instructions.
- Setup Public Endpoints: ssl certs and nginx config to serve rpc and lcd endpoints over https.
- RPC endpoint works.
Faucet - Also, you can optionally set up a faucet. However, you need to feed it with tokens so it has something to give out.
Block Explorer - You can optionally set up a block-explorer. forbole/big-dipper z