From 037448b0b0a257f9901cc19e2439ce0c7458391b Mon Sep 17 00:00:00 2001 From: Mac L Date: Fri, 26 Apr 2024 14:29:52 +1000 Subject: [PATCH] Fix cli text --- book/src/help_vc.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/book/src/help_vc.md b/book/src/help_vc.md index 1b7e7f2b0a..ede8e5d9b2 100644 --- a/book/src/help_vc.md +++ b/book/src/help_vc.md @@ -83,6 +83,17 @@ OPTIONS: --beacon-nodes Comma-separated addresses to one or more beacon node HTTP APIs. Default is http://localhost:5052. + --beacon-nodes-sync-tolerances + A comma-separated list of 3 values which sets the size of each sync distance range when determining the + health of each connected beacon node. The first value determines the `Synced` range. If a connected beacon + node is synced to within this number of slots it is considered 'Synced'. The second value determines the + `Small` sync distance range. This range starts immediately after the `Synced` range. The third value + determines the `Medium` sync distance range. This range starts immediately after the `Small` range. Any sync + distance value beyond that is considered `Large`. For example, a value of `8,8,48` would have ranges like + the following: `Synced`: 0..=8 `Small`: 9..=16 `Medium`: 17..=64 `Large`: 65.. These values are used to + determine what ordering beacon node fallbacks are used in. Generally, `Synced` nodes are preferred over + `Small` and so on. Nodes in the `Synced` range will tie-break based on their ordering in `--beacon-nodes`. + This ensures the primary beacon node is prioritised. [default: 8,8,48] --beacon-nodes-tls-certs Comma-separated paths to custom TLS certificates to use when connecting to a beacon node (and/or proposer node). These certificates must be in PEM format and are used in addition to the OS trust store. Commas must