WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
Verify that your keystore file was imported successfully.
Replace<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS> with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable.
If you wish to customize a graffiti message that is included when you produce a block, add your message between the double quotes after --graffiti. Maximum length is 16 characters.
To exit and save, press Ctrl + X, then Y, then Enter.
Run the following to enable auto-start at boot time.
Check your logs to confirm that the validator clients are up and functioning.
sudojournalctl-fuvalidator|ccze
For example when using 2 validators, logs will show the following:
INFO Enabled validator voting_pubkey: 0x82b225f66476962b161ed015786df00a0b7b28231915e6d09e81ba8d5c4ae8502b6d5337e3bf101ad72741dc69f0a7cf, signing_method: local_keystore
INFO Enabled validator voting_pubkey: 0x95d39860a0d6ea3b92cba78069d21f3a987988f3b8417b14f0945353d79ed9e338bbe6e9d63d487abc044a710ce34866, signing_method: local_keystore
INFOInitializedvalidatorsenabled:2,disabled:0
Press Ctrl + C to exit the logs.
Example of Synced Lighthouse Validator Client Logs
Once the validator is active and proceeded through the validator activation queue, attestation messages will appear indicating successful attestations.
Notice the key words "INFO Successfully published attestations".
Feb 08 01:01:0 INFO Successfully published attestations type: unaggregated, slot: 12422, committee_index: 3, head_block: 0xabc111daedf1281..., validator_indices: [12345], count:1, service: attestation
Feb 08 01:01:30 INFO Connected to beacon node(s) synced: 1, available: 1, total: 1, service: notifier