status-im/nimbus-eth2 v23.1.0

on GitHub

Notes

Nimbus v23.1.0 is a low-urgency upgrade, introducing support for on-the-fly database pruning making the storage requirements of Nimbus much more predictable on long-term time scales. When pruning is enabled, a typical beacon node expected to consume around 60 to 70 GB of storage. To take advantage of the new functionality without facing any downtime, users are advised to sync a fresh node through trusted node sync which now features a quicker history backfilling implementation.

Improvements

• After a trusted node sync, Nimbus requires less time to complete the block
  backfilling process by downloading the minimum number of historical blocks
  mandated by the spec:

  #4421

• Nimbus is able to sync in optimistic mode with the network even when not
  paired with an execution layer client. Please note that this mode is not
  suitable for validating:

  #4458

• A new --history=<archive|prune> configuration parameter controls the
  retention of old historic blocks in the database of the client. Enabling
  pruning on an existing installation will introduce a significant delay
  on the first run, while history pruning is taking place, so we recommend
  starting with a fresh database by executing a trusted node sync:

  https://nimbus.guide/history.html
  #4445

• The validator monitor is now considered out of BETA and enabled by default.
  To keep the number of created metrics to a reasonable level on installations
  with large number of validators, the default implies the previous behavior
  of the validator-monitor-totals flag:

  #4468

• Full support for the latest Capella/Shanghai devnets:

  https://notes.ethereum.org/@bbusa/Zhejiang#Nimbus

Fixes

• Out of date metadata for the Gnosis network bootstrap nodes:

  #4460

• Potential hanging of the client caused by inappropriate activation
  of the TTD block detection on beacon nodes created after the merge:

  #4486

• Inappropriate case-sensitivity in the --log-level parameter, accidentally introduced in the 22.12.0 release.

  #4523

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
7f362aa740007b4d84991c6b1ddd7d309b2b5a33969841a87f6c681976322078f5efddec85428363c822a35eaf5520605cc974edb58863b7e5506568459a473e  nimbus_beacon_node
d79df66d12ce904044a7fb2d4e8b86a722ba46b617b02bdd836aa710531ddf45fd5fb10d2f34403d24da59adc1d01d13d28670f0fce795b08aac7640de2fb4d6  nimbus_validator_client
# Linux ARM64
162a55dff1bd54b84e5aa3106e11c7a32866e7645f835f2a098d2db0ba1a3f0bd6e1a437ba9370d6f99acb38e43d8a5972b2fdf92fd87211b7cef1b15707cb14  nimbus_beacon_node
14bf497efc89427b9e636faeb2969edf24b1325be3fcd997de702e1ca18987fea6fb4a0a3e314a087287aa2d8ecb365745b4e1d00f64d2922bb96a056b58b2e2  nimbus_validator_client
# Linux ARM
f93ec36d94faa4aa045d363b27cf782ff0399d57aad9937ba3f0f22a0435873366f873987ead181e4c254938a2f539496f2aecda27686c2f63d037d7c19b3fdf  nimbus_beacon_node
c043d90d2b3fa32deb7ddb6735ee2941b641bacf9ed7dbc3093768c712df24b3c44dc7e50c45fbe772ca910dc88778c0a1a027bf0fdadc4e6c9a69aadd35fdb5  nimbus_validator_client
# Windows AMD64
98aec384a734f464544bad4741ed72458312b18b927b7cc1e98c4b1beb71d778f8de0d8e025fb0e29f813648e1696aedce794319ece834b8196e7c91a4b16d34  nimbus_beacon_node.exe
4c21b7e3411d7d2edec48ab1db98f73b2b80a191357c778c7cb88a35012398f04e7b2c1ba6cb34e26df477d167d70f4bbc196fa1c27fd9bb0e8dd07115e410b5  nimbus_validator_client.exe
# macOS ARM64
b68cf04e4f480dae3dff511a0359f7001d32853df0202108f0c1b62d100c30749a388b9fda78ead6e3ee2e26f527466f405851b0269c16a32f94442e357d2e9d  nimbus_beacon_node
09e93ccc56e0f4bc00730c008dd878f10cce4fa9a221de5865d938968daa80b6afa2f3fc03765bc8f70e7410dfa42567b6ef368c4831f2f9f1e52b894a950f06  nimbus_validator_client