Configuring Validators in a Production Network
As when configuring bootnodes:
- Create the node key pair (that is, the private and public key) before starting the validator.
When creating validators in the cloud (for example, AWS, Azure), attempt to assign a static IP to them. If your network is:
- Publicly accessible, assign an elastic IP.
- Internal only, specify a private IP address when you create the instance and record this IP address.
We recommend validator configuration is stored under source control.
Number of Validators Required
Ensure sufficient validators are configured to allow for redundancy. The number of faulty validators that can be tolerated when using IBFT 2.0 is:
f = (n-1)/3
- f = number of faulty validators
- n = number of validators
Adding and Removing Validators
Validators are voted in or out of the validator pool.
Validators as Bootnodes
Validators can also be bootnodes. Other than the usual configuration for bootnodes no additional configuration is required when a validator is also a bootnode.
If a validator is removed that is also a bootnode, ensure there are enough remaining bootnodes on the network.