From ca30f6a8a79acd5e3c764fcec350846e77275479 Mon Sep 17 00:00:00 2001
From: courtneyeh <courtney.hunter.nz@gmail.com>
Date: Tue, 5 Dec 2023 10:29:23 +1100
Subject: [PATCH] Add documentation for new CLI argument
 `--exit-when-no-validator-keys-enabled`

---
 docs/reference/cli/index.md | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/docs/reference/cli/index.md b/docs/reference/cli/index.md
index d552f67d2..ef2228717 100644
--- a/docs/reference/cli/index.md
+++ b/docs/reference/cli/index.md
@@ -456,6 +456,40 @@ doppelganger-detection-enabled: true
 
 Enables or disables [doppelganger detection](../../how-to/enable-doppelganger-detection.md). The default is `false`.
 
+## exit-when-no-validator-keys-enabled
+
+<!--tabs-->
+
+# Syntax
+
+```bash
+--exit-when-no-validator-keys-enabled[=<BOOLEAN>]
+```
+
+# Example
+
+```bash
+--exit-when-no-validator-keys-enabled=true
+```
+
+# Environment variable
+
+```bash
+TEKU_EXIT_WHEN_NO_VALIDATOR_KEYS_ENABLED=true
+```
+
+# Configuration file
+
+```bash
+exit-when-no-validator-keys-enabled: true
+```
+
+<!--/tabs-->
+
+When set to `true` Teku will fail to start when no validators have been loaded, and there are no active validators.
+
+Note: If the validator client and beacon node are being run seperately it only makes sense to add this option to the validator client side. This option should be used where you are loading the validator keys
+
 ### ee-endpoint
 
 <!--tabs-->