Nimbus v23.3.0
6 views
Skip to first unread message
zahary
Mar 10, 2023, 9:12:49 PM3/10/23
to nimbus-updates
Dear node runners,
We have a new release out!
Nimbus v23.2.0 is a low-urgency upgrade providing full support for the upcoming Capella hard-fork on the Goerli testnet. Keep an eye out for future mainnet releases!
https://github.com/status-im/nimbus-eth2/releases/tag/v23.3.0
You can now increase the resilience of your setup and eliminate any downtime during upgrade procedures of the execution client by allowing your Nimbus 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:
./run-mainnet-beacon-node.sh \
--el=http://127.0.0.1:8551 \
--el=ws://other:8551 \
--jwt-secret=/tmp/jwtsecret
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.
Happy Staking!
We have a new release out!
Nimbus v23.2.0 is a low-urgency upgrade providing full support for the upcoming Capella hard-fork on the Goerli testnet. Keep an eye out for future mainnet releases!
https://github.com/status-im/nimbus-eth2/releases/tag/v23.3.0
You can now increase the resilience of your setup and eliminate any downtime during upgrade procedures of the execution client by allowing your Nimbus 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:
./run-mainnet-beacon-node.sh \
--el=http://127.0.0.1:8551 \
--el=ws://other:8551 \
--jwt-secret=/tmp/jwtsecret
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.
Happy Staking!
Reply all
Reply to author
Forward
0 new messages