status-im/nimbus-eth2 v23.6.0

on GitHub

Notes

Nimbus v23.6.0 is a medium-priority upgrade, further improving the efficiency and the standards-compliance of Nimbus while laying out the foundations for the upcoming Deneb hard-fork.

Improvements

• The --history:prune option is now enabled by default.

• Nimbus can now process untimely attestations without triggering expensive state replays, resulting in increased resilience:
  #4911

• The Keymanager API can now be used to perform voluntary exits:
  #5020
  https://ethereum.github.io/keymanager-APIs/?urls.primaryName=dev#/Voluntary%20Exit

• The Nimbus validator client now leverages the more efficient support for SSZ responses of the Beacon API:
  #4999

• Full support for the upcoming Shapella hard-fork on the Gnosis chain:
  #5114

Fixes

• The support for interacting with the Beacon API from CORS-enabled clients has been restored:
  #5028

• The Nimbus beacon node will no longer inappropriately report el_offline=true when fully synced:
  #4991

• The Nimbus validator client will no longer occasionally fail to perform sync committee duties in the first slot of every epoch:
  #5083
  #5084

• Nimbus will no longer refuse to import certain valid SPDIR files (slashing protection interchange format):
  #4997

• The Nimbus behavior differed in minor ways from the Ethereum's fork-choice and honest validator specifications:
  #4992
  #5002

• The Nimbus beacon node was leaking a small amount of memory during a build-up of peer-to-peer block syncing requests:
  #4697

• The Nimbus validator client is now compatible with Lighthouse beacon nodes as it no longer exceeds the maximum allowed number of validator indices per request to the /eth/v1/beacon/states/{state_id}/validators endpoint:
  #5082

  We are deeply grateful to @jshufro for contributing important fixes in two consecutive Nimbus releases!

Removed functionality

• The implementation of the phase0-specific Beacon API endpoint /eth/v1/debug/beacon/heads has been removed:
  #5058

• The Web3Signer support for performing the phase0-specific V1 block signing requests has been removed:
  #5014

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
d7625312bea1aa9788aca45b2c97a890561d6f0efaf8d8f590fe7c19413856ab74badd178065230ea00ae3225cf604595aceddc48d77cbb24c0e74518de94b8a  nimbus_beacon_node
daf17f555044f10d0aa70bcbdea87dc8e62d87b51461e967c9a9d428a4bb0e299bdb27fa5b9a1e81c836ccfb20726fdec72c29d61bb57ad3650153a8d208b77a  nimbus_validator_client
# Linux ARM64
ed88504b18fa9a7d38d7ae0d1939091a927b28cfc7969a8fc187fce5c849ffa242a9f8a6761f7082182b4beb0098dc4be5b935a1e34ad0a3890097bf56f5b6b4  nimbus_beacon_node
884a686a1821e3a9e02f819da3336416f1685565535b7c484eee55f3d06bb3b00a19dbd38d774a1dcdc004d0343f2efa0ee87bd6d83629bc6d83530c9640c8a1  nimbus_validator_client
# Windows AMD64
bf6b4e9361025f8b43ccf4bd52094c3533907118e16e5ad536e074dd429799c89e8c22096751dbcd2e84783415174b65bd6b63244ae2e455ce812befa0abc2a4  nimbus_beacon_node.exe
735d9882df42eb6973f1b93a71d72c5e7a172c592576c37db3ca182b4122c5f41ca489dd34d85e4cdf5f7bcd523007d20528073a1267ae1b77a7616162ec7009  nimbus_validator_client.exe
# macOS AMD64
fe99a1db4610542c46a7ff0143e251313b2fe5785cae6757b07ea59e2f6881b52dc6d7e1dc628efa0a1b0ec35ca2bbed04cd04f8de87f46bc531f84e81745a28  nimbus_beacon_node
6e9b99c0f6fa06cdd2455803821b53d1ac925468fd64ac599f7e5599f5ae423c25343ad26642030eea833fe5c75f67e0b5dce95aaa81918ac6535f8e0f5e4a6f  nimbus_validator_client
# macOS ARM64
bed56d5ce3029951dd1854696ae10571e159ce508acef1dfbd1c1d888484bdf152bf79c8d9779dbaf677edebf948088d4cbf97480a076ae0c2188f2c0515fa64  nimbus_beacon_node
6bd08f6cb44891fbb4ad967622227a1b32e89dd336806113abe8a48044c433536603c19d56a6cae13e761c9dafe5682412e19e8a754829b9e36df9e32e79b1c5  nimbus_validator_client