status-im/nimbus-eth2 v23.10.0

on GitHub

Notes

Nimbus v23.10.0 is a low-urgency upgrade focusing on stability and performance improvements. The performance improvements will be most impactful on networks with a large number of validators such as the Holešky testnet.

Improvements

• Faster attestation packing algorithm reduces the risk of orphaned block proposals:
  #5471

• Nimbus now adjusts its own the file descriptor limits on start-up in order to reduce the risk of running out of file descriptors:
  #5436

• The Keymanager API now imports keystores faster when they are encrypted with the same password and salt (this is typical for keystores produced by the staking-deposit-cli tool):
  #5443

• The Beacon API now emits the spec-mandated finalized field on all relevant endpoints:
  #5422

• Faster SSZ hashing speed reduces the overall CPU usage of the client:
  #5463

• The list of mainnet bootstrap nodes has been expanded:
  #5472

• A more efficient algorithm for calculating the list of block proposers during the epoch reduces the risk of missed validator duties during the first slot of the epoch:
  #5414

• Nimbus now produces more detailed error messages when it fails to load validator keystores:
  #5480

• The options --verifying-web3-signer-url and --proven-block-property can be used in place of --web3-signer-url to leverage the support for the experimental Verifying Web3Signer protocol extension:
  https://nimbus.guide/web3signer.html#verifying-web3signer
  #5504

Fixes

• A rarely occurring file descriptor leak was degrading the performance of Nimbus over time in certain environments:
  #5394

• Nimbus was not properly maintaining connectivity to peers specified through the --direct-peer option. Besides the format /ip4/<address>/tcp/<port>/p2p/<peerId-public-key>, the option now also accepts ENR addresses:
  #5427

• Nimbus was rejecting some valid sync committee contributions during the first slot of every sync committee period (once per 27 hours):
  #5408

• The Nimbus validator client will no longer crash when the indicated beacon node hostname cannot be resolved:
  #5388

• The fork-choice algorithm was performing certain computations multiple times:
  #5437

• Nimbus was sending unnecessary validator registrations to the builders when configured with multiple per-validator builder preferences:
  #5431

• The Nimbus validator client was not able to process responses from a Teku beacon node replying to the /eth/v1/validator/liveness/{epoch} endpoint, due to the presence of additional non-standardized fields:
  #5418

• The Beacon API was using non-compliant HTTP status codes in case of invalid requests to certain endpoints:
  #5422

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
8818443c1532e7bd9d6b46f16908238222e536d25d47f5b5b65d6edb41064b4cbf0ba4a36e3d2d32225a2af7bb0c363bd1fad944712de9ccfcc2cc8223657400  nimbus_beacon_node
e493288d010b802567381226deb244ae6d68ef80a36fd29a88b917ff7b0be7ebb7a55f52f4c80d1c7a1eb440863041bbeb3afdbe6010160a2bc54d1442480ff7  nimbus_validator_client
# Linux ARM64
cf807429fad047abd573b41ec7af40cd9dbc401ccfc98c75f9b8782c2acf37ebb7919479a5a1d4290057107da1704b6de185514776583f6b79132080010adc5e  nimbus_beacon_node
2444c594789587ab43d7309f9ae122b3893c8fde7b7e0a2e724dcfd15d18f1b15e1693cd34db7181cc55e4e5a0b8f7c454df0af94c565c72d21e25c78776173b  nimbus_validator_client
# Linux ARM
9fccc079cd043d4af381f60e01a9e11645c9a193655a04fe3c85ac681eb7af7c4f822f74dfc3793180d4e58fa4e7dc892dc52ad20722bd5cf9cd3ceafdc28fff  nimbus_beacon_node
83dbf314b85d091eb8cf0e188594f740e1141a9e43667f44bac957e1853bcc2d83d323d005e3f4c9e55c8894e84f6f34026222ec2fccbb16b5cd7e7b784801db  nimbus_validator_client
# Windows AMD64
c944c0c6f179be3f8afd62924c90bad9296b1415fb022254644fb6570e0f616a848a2270f994349633a1e47e157426828b14ccca5c8f18a5cc5efa6138be0eca  nimbus_beacon_node.exe
480efd2d7b98906d340f2460f732dc802ce901cbb381bebabc95d740fc69ecd4295782745fd821be17b63d841a7a4c8553d2e0cb0c9cebb97b48a4aa69815c80  nimbus_validator_client.exe
# macOS AMD64
129b1ceb58f1c70da1e06ed4517d9a794ae5b2f5decb9bfa794d5da2d7fd89957a5bfa4efe1cb2d12590eb8871a9ba9a4e279fb679a60ef634b437047f93315c  nimbus_beacon_node
4d5c87b0ffa0c81905f477501792e266ad9b7122fef6327559d0c122ef5c6ea5996a4256957f247e1673d5ed636b2eca55f787057e40719d2631cd001a02599c  nimbus_validator_client
# macOS ARM64
defb6771b93fa8b1536bb5c4381a68c9350ca41ea2d17aacf276ac072f5d80621af99d80bb23f95d7c1b958d08dbe18abfd9e8d73faf3303c4e53601bc3d7c8c  nimbus_beacon_node
25ad809e690b516af66c758dc39e1cc31d03fb843485ae74c1000b2467e82d2beb38e7271e3a88a4ef3156e4c0b4e8b9436edbd8b2654547c76f46cdbcc27f40  nimbus_validator_client