validator-migration-steps

# Before migration

1 - Spin-up new instance

2 - Install gaia v2.0.8 on new instance

3 - Sync new instance

4 - Establish rsync connectivity between new and old instances

5 - Establish rysnc bewtween new validator and chainflow-sentry-200

6 - Confirm priv_validator_key.json and node_key.json on old instance are backed-up

7 - Create .gaiad/data/ backup, excluding priv-validator-state.json file, on new instance, before migration

8 - Continue syncing new instance

# During migration

## On old instance

9 - Stop gaiad on old instance

10 - Confirm gaiad is stopped

11 - Disable gaiad.service on old instance

12 - Close port 26656 on old instance

13 - Confirm port 26656 is closed on old instance

14 - Back-up priv_validator_key.json, node_key.json and priv_validator_state.json.
    
## On new instance

15 - Confirm new instance synced to height higher than old instance

16 - Stop gaiad on new instance

17 - Close port 26656 on new instance

18 - Disable gaiad.service on new instance

19 - Confirm gaiad on new instance disabled

20 - Migrate priv_validator_key.json, node_key.json and priv-validator-state.json to new instance

21 - Confirm correct versions of priv_validator_key.json, node_key.json and priv-validator-state.json are in place

## On old instance

22 - Confirm old instance is shut down completely

## On new instance

23 - Open port 26656 on new instance

24 - Enable gaiad.service on new instance

25 - Start gaiad on new instance