docs: add comments and docs for why nimbus use consensus client on importKeys

stdevMac · stdevMac · commit daa9bce7ba58 · 2024-10-07T17:50:03.000+04:00
diff --git a/cli/slashingImport.go b/cli/slashingImport.go
@@ -93,6 +93,9 @@ sedge slashing-import --from slashing-data.json --start-validator lighthouse`,
 		},
 		RunE: func(cmd *cobra.Command, args []string) error {
 			services := []string{validator}
+			// If the validator client is nimbus, we need to import the consensus service as well
+			// The consensus service is not imported by default because it's not necessary for the other clients
+			// On Nimbus, the consensus service is necessary to import the slashing protection data
 			if validatorClient == "nimbus" {
 				services = append(services, consensus)
 			}
diff --git a/docs/docs/commands/importKey.mdx b/docs/docs/commands/importKey.mdx
@@ -118,6 +118,8 @@ The resulted folder structure is:
 
 If you have to import your keys to nimbus, you will need to manually type the password when loading the keys, since the nimbus client does not support non interactive password loading.
 
+Importing keys on Nimbus is done using the consensus client container instead of the validator client container.
+
 :::
 
 Notice the new folder `keystore` inside the `sedge-data` folder, this is where
