The Vega network runs on a set of publicly maintained computers. A Vega network needs validator nodes that take part in consensus, as well as data nodes that receive and store network events that can be queried.
The more people run validators, the more robust the network will be. This is however limited by scalability of the underlying consensus protocol, and also requires some diversity properties (e.g., not all validators using the same cloud provider).
It is highly recommended that you have significant system administration experience before attempting to run your own validator node.
You must be able to handle and act on technical issues with your node. Being a validator involves more than just executing the Vega binary and self-staking.
Security, infrastructure, self-stake and active communication: Prospective validators on Vega must meet the requirements for their node infrastructure as well as building trust with the community.
Setting up and running a validator can be broken down into three parts:
- Setting up the server and building the software
- Configuring the components
- Joining the network and the validator set
Maintaining your node
To keep your node and its related components functioning and up-to-date, refer to the how-tos below.
|Restart network with checkpoints||This explains how to manage network restarts.|
|Restart from snapshots||This guide will take you through using the state snapshots.|
|Propose and execute a protocol upgrade||This guide describes how to propose a protocol software upgrade and then upgrade the network using Visor or manually.|
|Rotate Ethereum keys||This guide will take you through rotating your Ethereum key for security purposes.|
|Rotate Vega keys||This guide will take you through rotating your Vega key for security purposes.|
|Resolve common issues||This guide will describe issues you may encounter, and potential solutions.|