status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Some tweaks to the release notes

This commit is contained in:
Zahary Karadjov 2023-03-11 04:09:39 +02:00
parent 9906a0d5a2
commit 1a8b182d98
No known key found for this signature in database
GPG Key ID: C1F42EAFF38D570F
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -5,7 +5,7 @@ Nimbus `v23.3.0` is `low-urgency` upgrade bringing full support for the upcoming
### Improvements
* You can now increase the resilience of your setup and eliminate any downtime during upgrade procedures of the execution client software by allowing your beacon node to manage multiple execution clients. To enable this mode, just specify multiple URLs through the `--el` option (alias of `--web3-url`) when starting your beacon node:
* You can increase the resilience of your setup and eliminate any downtime during upgrade procedures of the execution client by allowing your beacon node to manage multiple execution clients. To enable this mode, just specify multiple URLs through the `--el` option (alias of `--web3-url`) when starting your beacon node:
```sh
./run-mainnet-beacon-node.sh \
@ -14,7 +14,7 @@ Nimbus `v23.3.0` is `low-urgency` upgrade bringing full support for the upcoming
--jwt-secret=/tmp/jwtsecret
```
As long as only one of execution clients remains operational and fully synced, Nimbus will keep performing all validator duties.
As long as any of execution clients remains operational and fully synced, Nimbus will keep performing all validator duties. To carry out an upgrade procedure without any downtime, just restart the execution clients one by one, waiting for each instance to re-sync before moving to the next one.
If you use this mode with different execution client implementations, Nimbus will act as an execution layer consensus violation detector, preventing the publishing of blocks that may trigger a catastrophic partitioning in the network.

2
docs/the_nimbus_book/src/eth1.md
View File

@ -106,7 +106,7 @@ You can increase the resilience of your setup and eliminate any downtime during
!!! tip
You can use a different secret for each connection by specifying `jwtSecret` or `jwtSecretFile` as a query parameter in the anchor section of the URL (e.g. `http://127.0.0.1:8551/#jwtSecret=0x12345...` or `http://127.0.0.1:8551/#jwtSecretFile=/tmp/jwtsecret`).
As long as only one of execution clients remains operational and fully synced, Nimbus will keep performing all validator duties.
As long as any of execution clients remains operational and fully synced, Nimbus will keep performing all validator duties.
!!! tip
To carry out an upgrade procedure without any downtime, just restart the execution clients one by one, waiting for each instance to re-sync before moving to the next one.