status-im/nimbus-eth2 v22.9.1

on GitHub

Notes

Nimbus v22.9.1 is a medium-urgency upgrade addressing several frequently reported issues after the merge and bringing minor performance improvements in the post-merge world.

Breaking changes

• Nimbus no longer supports the non-standard /api/ prefix for the Beacon REST API. All users should migrate to the standardized /eth/ prefix:
  #4115

Improvements

• Implemented the /eth/v1/validator/register_validator, enabling the use of an external block builder when the Nimbus beacon node is used with a validator client:
  #4115

• The expensive TTD block detection is no longer performed when the client is launched after the merge:
  #4152
  #4129

• Peer scoring improvements will result in a more stable peer connectivity during syncing:
  #3381
  #4090

• The Nimbus peer metrics can now properly track the number of Lodestar peers:
  #4108

• Fee recipient configuration, applied through the Keymanager API remains active even after disabling the Keymanager API in a consecutive run:
  #4078

• Improved support for working with custom networks:
  #4132
  #4134

Fixes

• Using an HTTP connection to the EL client will no longer result in sporadic crashes:
  #4125

• Nimbus will no longer trigger warnings or errors regarding an invalid terminal block hash during transition configuration exchanges:
  #4126

• The initial transition configuration exchange is performed after a short delay to give more time for the EL client to initialize when all services are started at the same time:
  #4114

• The Nimbus beacon node service installed by our DEB and RPM packages will now use the correct Engine API port by default (8551 instead of 8546):
  #4099

• Nimbus has better compatibility now with various beacon API servers used for trusted node sync (such as Prysm and Alchemy):
  #4133
  #4139

• Nimbus was delivering incorrect head block details through the events API:
  #4119
  #4141

• Nimbus can now import keystores exported from ethdo or Prysm:
  #4149

Nimbus v22.9.0 was a high-urgency upgrade that fixes a critical pre-TTD block production issue affecting users that restarted their node after Bellatrix. It also improves compatibility with Besu, Prysm and slow block builders and provides a speed boost in block processing important for those running on Raspberry Pi and similar hardware.

With the merge drawing near, the focus of this release has been to include low risk changes that improve stability and compatibility - if you are unsure whether to upgrade, do reach out to us in discord to discuss your particular deployment.

A shout out to our great community for reporting and helping diagnose the issues that led up to this release - in particular Michael Sproul (Lighthouse) and Joe Clapis (Rocket Pool).

Improvements (v22.9.0)

• Allow more time for block builder to deliver block
  #4088

• Improve Bellatrix block processing performance
  #4085 and #4082

• Optimize execution layer calls when not producing blocks, improving Besu performance and compatiblity
  #4055

• Revise timing of execution layer configuration call, resolving warnings that no consensus client is present on Geth and Besu
  #4077

• Log Exchanged engine configuration when first connected to correctly configured execution engine
  #4096

• Switch to nim-websock for websocket connections, resolving delays when payloads exceed 1mb
  #4061

Fixes (v22.9.0)

• Fix pre-TTD block proposals on nodes that (re-)started after Bellatrix
  #4094

• Fix gossip message id, improving connectivity health with Prysm
  #4076

• Improve handling of blocks deemed invalid by the execution layer
  #4081

• Fix a rare crash that could happen when execution layer disconnected
  #4095

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
cbcbd231ba1887958ec04ea0e5b438a8ff0abb311b45e4110cb7262876b0f500063e79154fdeb5a975d671a053df22e70b449cced32b4634bd3f9ac9445dabeb  nimbus_beacon_node
905958c80af9af7afff3d645a18c29c2cbd31f40b5376747d1e314d340fd23f7d3ecd8178eb25127e4875fdbf21b5c54b352cdef666a368c7ef46a5b84be373d  nimbus_validator_client
# Linux ARM64
69c2315bd110cefd77f7b5e03a21a5b78ad4a0aad3e656428b8cd51acd7225fb9de2f387d609a4474659348a5a6593d3cffe07df568b8c8126596607b08c1fc0  nimbus_beacon_node
a9ae98f4be46aa58890703e8bace050a3559af0c6788084c10ef35b2e11e0c0004072dcdc5a4d8a1f93d8c756d4fbfbd0a9525d8ddbc3de87f1d8bcb90cc7a9d  nimbus_validator_client
# Linux ARM
e7ca84cdd267212d629c588391b68e1291e987d763a18aacc350eceb53e80a4939961e8fc085e6e8377d9a4a595ebab92d991e4123f52d0329a057991e3faed2  nimbus_beacon_node
5997d3ff32d3cc2fac9d820806a4a3da4b33cce98196545369dbacdbe572ce51d9f64134931adf2aa1689c11eb73fa76e0b2adb52b3461e4d97c5ef6db99b4aa  nimbus_validator_client
# Windows AMD64
ed9ad84062da39916a27cc5dbac4f2e9731c3dee8b9aee1a456b88bd3f19232819210d7d94a7e58db931ae8183b49ae873a374265034a989ed84191fc36c9448  nimbus_beacon_node.exe
4075aaa137d74bb4e9b27b27870a5857438e6c8d5e9ea870705f8df4294856bc872eeea9301911360a6e0ec63c2f93c59bc21d08bdec06cac5959dcfe2e18189  nimbus_validator_client.exe
# macOS AMD64
635f8c0612d5ec3d811bdaf20b2ce7ef6bf227e16bef7d16a5122a649188939b034dc5f66b75233423d9bde06d2b3144d7f46746a66604fb08bad7a9d8e77891  nimbus_beacon_node
cd1384f8b610f386bd0b3d477d7ce979fff089eed56115ac2296018206d58c36a673677edc8029155d7cf94f60b25a92056a0dfce68dcbaa93d79afd78cd6b45  nimbus_validator_client
# macOS ARM64
7645b00cff798abfa976b7d59ba3c3fa0ff3c9fd5a39774af4c0474400e05a72faea8546d67db71065c846183d730904f34ef9c60702206cdd168e339fbd58ba  nimbus_beacon_node
9fbc6d5ea0d293c9ad04251f6051837f9dcc778402d4260d822c1e390eaf28419648970370f41643b0666463afce370dc22e67a15152470698f9b9e7e5f2a609  nimbus_validator_client