status-im/nimbus-eth2 v23.2.0

on GitHub

Notes

Nimbus v23.2.0 is a low-urgency upgrade providing full support for the upcoming
Capella hard-fork on the Sepolia testnet. Keep an eye out for future mainnet releases!

Improvements

• Status now provides an APT repository that will host the latest version of the
  Nimbus beacon node and validator client software:
  https://apt.status.im/

• The deposits import command now provides the option --method=single-salt which
  will significantly improve the keystore loading speed on start-up on beacon nodes
  and validator clients running with a very large number of validators. Please see
  the documentation provided in the Nimbus guide in order to understand the security
  implications of using the option:
  https://nimbus.guide/keys.html#optimised-import-for-a-large-number-of-validators
  #4372

• More efficient sync committee caching strategies bring 20-30% of syncing
  speed improvement post Altair:
  #4592

• Nimbus performs fewer interactions with the EL node during optimistic syncing
  which further improves the syncing speed:
  #4591

• The Keymanager API now supports all gas_limit end-points:
  https://ethereum.github.io/keymanager-APIs/#/Gas%20Limit
  #4612

• Nimbus serves light client updates up to the retention period mandated by
  the spec even when pruning is enabled:
  #4499

• The Linux packages of Nimbus no longer depend on lsb-release:
  #4597

• The list of bootstrap nodes for the Gnosis network has been expanded:
  #4603

• Nimbus now performs fewer forkchoiceUpdated Engine API calls with lower risk
  of reporting conflicting data to the EL node:
  #4609
  #4614
  #4623

Fixes

• Nimbus will no longer suffer from performance issues when a large number of
  non-active validators are imported in the beacon node or the validator client:
  #4590

• Nimbus will no longer crash when it fails to resolve the hostname of a remote
  validator imported through the Keymanager API:
  #4590

• The Nimbus validator client won't attempt to perform sync committee duties when
  the attached beacon node is only optimistically synced:
  #4622

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
f9a694ed11ef47612c56db5e7c7738956b85619cfd5df57d81b442d224d582ee1ad35d2caefc36da158cdf8ea474e50d244db61b3ebcd29233b6bfd5aacfae72  nimbus_beacon_node
84cec09bed52e347ea4c793fdac54e1c63af6803f1a47ec066ecf175e09a2ead707ea8f807a749d850f4a86e9e4136bf6335aa8fb58000846160a05957959ffb  nimbus_validator_client
# Linux ARM64
42a4dc5043fd11612ebb1cb0e7b075a16f7b6ca875b6c2dfdd5135eb30a7f79e4c8767659dc027a70ea439bbc8d8b6e69c9d672e4ba4de62e59d56710b539f69  nimbus_beacon_node
4597fb3b5386218b7d27e70647127c2ddcc861c4044425555b11cdc64879dc2d6887dcc8a5d97354ff5d8157e8f5fc240a1658be7c19e67b3484b05be085d6dd  nimbus_validator_client
# Linux ARM
a259637b31695d33e4da57e010b9c57652918a26d8ea57dd8f54966dd93018c8cc0b4cef6b9e28f3df5c8e4543892a6c8435fc8c52767da9c46a6f1a4fadaa58  nimbus_beacon_node
6a214cc3a2ca1166c142f71b6d2fc363a93dc99ccc04e89417f7f2ef5cc0fb277e727118fd8a5c5e7c8a9587adaa88a139c34d79bee79ea4530902f730f91a0e  nimbus_validator_client
# Windows AMD64
2b37b70739f19e7ff19b799a0bd85bbb52bf91994f0cf6357f6e1e2df47c489dd6667cfdbf3fb8406dad59af7e263f251828c04c64dc0dd8a218814cb12e0411  nimbus_beacon_node.exe
6a7deced63cfb7f09e5bc99bdfe9182cd299e94cb74980c5a914710bd9829067e235ea4e28ec071fdf7ee95b9e20209313f5f7b70518fe9d0da1e466881a5120  nimbus_validator_client.exe
# macOS ARM64
7db94cc35fcfe8c918ea81248151a36763c7a01f26efcfd60ed0f7a2c96864ad24c247caf4d290f07faca857bd71e82c669db92a8580c079fbf4c8f63ba3e0ba  nimbus_beacon_node
2d24c0a29f86a9d99473ea0b40629d36e394a2fa270f3f77ec6fc67d90cadb5977a757d7088141cb739741e36dd136e7dca2eac00d5793d856d69a15c33e9139  nimbus_validator_client