status-im/nimbus-eth2 v23.5.1

on GitHub

Notes

Nimbus v23.5.1 is a medium-urgency point release improving the compatibility of Nimbus with 3rd party validator clients and beacon nodes and introducing the support for incremental pruning. If you are still not using the --history:prune option, we recommend testing it in a non-production environment, as it will be enabled by default in our next release.

Breaking changes

• The Nimbus validator client no longer accepts under-specified beacon node URLs that doesn't include a port number or a protocol scheme. When a protocol scheme is specified, Nimbus now uses the default port for the selected protocol (80 for HTTP and 443 for HTTPS):
  #4921

Improvements

• The history pruning is now incremental and no longer results in start-up delays when the --history:prune option is enabled on an existing node:
  #4887

• Nimbus now uses the withdrawal address of the validator as a default choice for the fee recipient address if the user has not provided any value in the configuration:
  #4968

• Nimbus now supports the upcoming Capella hard-fork in the Gnosis network:
  #4936

Fixes

• The Capella-related properties MAX_BLS_TO_EXECUTION_CHANGES, MAX_WITHDRAWALS_PER_PAYLOAD, MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP and DOMAIN_BLS_TO_EXECUTION_CHANGE were missing from the /eth/v1/config/spec REST API end-point:
  #4925

• The /eth/v1/validator/blinded_blocks/{slot} was supplying incorrectly encoded response when requested to return SSZ data:
  #4943

• The safety checks associated with the --weak-subjectivity-checkpoint parameter are now compliant with the latest Ethereum specs:
  #4923

• The Nimbus validator client was using HTTP pipelining which is not supported by all beacon node implementations:
  #4950

• The "Connection to EL node degraded" warning is now printed only after sufficiently persistent connectivity issues with the EL client:
  #4960

• After being only briefly disconnected from the execution layer client, the Nimbus beacon node was prematurely setting the execution_optimistic flag when returning validator duties:
  #4955

• Nimbus now allows the builder to respond 500ms later than the spec-mandated timeout in order to account for possible additional delays introduced by proxies such as mev-boost:
  #4964

• During sync committee period transitions, for a brief period of time there was a low risk of producing an invalid sync committee contribution:
  #4953

• Nimbus v23.5.0 introduced an unintended backwards-incompatible change in the parsing of remote keystores which is addressed in this release:
  #4967

Nimbus v23.5.0 was a medium-urgency upgrade that addresses a critical issue which was introduced in the previous version (v23.4.0). The issue was causing missed block proposals for users who were utilizing an external builder.

Improvements

• After Nimbus completes a trusted node sync executed with the --trusted-block-root flag, it will enable signature verification of all backfilled blocks, thereby reducing the assumed trust in the specified beacon node URL to merely expected data availability rather than expected data authenticity:

  #4858

• The /eth/v1/node/syncing BeaconAPI endpoint now supports the standardized el_offline property:

  #4860
  ethereum/beacon-APIs#290

• The secp256k1 library has been upgraded to version 0.3.1.

• Nimbus now supports an experimental extension of the Web3Signer protocol, allowing the signer server to verify certain properties of the signed block, such as the specified fee recipient:

  https://nimbus.guide/web3signer.html#verifying-web3signer
  #4775
  #4912

Fixes

• Nimbus was submitting blocks with incorrect state root to the attached external builder which resulted in missed block proposals:

  #4889

• Nimbus was skipping block proposals due to an inappropriate triggering of the slashing protection logic when an external builder was providing a block with insufficient value to be selected under the new --local-block-value-boost mechanism:

  #4894

• Nimbus was crashing after certain unsuccessful requests to the external block builder:

  #4890

• The Nimbus validator client was failing to perform sync committee duties when attached to multiple beacon nodes and when some of them were only optimistically synced:

  #4878

• The --trusted-block-root option was not visible in the trustedNodeSync help listing:

  #4859

• Nimbus was experiencing sporadic request time outs when being connected to the execution client over HTTP. Under specific circumstances this was introducing risk for missed attestation:

  d784672

• The required traffic to the execution client was reduced by preventing the sending of the same block multiple times:

  #4850

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
167efeda92d632db183601ef35f3286edf4f17a333b9f8f5cc9124b1bceb104c3cc4a39ba3174133c01199c5b620b45bffdfb33b9c16f408ca45f39fadd9e5cb  nimbus_beacon_node
3a1d319ec2a5114a164d24fe8f3ccd79eae3277bf52db3befef74bad7dd62c690f1612300d8eb0236ecab009eecca1d62da72fa17ce93fd13025ce8b19e68a3c  nimbus_validator_client
# Linux ARM64
8c9315045d3f15db5cdc513c9620406e502f740f9b119d083a8a1716c76ba8f25387720ea15f08c979f5cf49a366ca0cdec5a339f0e34cc8f2f705209e892015  nimbus_beacon_node
5ead09a4bca13dcbf49f9cfdab6376c616d3b5e426eb48fd20d6f84f678a52c35bec015da5ecc8520f3c28ed0edf66d970fff18d89ca47bed65574dc0bc4a1f3  nimbus_validator_client
# Linux ARM
df7ff9d8983a62809c59cb75dbdd67264dbf2bee3ad5ee3f883a64f6d9a05c5a86050074ff580b553463b82be9360dedf6306d6c0566e52ac02e723b053d64a0  nimbus_beacon_node
702556ec8cda5d3bbc31f92601880a8da52d57644cd54761601bbdc728cfc03482465aefa72c0647c3df2afdc60324fa421b203a9a63d6e23031e4cebb91ac3e  nimbus_validator_client
# Windows AMD64
c3a7566d117a05cba309b1169b4cf055756ce8729421a298ee5b1c3c5271e4b6283903582f3b571ec7d5ea146c70a408034af3e258f5348776d2b638a47a84aa  nimbus_beacon_node.exe
eb1bd230354b4d9ec7f22eee0099aae171b79fb0e59f50897d9ea5d15b69d0d375071cb3ce7163b72ef57aac034e621c13749ef333832826c5ad230e2da105fd  nimbus_validator_client.exe
# macOS AMD64
316546338caeee5f5f7e29233c37af9194760030b708c5974f052d2d4477984660a95534e2cf2d66397e22155f85b921db9ed30043864b38d26550d0919b7f5e  nimbus_beacon_node
6d270da55e91f4283095bfc1ced2f94c96efbd92da647f86f073f1e8dd1d5cea6485ea0154316e131d8c602ad4b5d112e9e691317548cd629f9dde83feb1259d  nimbus_validator_client
# macOS ARM64
940b5774cf4d72e86bc8a76ff645b43d72d08eda5a289afc3d1d9b51c11b2acf51946b22ef1f757a7ef30b49bd85a5a4e30e4a215c509c67c0201671bdab444b  nimbus_beacon_node
e640cf9f8ce61e39ff5b501ff59646966419027bac6da2078263944fa9773b3a5ccf862cf3ebeec30de2e826f90fefd9f162f4f9fd2b348cda758dce70018650  nimbus_validator_client