2. Confirm that you have the recovery seed phrase information for the active key running on the old machine
lavad keys export mykey
This prints the private key that you can then paste into the file
mykey.backup
lavad keys list
lavad keys add mykey --recover
lavad keys import mykey mykey.backup
lavad status 2>&1 | jq .SyncInfo
catching_up
should be equal tofalse
To prevent double signing, you should stop the validator node before stopping the new full node to ensure the new node is at a greater block height than the validator node If the new node is behind the old validator node, then you may double-sign blocks
sudo systemctl stop lavad
sudo systemctl disable lavad
The validator should start missing blocks at this point
sudo systemctl stop lavad
After being copied, the key
priv_validator_key.json
should then be removed from the old node's config directory to prevent double-signing if the node were to start back up
sudo mv ~/.lavad/config/priv_validator_key.json ~/.lavad/bak_priv_validator_key.json
sudo systemctl start lavad
The new node should start signing blocks once caught-up
lavad tx slashing unjail --chain-id $LAVA_CHAIN_ID --from mykey --gas=auto -y