status-im/nimbus-eth2 v23.4.0

on GitHub

Notes

Nimbus v23.4.0 is a medium-urgency upgrade addressing a number of low probability risks for missed block proposals, bringing performance improvements in setups relying on the Nimbus validator client, and introducing some exciting new capabilities of the Nimbus light client and Builder API implementations.

Improvements

• Nimbus now obtains blocks from the configured builder and execution layer nodes without providing timing advantage to any source. You can use the newly added --local-block-value-boost option to give preference to the best block provided by an execution layer node, as long as its value is within the specified percentage of the value advertised by the best external builder. Setting this flag to a non-zero value is recommended because the usage of an external builder introduces an additional risk that the advertised block won't be published by the builder:

  #4749
  #4795
  #4847

• Nimbus now supports the standardized Builder API liveness failsafe mechanism:

  #4746

• The --sync-light-client option is now enabled by default, providing significant speedups in beacon chain syncing and re-syncing:

  #4805

• The trustedNodeSync command features a new --trusted-block-root option that leverages the Nimbus light client in order to minimize the required trust in the specified Beacon API endpoint. After downloading the state snapshot, the light client will verify that it conforms to the established consensus in the network. Note that the provided --trusted-block-root should be somewhat recent, and that additional security precautions such as comparing the state root against block explorers are still recommended.

  #4736

• Improved scheduling mechanisms in the Nimbus validator client deliver stability and performance improvements:

  #4743

• The deposits exit command can now be used to perform voluntary exits for multiple validators at once:

  #4855
  https://nimbus.guide/voluntary-exit.html

• Nimbus now supports the /eth/v1/beacon/states/{state_id}/randao REST API endpoint:

  #4799

• Nimbus now uses only the Capella-enabled engine_forkchoiceUpdatedV2 endpoint in all communication with the execution layer:

  #4817

Fixes

• Nimbus has addressed a risk of missed block proposal due to incorrectly computed withdrawals at epoch boundaries:

  #4820

• Nimbus has addressed a low probability risk of missed block proposals when the configured builder doesn't respond in time:

  #4764

• Nimbus has addressed a low probability risk of missed block proposals when a late block triggers a chain re-org while an engine_forkchoiceUpdated request to the execution layer is in flight:

  #4800

• Nimbus will no longer experience occasional response timeouts when performing a large number of concurrent HTTP requests (e.g. when configured to operate with a large number of remote keystores):

  status-im/nim-presto#44
  status-im/nim-chronos#324
  #4779

• The Nimbus validator client will no longer crash on start-up when supplied with incorrect beacon node configuration:

  #4765

• Nimbus will no longer crash when there is a network mismatch between the imported slashing protection database and the specified data directory:

  #4791

• Inactive validators will no longer affect the initial GossipSub topic subscriptions:

  #4793

• Failed or timed out request to engine_exchangeTransitionConfigurationV1 will no longer degrade the status of the connection to the execution layer:

  #4831

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
4e3987df2e15d11f9e3adb05fb8223b5db8e4cdee48c4e9480992a4a87c7fac9f0f307686bdc8b22e35543bf887888f563888b5fae818fca7fb846159f2ae4fa  nimbus_beacon_node
0de3d47636ce9e389b97b625e2c9b3aa416a3ce07f51a02733d0ecd2fa6bc907dc478feeb5b9e758b22bd0c9790a6ab178fbe2258292046e2663a637ceded937  nimbus_validator_client
# Linux ARM64
9c6adeffbf44f8975b54a300a50477459cd4ef4a3b2e867f7251ca2af5fab3f0a4a1ceaf99f1cbc898c21b7bc3d64fb5ec5f2b9e077f3661ff19d299dc2d6fa3  nimbus_beacon_node
6231b6cf5a4904e91d0b4dbccca32bfc2287af26a05c44884bf2f958df311f74f5fdc45961a653dc9650e84752ac43671d5f4f2dc73c2edcc14b22689837ecb4  nimbus_validator_client
# Linux ARM
b3334c9c6d532c720a415f547dbe16977a4e4761e5f1958f457082ae461aaac7fdb50980cb49681e48148ee02fac98a150d89acc033a6af65c990aca81c7d0ba  nimbus_beacon_node
ca2a4dc57c8994fed6c88af2af2c49dd4b074b18a0f928bbda41d3a60c4d990dbff8d0b778d613566c3199f1f564b68a5059b9d925886485ee5802373be514c8  nimbus_validator_client
# Windows AMD64
fe46d7b7162df01f2c7593a415a91ab73d37acca8cfff783526063e67db89445151df6e2647f17ee22a5b8e21a6bd787f01d034f39cdd92cbac2817dac7f9c1a  nimbus_beacon_node.exe
e940ea0a41beef3c7033f04cce38126d59603b9be3c63c723984f07e995c0ed5755f05bd98e0067fd64af74251014e7a1594aedc645e6924e6af279a5d4f817b  nimbus_validator_client.exe
# macOS AMD64
1d2741c0b8dec919576fa7d1e375d147f91f136e4e9f1b0d7e4f502d14ca801ba2676cec720023654f710b0d95c6e68ca7db339038d0878b79286720aa95b88b  nimbus_beacon_node
6128163f8d40f0330ae3a6a01bf8ef0072a7c81b526edfd4c18bc532c6c583897356bef23a2868eaf1e2286828f1957db98222712c8d2858887de59b531ed6c4  nimbus_validator_client
# macOS ARM64
027d16a6d3f25b7f5686ded8bbec34d5c95396d22e4a1d4886123da2b9f94aabd715898799623b28095a859fc7d953a21e5b6fd1b4f93d748da0202382831eac  nimbus_beacon_node
f3d0695f07bd401cebe4b232d2b8d6718543e9f7fa249c46257afa0cea4c2919ee639888a0a46883ffc5672968dba0215d2ffb286bc29ee7625f1bf0adc323ab  nimbus_validator_client