To import your signing key(s) into Nimbus, copy the
validator_keys directory -- the directory that was created for you when you generated your keys -- into
nimbus-eth2. Then run:
build/nimbus_beacon_node deposits import --data-dir=build/data/shared_pyrmont_0
build/nimbus_beacon_node deposits import --data-dir=build/data/shared_mainnet_0
Note: You can also specify a different path to your validator_keys directory as follows:
build/nimbus_beacon_node deposits import --data-dir=build/data/shared_pyrmont_0 "<YOUR VALIDATOR KEYS DIRECTORY>"
build/nimbus_beacon_node deposits import --data-dir=build/data/shared_mainnet_0 "<YOUR VALIDATOR KEYS DIRECTORY>"
<YOUR VALIDATOR KEYS DIRECTORY>with the full pathname of the
validator_keysdirectory that was created when you generated your keys using the command line app.
validator_keysdirectory to print the full pathname to the console (if you're on Windows, run
You'll be asked to enter the password you created to encrypt your keystore(s).
Don't worry, this is entirely normal. Your validator client needs both your signing keystore(s) and the password encrypting it to import your key (since it needs to decrypt the keystore in order to be able to use it to sign on your behalf).
When you import your keys into Nimbus, your validator signing key(s) are stored in the
build/data/shared_<TESTNET OR MAINNET>_0/ folder, under
validators - make sure you keep these folders backed up somewhere safe.
secrets folder contains the common secret that gives you access to all your validator keys.
validators folder contains your signing keystore(s) (encrypted keys). Keystores are used by validators as a method for exchanging keys. For more on keys and keystores, see here.
Note: The Nimbus client will only ever import your signing key -- in any case, if you used the deposit launchpad, this is the only key you should have (thanks to the way these keys are derived, you can generate the withdrawal key from your mnemonic whenever you wish to withdraw).