Validator Node Architecture

The System architecture of a validator node on the Energy Web Chain is made up of three components:

Parity Client: The parity client that connects the validator to the Energy Web Chain, collects transactions and proposes blocks according to the AuRa consensus algorithm. Read the documentation of the parity client here:

Node Control: Node Control is a small software client that interacts with the node control system contract and listens to events from the chain. It can be used to upgrade the parity client. Learn more here: Node Control Client. The use of node control is opt-in. Validators can disable it if they are comfortable with performing critical tasks on the node themselves and have personal dedicated to the maintenance of the node that are available and able to react fast whenever a critical problem is discovered. Update May 2020: Node Control was formally retired in November 2019 per the emergency operating procedure approved in the monthly governance vote. See Validator FAQ for more details. 

Telemetry: There is a monitoring system on the validator node that uses Telegraf to securely send telemetry to a InfluxDB that is connected to Grafana. Learn more here: Telemetry. The use of telemetry is opt-in. Validators can disable it if they have their own monitoring system in place that allows for real time tracking of all relevant metrics.

All components are run in separate docker containers managed by docker compose. For additional information on docker visit: and