Network Operations

Checklist for a new network

TODO: validator, sentinel, failover nodes (0downtime), load balancers with HTTPS/WSS, generate genesis, create network config, create peer list in the config

Setting up the (virtual) machine to run the leap-node

TODO: leap-node, logging, systemd service, firewall/security groups

Setting up AWS Load Balancer for JSON RPC nodes

TODO

How to setup the network for 0-downtime upgrades

https://github.com/leapdao/leap-node/issues/185#issuecomment-468921734

TODO: add image with network topology (load balancer for sentinels, two validators in intranet etc)

How to migrate validator to the new network

if you start a validator for a new network keeping the old validator key, be sure to remove old validator state. In older tendermint version the state is kept in priv_validator.json file along with the key you want to preserve.

1. For older tendermint — edit priv_validator_key.json
2. For new tendermint — just run the node with --fresh key (it will reset the state which is in a separate file from now on)

if you start a new network and upgrade to newer tendermint at the same time, then either a) use the 1 option before you run the upgrade leap-node for the first time. b) run updated node so that priv_validator structure is updated, stop the node, run it with --fresh, then start normally

How to check the validator is submitting periods

TODO

How to add new validator (PoA)

TODO: checklist for new validator, generate validator key with some ETH, call setSlot via governance