status-im/nimbus-eth2 v23.3.0

on GitHub

Notes

Nimbus v23.3.0 is low-urgency upgrade bringing full support for the upcoming Capella hard-fork on the Goerli testnet. Keep an eye out for future mainnet releases!

Improvements

• 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:

  ./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.

  #4465
  https://nimbus.guide/eth1.html

• The metrics engine_api_responses, engine_api_request_duration_seconds and engine_api_timeouts provide statistics about latency and response status codes for all requests sent to each individual execution layer URL:

  #4465
  #4707

• Nimbus will now attempt to connect to a locally running execution client even when the options --el and --jwt-secret are not specified. This is made possible by the following proposed standard:

  ethereum/execution-apis#302

  Please note that the standard hasn't been implemented in any execution client yet.

• Nimbus now support the latest version of the Builder API, adding support for the Capella hard-fork:

  #4643

• Improved diagnostic messages and more spec-compliant behavior of the Nimbus validator client when being paired with a non-synced or optimistically synced beacon nodes:

  #4643
  #4657
  #4673

• The Sqlite3 database engine has been upgraded to version 3.40.1:

  #4649

Fixes

• The doppelganger detection now acts safer after a period of lost network connectivity

  #4616

• The doppelganger detection now acts safer in the presence of out-of-order responses from the beacon node:

  #4691

• Nimbus can now export ERA files for the Sepolia network:

  #4689

• The --history=prune mode will no longer interfere with serving light client data for the full retention period as mandated by the spec:

  #4702

• Nimbus now downloads a longer range of recent execution blocks in order to avoid potential situations where our Eth1Data votes fail to agree with the honest majority in the network:

  #4588

• Nimbus has addressed a potential interruption of deposit syncing when connected to Geth over WebSocket:

  #4708

Urgency guidelines

low-urgency: update at your own convenience, sometime within our normal update cycle of two weeks

medium-urgency: may contain an important stability fix, it is better to update sooner rather than later

high-urgency: update as soon as you can, this is a critical update required for Nimbus to function correctly

SHA512 checksums

# Linux AMD64
70b56b802e57be9b0aa4e576ad9055775f95adc15c2cc23376cc3f97684bf52b8c84fa31194ba0c3f6bb5fdb8872d8edf446e6925959f11e6db5e9648e5210fe  nimbus_beacon_node
8718aa14417008a122fc67269e0a0dbef606aedec3fdf1bc2b7bd89935bd785d5d09d0eacd148169e3920b948456fad3a0077bf96819820af2d0cb5026631dd0  nimbus_validator_client
# Linux ARM64
1f4f9371610c8e3c7fdcae509a7d1b0f2169221c796a528bf15452dcb5b0ba0784feb1bcdfebf26674d6e89cef04519f0f3cd089f5a486eac68a409317fa7ef4  nimbus_beacon_node
670baab845834962f90ba515d75e8353e16a1937403fdb886bccf41caa6deb0b62186c32862faa474235f975db3197c1fe8319d61f45d17bbae60e5edbbe9322  nimbus_validator_client
# Linux ARM
0fbf0925c4d12d3c97accfcab87d5a18b9d6846a032be2bcb3d3c8fa9c43b5d46f6cbd9cbc2ba200b8dff113e7b120cb1aad87c05ffa9b12694d3d4625e3bbfa  nimbus_beacon_node
25b0279c3d83042c9ad7fa1df5c3d26d145167fc51f63c5a37524599c8527f51a22c482b65b0786f7d50d66fd06a287f402667c69aa025776119f728dc1d6b96  nimbus_validator_client
# Windows AMD64
294aa8b58c45b80b26686909bdc8f4ce3b3ba1511209a6383dd73b600b1a32675c4de1981028d5f1cf9575a59ef28abac39c73f455357df06a0ca20a73c00e48  nimbus_beacon_node.exe
a8c0093f9cbf02e4e7019ab388bb19c8133c5e10240f0a968a2850aec9fb96e11f69ac8909f6ab9f855a8755934888165484d43ca2f35047af8c7c45ca148466  nimbus_validator_client.exe
# macOS ARM64
af59df6a78cb971863e6efb81d363a96d2935d0bd1fed530d53d06b39b8963e1da01191b350bbdabcf112c4a1ce36c0946f9db3995bfbf36f99d23d726dbb322  nimbus_beacon_node
b2856143952a08f3308ad41b3374f6e350a79381dc44c7fbeb8c49c9873398bcda1bca61ca80713781758e7ed90f095e70f7c4d6cea1fee899756e4e1b91f1cc  nimbus_validator_client