docs - configuration/network - add p2p/max_bootstrap_attempts
-
-There's 2 differents network interfaces which are covered by their respective section:
+There are 2 different network interfaces which are covered by their respective section:
```yaml
rest:
@@ -95,6 +94,13 @@ rest:
- `topology_force_reset_interval`: (optional) If this value is set, it will
trigger a force reset of the topology layers. The default is to not do
force the reset. It is recommended to let the protocol handle it.
+- `max_bootstrap_attempts`: (optional) number of times to retry bootstrapping from trusted peers.
+ If not set, default beavior, the bootstrap process will keep retrying indefinitely, until completed successfully.
+ If set to *0* (zero), the node will skip bootstrap all together -- *even if trusted peers are defined*.
+ If the node fails to bootstrap from any of the trusted peers and the number of bootstrap retry attempts is exceeded,
+ then the node will continue to run without completing the bootstrap process.
+ This will allow the node to act as the first node in the p2p network (i.e. genesis node),
+ or immediately begin gossip with the trusted peers if any are defined.
### The trusted peers
@@ -113,7 +119,7 @@ You can generate a public id with **openssl**, for example: `openssl rand -hex 2
This is optional an optional value to set. The default is:
-```
+```yaml
messages: low
blocks: normal
```
@@ -123,14 +129,14 @@ that are not even publicly reachable.
However for a publicly reachable node, the recommended setting would be:
-```
+```yaml
messages: normal
blocks: normal
```
and for a stake pool
-```
+```yaml
messages: high
blocks: high
```
