Teku
Teku validator client's data directory structure before imports.
Import validator keys
Teku doesn't have import command therefore it doesn't use a container. The client will read and import keystores from directory specified using --validator-keys flag passed to the Validator client. By default Nimbus deployed using slingnode.ethereum will point to the same directory for keys and the keystore password.
The role copies the keystores and passwords to the keystore directory on the server and restarts the container. Teku imports the keystores when it starts.
From Teku docs:
Directory or file to load the encrypted keystore file(s) and associated password file(s) from. Keystore files must use the .json
file extension, and password files must use the .txt
file extension. When specifying directories, Teku expects to find identically named keystore and password files. For example validator_217179e.json
and validator_217179e.txt
.
Data directory structure after keys import
There's no changes to the file layout.
Slashing protection db import
Import command output
Slashing protection DB export
Export command output
Last updated