gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-04-30 11:13:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix cli text

Browse Source
This commit is contained in:
Mac L
2024-04-26 14:29:52 +10:00
parent 85443e8b19
commit 037448b0b0
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
book/src/help_vc.md
View File

@@ -83,6 +83,17 @@ OPTIONS:
--beacon-nodes <NETWORK_ADDRESSES>
Comma-separated addresses to one or more beacon node HTTP APIs. Default is http://localhost:5052.
--beacon-nodes-sync-tolerances <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 <CERTIFICATE-FILES>
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