Vega node how-to guides

📄️ Propose & execute upgrades

The protocol upgrade feature allows node operators to automatically update nodes to a new version of the Vega protocol.

📄️ Use snapshots

Snapshots are a mechanism that allow a node be restarted, or join the network from an empty state, without having to replay the whole chain from genesis. A snapshot is taken by the network periodically, after a set number of blocks. The frequency is based on the network paramter . It contains all of a node's active state for that particular block. Every node participating in the network will produce identical snapshots and they will be stored locally on each node's machines.

📄️ Rotate Ethereum keys

Ethereum key rotation is a safety feature that allows validator nodes to manage their Ethereum keys. Every validator node in the network needs three keys: Ethereum, CometBFT and Vega. This section described to how to dynamically rotate a node's Ethereum key.

📄️ Rotate Vega keys

Vega key rotation is a safety feature that allows validator nodes to manage their Vega keys. Every validator node in the network needs three keys: Ethereum, CometBFT and Vega. This section described to how to dynamically rotate a node's Vega key.

📄️ Maintain multisig contract

The Multisig Control contract contains a set of signers whose signatures are required to complete actions on the Ethereum bridge. The set of signers on the contract should match the set of consensus validators in the network. As validators join or leave the network and the set of consensus validators on a network changes, the signer set on the Multisig Control contract must be updated alongside those changes to maintain the security of the bridge.

📄️ Resolve common issues

Below is a list of common issues with running validator and data nodes, and their solutions.

📄️ Save disk space

Clean up and disable the CometBFT indexer