Skip to content

Import your validator keys

Tip

systemd service file users will want to follow the service file guide instead!

Having followed the deposit guide, you will have a validator_keys folder containing several .json files in the nimbus-eth2 directory.

We'll import the signing key of each validator to the data directory using the deposits import command:

build/nimbus_beacon_node deposits import --data-dir=build/data/shared_mainnet_0

build/nimbus_beacon_node deposits import --data-dir=build/data/shared_prater_0

You'll be asked to enter the password you created to encrypt your keystore(s).

If your validator_keys folder is stored elsewhere, you can pass its location to the import command:

build/nimbus_beacon_node deposits import \
  --data-dir=build/data/shared_mainnet_0 \
  /path/to/keys

build/nimbus_beacon_node deposits import \
  --data-dir=build/data/shared_prater_0 \
  /path/to/keys

Replacing /path/to/keys with the full pathname of where the validator_keys directory is found.

On success, a message will be printed that your keys have been imported: 

NOT 2022-07-19 17:36:37.578+02:00 Keystore imported

NOT is short for NOTICE and not not :)

After importing keys, it's time to restart the node and check that the keys have been picked up by the beacon node.

Tip

You can read more about the different types of keys here - the deposit import command will import the signing key only.

Troubleshooting

If you come across an error, make sure that:

  • You are using the correct data directory
    • for systemd users, look for the --data-dir option in the .service file
  • You are running the command as the correct user
    • for systemd users, look for the User= option in the .service. Assuming the user is called nimbus, prefix all commands with: sudo -u nimbus
  • Permissions for the data directory are wrong