Vega networks support restarts using checkpoints. Checkpoints are a minimal save of the state of the network every N block, or, after funds are moved in or out of the network. They are both a way of restarting a clean chain with the current view of all accounts balances, and a security measure in order to not misplace any funds in case of a major issue that would require a restart of the chain.
This guide is valid for a network restart with version 0.50
Step -1: Verify your node wallet keys (to do before any following steps)
In a recent version of the Vega core, validation has been added at runtime to ensure the keys that validators have set up in the genesis block matches those saved in the node wallet.
Do this by by running the following command:
vega genesis new validator --tm-home="/path/to/tendermint/home" --home="/path/to/vega/home" --country="any" --info-url="any" --name="any"
The 3 flags
--country, --info-url, --name here are placeholders to run the command, only the output is important
The output of the command should look similar to this:
Enter node wallet passphrase:
Info to add in genesis file under `validators` key
Info to add in genesis file under `app_state.validators` key
You should the verify that your validator information set in the genesis file matches the one from the output of the command. In particular, your Tendermint public key (
plmxJSjg5IC7r8yLWBQUFFTosvXC+rTpbXgf0kCoqoY= here), Vega public key (
ec066610abbd1736b69cadcb059b9efdfdd9e3e33560fc46b2b8b62764edf33f here) and Ethereum address (
0xDdF662BBb29EB7a42340E426A75dd13337E482fc here) need to match.
Should there be a difference between the keys in the genesis file and those in the output of the command, this should be raised on Discord.
Step 0: Edit configuration
You can prepare your configuration but you may not want to update your mainnet node with the configuration before it's stopped.
Add the Tendermint public key to your node wallet
The node wallet now requires your Tendermint public key. You can save this key by running the following Vega command:
vega nodewallet --home="/path/to/vega/home" import --chain=tendermint --tendermint-pubkey="YOUR_TENDERMINT_PUBKEY"
Update the Vega configuration
New fields have been added to the Vega configuration. We recommend you generate a new default config and ensure that no sections are missing from the configuration if the default is not as required for your specific configuration.
The configuration must specify if a node is running as a validator or not. If you are running a Vega validator node (taking part in Tendermint consensus) add the following line to the Vega configuration:
NodeMode = "validator"
Update the data-node configuration
For the Vega configuration, new fields have been added in the data-node configuration. We recommend you generate a default one to compare with what you used.
The Vega node connected to the data-node should add the following line to its config:
NodeMode = "full"
The data-node configuration supports SSL for the HTTP connection. It is highly recommended that SSL is setup on the data-node as this enables GraphQL subscriptions, which are used by frontend dApps.
This can be set up in the following section of the data-node:
Level = "Info"
Timeout = "5s"
SubscriptionRetries = 3
GraphQLPlaygroundEnabled = true
Port = 3007
IP = "0.0.0.0"
Port = 3008
IP = "0.0.0.0"
Enabled = true
ComplexityLimit = 0
HTTPSEnabled = false # from here
AutoCertDomain = ""
CertificateFile = ""
KeyFile = "" # to there
Port = 3009
IP = "0.0.0.0"
Enabled = true
APMEnabled = true
If you do not want to enable SSL, ensure
HTTPSEnabled is set to false or the data-node will not start properly.
Step 1: Stop the network
Wait for a new checkpoint file to be produced, then stop all the nodes of the network (Vega, data-node and Tendermint). Once stopped, back up all Tendermint chain data and Vega data.
Save the selected checkpoint file in a safe location. You will need to reuse it later.
You can locate all your nodes' checkpoint files under:
You can also get a list of all paths used by your node using
vega paths list. The checkpoints folder path is
CheckpointStateHome within this list.
You can now remove all previous states of the chain by running:
vega unsafe_reset_all --home="/path/to/vega/home"
vega tm unsafe_reset_all --home="/path/to/tendermint/home"
rm -rf "/path/to/data-node/home/vega/data-node/storage/"
The exact path of the data-node folder to remove can be found using
vega paths list. The required path is
DataNodeStorageHome in the list.
Step 2: Update the genesis file
One of the validators will now need to update the genesis file with the following information:
- The new start date of the network
- The new network ID
- The hash of the checkpoint file to be used
This should be done via a pull request on the networks repo and ideally approved by 2/3+1 of all validators.
Step 3: Restart the network
This is a critical step that needs to be done with all validators synchronously. (This will not be needed in future updates).
All validators need to restart their node in a synchronous way. This is required as the network needs to synchronise its state with the Ethereum state in relation to the Vega token delegation to the Vega network.
This is done during the bootstrapping period, which happens during the first
N blocks of the chain (
N can be configured in the genesis file).
During the bootstrapping no transactions from users can be emitted other than the transaction to submit the checkpoint. This should be done only once by one of the validators using the following command:
vega checkpoint restore --home="/path/to/vega/home" --passphrase-file="YOUR_NODEWALLET_PASSPHRASE_FILE" --checkpoint-file="/path/tothe/
Once this is done, you will need to monitor the network to make sure all delegation are recovered properly by the end of the bootstraping period.
The Ethereum event forwarder is no longer required. This should be removed from your infrastructure and not started. This service has been re-written and is now integrated in the Vega core node.