Run a separate validator client
This feature is currently in BETA - we are still testing it and implementation details may change in response to community feedback. We strongly advise against using it on mainnet - your validators may get slashed
By default, Nimbus integrates the validator client into the main beacon node process - this is a simple, safe and efficient way to run a validator.
Advanced users may wish to run validators in a separate process, allowing more flexible deployment strategies. The Nimbus beacon node supports both its own and third-party validator clients via the built-in REST API.
So far, all slashings with known causes have been linked to overly complex setups involving separation between beacon node and validator client! Only use this setup if you've taken steps to mitigate the increased risk.
To run a separate validator client, you must first make sure that your beacon node has its REST API enabled - start it with the
Next, choose a data directory for the validator client and import the keys there:
Do not use the same data directory for beacon node and validator client - they will both try to load the same keys which may result in slashing!
If you are migrating your keys from the beacon node to the validator client, simply move the
validators folders in the beacon node data directory to the data directory of the validator client
With the keys imported, you are ready to start validator client:
See the validator client options page for more information about beacon node roles, redundant setups and sentry nodes!