v22.10.0

Notes

Nimbus v22.10.0 is a medium-urgency release, continuing our accelerated release schedule and bringing further stability and performance improvements after the merge.

Improvements

• Faster block production, bringing practical benefits on low-powered devices such as the Raspberry Pi:
  #4184
  #4196

• The Nimbus validator client can now work with multiple beacon nodes with configurable responsibilities:
  #4113
  #4140

• The /eth/v2/validator/blocks/{slot} API now features an optional randao_reveal parameter in accordance to the latest Beacon API spec:
  ethereum/beacon-APIs#222
  #3837

• The /eth/v1/beacon/blocks API now supports SSZ-encoded payloads:
  #4154

• The new metrics beacon_block_builder_proposed, beacon_block_builder_missed_with_fallback and beacon_block_builder_missed_without_fallback can help you track the successful and failed attempts to use the configured external block builder:
  #4158

Fixes

• Rare, but critical conditions manifesting primarily in the Goerli network were leading to an unrecoverable database corruption:
  #4174
  #4192

• If the chain was re-orged while Nimbus is shut down, this created a low risk that the client may become stuck on a non-canonical block:
  #4161

• Nimbus was not serving the best possible light client updates when back-filling after a trusted node sync:
  #4195

Upcoming breaking changes

• The pre-altair REST API paths /eth2/beacon_chain/req/beacon_blocks_by_{range,root}/1/ are now deprecated and will be removed in the next Nimbus version. Since these APIs support only phase0 responses, it is unlikely that there are any remaining clients using them.

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
5b909f92255d945fb2af7ae8e81c7da5a3fd5aa58d64c68ac4cfb1a87db4a4476c890c0f5a4459c985bbef189e6b2b307cb903626db8c9347b7f707f351cbb72  nimbus_beacon_node
568b18ae48d6a2ce59377a9ec1e01af48cbf3fd14e52d42ed164761f27e441f49a33b9bef2cb8a63068ca213ef42e13a4536bb79facb43ec39b66a6947a44fe1  nimbus_validator_client
# Linux ARM64
5f4becd77f01c6b85d939008e86cb36e4bbf322db37d79f26d3ee9696fbd0aae1b15d71b0f9f046e56729cfb649b718f1fff8d40ad798fd15b60e9bada07b2a0  nimbus_beacon_node
5d7c3895f6ad9922724214490a15243d8cf35f08e70641e9ca3f6acc4d50a0e47fb6c56616f55f1930f94c3fd0e5c833eb7bbe656fc2f27847c60901aee83dab  nimbus_validator_client
# Linux ARM
2e2a555fb6ded2045714235c77e1324b218ebf208162b4006a63866819e924526ee40ab0213e0dc4f8dfbacbd68a12abadcbf3d9f4522392ca16fbc6fd4f97a8  nimbus_beacon_node
c8d391fd8dfd860b7f8f63a393592edfc0f8e48fc92c096acfd02025c130071e1841fa92e0d5e4ff1db3683c7e72b900cb7791ba48990f5f6bf38d10cb80750c  nimbus_validator_client
# Windows AMD64
f3cf63edc97018cf7dcc2a72eae79b5e8709a9a31b691cb404a8f33d671b1e835dd1bb637530ce3ade14b19a9c396a1647d8459dda8718ab107213afd89d34cc  nimbus_beacon_node.exe
a5585b1ae39249df2cacd690f7e0fb39872eb6344fbc90b23325b1a64d45ad51dc4c1e1fee6aa6f152b3df0e265ee003a03bf517cc0b7173dda8f66c5357e8d9  nimbus_validator_client.exe
# macOS AMD64
a3b46db0e4ceb0e14cbf5b957d3b01ab029669692b54bbee4ef307a75d6fc2a597968c3010b76216ebb7527ac5daa26499502c10ee4c6018b7c5a3fe43989f3f  nimbus_beacon_node
02a9cc13d93e2e88c61966d5d09e028cb334b37ac80f9080f65fd18347047f4ccb817f02a5ce479cd77b487474baa8a78b845c564ffec75494aabbbd963706c4  nimbus_validator_client
# macOS ARM64
f65cd6555cb85332e08149e8e6ef9e619144dd84e23d7a7a2cb45c4cbfcca575c2bc6421b34d044ca13914d1dfe47399f197f73c1389cf97ae4cf3a70fcbcfe9  nimbus_beacon_node
1f395812ffc0f51df6b844542f6a2fd00a789aa149b5ef999f7061e942c28acd80c832cfc0f7dfd92958d5cbf16391f44b679a685aa8e822924016802ef97402  nimbus_validator_client

v22.9.1

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

v22.9.0

Notes

Nimbus v22.9.0 is 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

• 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

• 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
d2676155cbdd15711e9e968cc4adb022c5fb1e1b5ae265e910105e8304f6b0cac29fce4f2e5a4891dd7089f4f351fb23d8e9a9617e18293e1c632abaf00f563a  nimbus_beacon_node
e7654b2f7a4ec9b3bdd94d71f9b306aca0be51edae63e752d9dde81a9b204fcf39431aa2a744cd1dd9274a49821accece4a79ed11e7f79a69c865d0cd03039f2  nimbus_validator_client
# Linux ARM64
dc2cc513181bde347dbb81e1a0a9cca0c803ebf753f9225d22e6a43bb117cd423e1732e2e97645c37ab7508ea4c6088d51ad92fc2707ea38826661aa189fc980  nimbus_beacon_node
8da341eabb702e5c27442356291a31b849eebc20aaa9fb49459a254a20b5d13939b717b05aa18c720f25e930476d2e0ddb4b118f59234332ee5e71ea25962bcb  nimbus_validator_client
# Linux ARM
2428a405bc4305c1909e9dc79665ae207bce82fa5f057817c5b7519cdc67e1f15c3000a10a4c243e148567e3513bb2eb2a09a4fd552fc73c9c97c1816ef22117  nimbus_beacon_node
cee17eb1f9825527e7029ce2074e3e878f5926b8bbecac48c37c70714d7ba20b0cc4bf0506cb038f6d43d2ef481ad4d279f587437088619eb618602c32f0f568  nimbus_validator_client
# Windows AMD64
e2174c5bbc28d1c3f772311c145a22efba1ce5332a7acc181eb7dcaede1ed881b747077be513609e8902aef0690ed0870dfcfb44646b9a8abcc2effe13f6a425  nimbus_beacon_node.exe
97f4c392df46a3e88ba49b2e12cc070baab6a735fc047c6967a9370859602a3d2155b76a2edca61cf9935a717564bee0182d127b87533d8246853d7070145b2f  nimbus_validator_client.exe
# macOS AMD64
385c35c4c13ab76bdae39821be693d98213aae07ac8ff131d7f0efdb2496c86128be77f2bbc02bf25f05fc05ffa2ca854f4796d73daad71389c93cd01e70a693  nimbus_beacon_node
79fe2280875a0cb88f0107602eb74e0dbf20341ba5eaf4704420ef1eb599b0b0bb4c3aa98c929651ec42afea9f41aeebf738ddd743c11d9291f70c52bb2e6c54  nimbus_validator_client
# macOS ARM64
7f8e9bb55afa35da6cc6b7adc057a6ad01fd3214ff75e6e2bdbe832b40b3d7cac4dcfc5c299b1b581ffbcba1612c78aa6c8a4ff63e27977eb4a2678b3ca22ddc  nimbus_beacon_node
deffe991c784073f642429ddde44da05694aa42eedb0da693cdaab5be93367380fe9b0b2002b1ee749761456c8d62017b8340a12d4919dc580b97adf299ebcdb  nimbus_validator_client

v22.8.2

Notes

Nimbus v22.8.2 is a low-urgency hotfix release, eliminating a risk for potential crash during block production that was introduced in the v22.8.1 release. You can safely skip this release if you haven't enabled DEBUG logging on your beacon node, as the risk exists only when DEBUG logging is enabled.

Improvements:

• Reduced CPU usage for validator registration when using an external builder:
  #4040

Fixes:

• A potential crash during block production when DEBUG logging is enabled:
  #4054

---

Nimbus v22.8.1 was a high-urgency upgrade, improving the stability and performance of Nimbus in post-merge networks. Upgrading is highly recommended due to improved timing of the interactions with the execution engine which may lead to higher profitability from block production, especially for users running Nethermind.

Improvements (v22.8.1)

• More timely block proposals in the presence of a non-responsive builder node:
  #4012

• More timely delivery of fork-choice update information to the execution client, enabling the production of more profitable blocks:
  #4012

• Improved SHA256 hashing performance resulting in a minor overall CPU usage reduction:
  #4017

• Reduced latency in the light client when following the head of the chain optimistically:
  #4002

• Spec-compliant delivery of the "safe block hash" property of the "fork-choice update" messages sent to the Engine API:
  #4010

• Relax overly aggressive gossip filtering conditions for incoming blocks:
  #4044

• New metrics beacon_block_production_errors andbeacon_block_payload_errors for detecting non-healthy operation of the Engine API:
  #4036

Fixes (v22.8.1)

• Sporadic loss of connectivity to the execution engine in the presence of large payloads:
  #4028

• Inappropriate loss of connectivity to honest peers in the presence of a non-responding execution client:
  #4020

• A loophole allowing the inclusion of very old and invalid slashing and exit messages within blocks:
  #4013

• Confusing error message when trusted node sync is executed with an invalid REST URL:
  #4024

---

Nimbus v22.8.0 was a medium urgency release, featuring full support for the upcoming mainnet merge! All users should upgrade at their earliest convenience, but no later than 5th of September.

Since the network will go through the Bellatrix hard-fork on Sept 6, 2022, 11:34:47am UTC, failure to upgrade in time will result in inactivity penalties.

Please note that once the network reaches the terminal total difficulty (currently estimated to happen between 13th and 15th of September), it will no longer be possible to operate a beacon node without pairing it with a single non-shared merge-ready execution client. Nimbus is fully compatible will all execution clients and the required configuration steps for all of them are the same. Please refer to our merge guide for more details:

https://nimbus.guide/merge.html

To raise awareness of the required configuration changes, once the Bellatrix fork is activated on 6th of September, Nimbus will refuse to start unless a properly configured and authenticated Engine API end-point is provided through the command-line options --web3-url and --jwt-secret. If you need more time to complete the transition, you can temporarily run the beacon node with the command-line option --require-engine-api-in-bellatrix=no, but please note that such a setup will stop working once the network TTD is reached!

We would like to say a huge THANK YOU to all of our users who provided immensely valuable feedback in the many months of hard work leading to the merge and to all the fellow research and implementation teams who made this historic release possible!

Onwards and happy merging!

Breaking changes (v22.8.0)

• Nimbus will refuse to start unless connected to a properly configured execution client in Bellatrix-enabled networks:
  #4006

• The custom error code returned by Nimbus when a validator doppelganger is detected has been changed from 1031 to 129 to improve compatibility with systemd:
  #3977

Improvements (v22.8.0)

• Support for external block builders (a.k.a. MEV):
  #3883

• Beta release for the Nimbus stand-alone light client, which can be used to drive any execution client without requiring a full-blown beacon node:
  https://nimbus.guide/light-client-data.html

• The first spec-compliant implementation of the LibP2P protocols for serving light client data:
  https://nimbus.guide/light-client-data.html

• Keystore locking prevents accidentally loading the same validator keys in multiple instances of the Nimbus beacon node and the Nimbus validator client, thus eliminating a potential slashing risk:
  #3907

• Debian and RPM packages for the Nimbus beacon node and the Nimbus validator client are now available as part of the release. In the near future, Status will also provide a package repository, offering a more convenient installation:
  #3974
  status-im/infra-nimbus#79

• Improved performance on networks with heavy forking activity through a reduction of the required state replays:
  #3990

• The Nimbus validator client now supports validator activity metrics such as beacon_attestations_sent, beacon_aggregates_sent, beacon_attestation_sent_delay, beacon_blocks_sent, beacon_blocks_sent_delay, beacon_sync_committee_messages_sent, beacon_sync_committee_message_sent_delay, beacon_sync_committee_contributions_sent:
  #3915

• The sync status displayed in the Nimbus status bar and certain log messages now describes the state of the client more accurately (optimistically synced vs fully synced):
  #3987

Fixes (v22.8.0)

• Spec violation in the expected payload of the /eth/v1/validator/prepare_beacon_proposer Beacon API end-point:
  #3938

• Invalid empty execution payloads being produced when the execution client is not responding:
  #3991

• Potentially incorrect Eth1 block votes, disagreeing with the forming majority:
  #3944

• More resilient deposit synchronization when Nimbus is paired with a highly loaded execution client:
  #3943
  #3957

• A potential delay in detecting the terminal total difficulty block:
  #3956

• Missing Gossip filtering rule for sync committee contributions resulting in unnecessary traffic:
  #3941

• Compatibility issue preventing trusted node sync from Lodestar nodes:
  #3934

• A potential crash while processing rare gossip messages such as slashings and exits:
  #3965

• Inappropriate attestations sent by the validator client when the connected beacon node is only optimistically synced:
  #3968

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
a91ad7421078305f9e8db34f22e2ec0ba3e7f8cd0fec03b1cddb8c4b18f3929990063c2a792c5e01aba186aa4edb3153269f2e828742f901ea52242a6b9e0fe2  nimbus_beacon_node
093f71628e443a671fa073fd70b1147d9e925b8f0e95b332032cd8477456fef738b73066b653776706dbe1fa2c2abef7760e7898c5cd8913bc376e3952b10ed3  nimbus_validator_client
# Linux ARM64
6e6c587a8cc60a4890e187683b61094815a8fcd66a1ab9222ff9853082f3e89f3b613b444b551bd5e16d41a05a329510d31fbc63bb78454487d624fc4fa51f3a  nimbus_beacon_node
6b77bb74d23d3fd56bfa940cb0c79febc5b3eedcb131021928bea70783a59c7ad77b3af857d4c8353bc6f93b568107804e0a20cf4e04df88c3eb856e09bbed92  nimbus_validator_client
# Linux ARM
59beb026273a310380ff385b8eea2225f8859bb42341c2fc4c78b0e9e565298e6d685e6f0edc266322aff653584dd751cb6c24fe1b960dc53a1172682510a02d  nimbus_beacon_node
12885c763c5725ca7a3f6c68cc008fdda5fa0b592a834e4b5a46b42c37cfff8198695b920c7a0575a9f18714d79c77953e326e51806eb075bb10daf069b43932  nimbus_validator_client
# Windows AMD64
0241ca349b9ea831adc408e02a5197b1f4134757700c290337b45d3a6a6ab66349e300f2ae42695bc1cc2ddc5a05ba70bf9269408536aebb48ab18a5a40f34f3  nimbus_beacon_node.exe
783803290b7fda0840d5c55ece24c7b942ffd418b15c7ad381f2a0d08083b17fbeb1224f48271dffbf0607f77ff054f1494e4f9e6e7acfff4cf937cbe20f2a55  nimbus_validator_client.exe
# macOS AMD64
5f623780625cf177019ea1bea545b2452158a8beb8a3fc12403249a451a5f89a975fc2a8a9da33eb26df6dc94ea4e9b77918d6059f51917902e62...

v22.8.1

Notes

Nimbus v22.8.1 is a high-urgency upgrade, improving the stability and performance of Nimbus in post-merge networks. Upgrading is highly recommended due to improved timing of the interactions with the execution engine which may lead to higher profitability from block production, especially for users running Nethermind.

Improvements

• More timely block proposals in the presence of a non-responsive builder node:
  #4012

• More timely delivery of fork-choice update information to the execution client, enabling the production of more profitable blocks:
  #4012

• Improved SHA256 hashing performance resulting in a minor overall CPU usage reduction:
  #4017

• Reduced latency in the light client when following the head of the chain optimistically:
  #4002

• Spec-compliant delivery of the "safe block hash" property of the "fork-choice update" messages sent to the Engine API:
  #4010

• Relax overly aggressive gossip filtering conditions for incoming blocks:
  #4044

• New metrics beacon_block_production_errors andbeacon_block_payload_errors for detecting non-healthy operation of the Engine API:
  #4036

Fixes

• Sporadic loss of connectivity to the execution engine in the presence of large payloads:
  #4028

• Inappropriate loss of connectivity to honest peers in the presence of a non-responding execution client:
  #4020

• A loophole allowing the inclusion of very old and invalid slashing and exit messages within blocks:
  #4013

• Confusing error message when trusted node sync is executed with an invalid REST URL:
  #4024

---

Nimbus v22.8.0 is a medium urgency release, featuring full support for the upcoming mainnet merge! All users should upgrade at their earliest convenience, but no later than 5th of September.

Since the network will go through the Bellatrix hard-fork on Sept 6, 2022, 11:34:47am UTC, failure to upgrade in time will result in inactivity penalties.

Please note that once the network reaches the terminal total difficulty (currently estimated to happen between 13th and 15th of September), it will no longer be possible to operate a beacon node without pairing it with a single non-shared merge-ready execution client. Nimbus is fully compatible will all execution clients and the required configuration steps for all of them are the same. Please refer to our merge guide for more details:

https://nimbus.guide/merge.html

To raise awareness of the required configuration changes, once the Bellatrix fork is activated on 6th of September, Nimbus will refuse to start unless a properly configured and authenticated Engine API end-point is provided through the command-line options --web3-url and --jwt-secret. If you need more time to complete the transition, you can temporarily run the beacon node with the command-line option --require-engine-api-in-bellatrix=no, but please note that such a setup will stop working once the network TTD is reached!

We would like to say a huge THANK YOU to all of our users who provided immensely valuable feedback in the many months of hard work leading to the merge and to all the fellow research and implementation teams who made this historic release possible!

Onwards and happy merging!

Breaking changes (v22.8.0)

• Nimbus will refuse to start unless connected to a properly configured execution client in Bellatrix-enabled networks:
  #4006

• The custom error code returned by Nimbus when a validator doppelganger is detected has been changed from 1031 to 129 to improve compatibility with systemd:
  #3977

Improvements (v22.8.0)

• Support for external block builders (a.k.a. MEV):
  #3883

• Beta release for the Nimbus stand-alone light client, which can be used to drive any execution client without requiring a full-blown beacon node:
  https://nimbus.guide/light-client-data.html

• The first spec-compliant implementation of the LibP2P protocols for serving light client data:
  https://nimbus.guide/light-client-data.html

• Keystore locking prevents accidentally loading the same validator keys in multiple instances of the Nimbus beacon node and the Nimbus validator client, thus eliminating a potential slashing risk:
  #3907

• Debian and RPM packages for the Nimbus beacon node and the Nimbus validator client are now available as part of the release. In the near future, Status will also provide a package repository, offering a more convenient installation:
  #3974
  status-im/infra-nimbus#79

• Improved performance on networks with heavy forking activity through a reduction of the required state replays:
  #3990

• The Nimbus validator client now supports validator activity metrics such as beacon_attestations_sent, beacon_aggregates_sent, beacon_attestation_sent_delay, beacon_blocks_sent, beacon_blocks_sent_delay, beacon_sync_committee_messages_sent, beacon_sync_committee_message_sent_delay, beacon_sync_committee_contributions_sent:
  #3915

• The sync status displayed in the Nimbus status bar and certain log messages now describes the state of the client more accurately (optimistically synced vs fully synced):
  #3987

Fixes (v22.8.0)

• Spec violation in the expected payload of the /eth/v1/validator/prepare_beacon_proposer Beacon API end-point:
  #3938

• Invalid empty execution payloads being produced when the execution client is not responding:
  #3991

• Potentially incorrect Eth1 block votes, disagreeing with the forming majority:
  #3944

• More resilient deposit synchronization when Nimbus is paired with a highly loaded execution client:
  #3943
  #3957

• A potential delay in detecting the terminal total difficulty block:
  #3956

• Missing Gossip filtering rule for sync committee contributions resulting in unnecessary traffic:
  #3941

• Compatibility issue preventing trusted node sync from Lodestar nodes:
  #3934

• A potential crash while processing rare gossip messages such as slashings and exits:
  #3965

• Inappropriate attestations sent by the validator client when the connected beacon node is only optimistically synced:
  #3968

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
70b794b83184deb9830bef5f418cec4553153331f9644fd634ecfe1e9898892a91bee225988372e1dbfbe99c65b4b263005585a20480a53aad72e1fb0cc28b00  nimbus_beacon_node
851ebb942f3fe69800ecbeb7b417765708cff69d8152a63486ba3adf2eaa6492ee637ff1c0db09bd690ed2433d35da8d6fe9135dfea7a49c1e750fd956c67aa1  nimbus_validator_client
# Linux ARM64
64c2f34e4ae1a2cb7a974f389f31ca7ad3cb5c9df8c9a2d8a76d651f94c8beb37bc41b68e66a2b59abcf8dfba4e2b9b37efe14212e5f08d1e9de02ec2c34d8d6  nimbus_beacon_node
6942e0f74361a5051f19beedae93e65e805841c87a93b2c62393c76e9794263253d21896f9e1c0a56a65ef148063112085234a66a6de7dd613af740c49f9f4bb  nimbus_validator_client
# Linux ARM
f7f902adc1f3cbcbeba79dc74fa5ff98d295c4cc727721143ae4e7a6eff3823faa7481646ccb1d3f1fd15b0a07dd073a1c5acada8f34c7a63152a9ed31135fcc  nimbus_beacon_node
ffea8b15da5ab6ab8e7d50ca65fdf20e6bf566d0592c411f3843998ba44a9227e5b81a676ffcf9909395b0f52a38c2ff939de9470673544fe9187da33e61c064  nimbus_validator_client
# Windows AMD64
3015038e7a76dd9db4b38ca4ab07014921d97c6a7a23361ace1a9a6ed8ff36a6693c17ead1db921660f4d6cddec2d117272b8734aed9517d7c8affd21669f289  nimbus_beacon_node.exe
624701ba5d4fcb6b65e71b981cc2eb3c9d4dc492c93c4c64079b48aa431f40e064341fdd512f5a9d20ba6ca59ec1e2a9cd706dba927a49361dee6cb686e16f01  nimbus_validator_client.exe
# macOS AMD64
810c850c3639db51547a2886c094c9399a4317f7f9c2e7453130371125188a1a6f2a7cbf5c912400eca0868ddb0394d7b9a4c404536042cf7be9572eb0a23c23  nimbus_beacon_node
920467ee9ce77e9746126118e8717cf13230c6b76fbffbc597aa87494a2e662efab9444f879c088f1fddede5b97dd73515edc060ba68df72579f8f5bde3154b1  nimbus_validator_client
# macOS ARM64
dcb111d93f0f06769aa6e6d9ee8b589a10267ad328dfddaed0fb95e849c1309c787fd6b217d2c6fac63f34a366ba1ffece7558f1d46254ee09d379be4be3cbd6  nimbus_beacon_node
276c71d160011c0a748cba878804bfcd57f27039b88755d209073d0a3cd7d05743bca2fcf7b6f3909cdcdab5b5f14ac759f0a6f3dbf9e2518b4dba435af530b6  nimbus_validator_client

v22.8.0

Notes

Nimbus v22.8.0 is a medium urgency release, featuring full support for the upcoming mainnet merge! All users should upgrade at their earliest convenience, but no later than 5th of September.

Since the network will go through the Bellatrix hard-fork on Sept 6, 2022, 11:34:47am UTC, failure to upgrade in time will result in inactivity penalties.

Please note that once the network reaches the terminal total difficulty (currently estimated to happen between 13th and 15th of September), it will no longer be possible to operate a beacon node without pairing it with a single non-shared merge-ready execution client. Nimbus is fully compatible will all execution clients and the required configuration steps for all of them are the same. Please refer to our merge guide for more details:

https://nimbus.guide/merge.html

To raise awareness of the required configuration changes, once the Bellatrix fork is activated on 6th of September, Nimbus will refuse to start unless a properly configured and authenticated Engine API end-point is provided through the command-line options --web3-url and --jwt-secret. If you need more time to complete the transition, you can temporarily run the beacon node with the command-line option --require-engine-api-in-bellatrix=no, but please note that such a setup will stop working once the network TTD is reached!

We would like to say a huge THANK YOU to all of our users who provided immensely valuable feedback in the many months of hard work leading to the merge and to all the fellow research and implementation teams who made this historic release possible!

Onwards and happy merging!

Breaking changes

• Nimbus will refuse to start unless connected to a properly configured execution client in Bellatrix-enabled networks:
  #4006

• The custom error code returned by Nimbus when a validator doppelganger is detected has been changed from 1031 to 129 to improve compatibility with systemd:
  #3977

Improvements

• Support for external block builders (a.k.a. MEV):
  #3883

• Beta release for the Nimbus stand-alone light client, which can be used to drive any execution client without requiring a full-blown beacon node:
  https://nimbus.guide/light-client-data.html

• The first spec-compliant implementation of the LibP2P protocols for serving light client data:
  https://nimbus.guide/light-client-data.html

• Keystore locking prevents accidentally loading the same validator keys in multiple instances of the Nimbus beacon node and the Nimbus validator client, thus eliminating a potential slashing risk:
  #3907

• Debian and RPM packages for the Nimbus beacon node and the Nimbus validator client are now available as part of the release. In the near future, Status will also provide a package repository, offering a more convenient installation:
  #3974
  status-im/infra-nimbus#79

• Improved performance on networks with heavy forking activity through a reduction of the required state replays:
  #3990

• The Nimbus validator client now supports validator activity metrics such as beacon_attestations_sent, beacon_aggregates_sent, beacon_attestation_sent_delay, beacon_blocks_sent, beacon_blocks_sent_delay, beacon_sync_committee_messages_sent, beacon_sync_committee_message_sent_delay, beacon_sync_committee_contributions_sent:
  #3915

• The sync status displayed in the Nimbus status bar and certain log messages now describes the state of the client more accurately (optimistically synced vs fully synced):
  #3987

Fixes

• Spec violation in the expected payload of the /eth/v1/validator/prepare_beacon_proposer Beacon API end-point:
  #3938

• Invalid empty execution payloads being produced when the execution client is not responding:
  #3991

• Potentially incorrect Eth1 block votes, disagreeing with the forming majority:
  #3944

• More resilient deposit synchronization when Nimbus is paired with a highly loaded execution client:
  #3943
  #3957

• A potential delay in detecting the terminal total difficulty block:
  #3956

• Missing Gossip filtering rule for sync committee contributions resulting in unnecessary traffic:
  #3941

• Compatibility issue preventing trusted node sync from Lodestar nodes:
  #3934

• A potential crash while processing rare gossip messages such as slashings and exits:
  #3965

• Inappropriate attestations sent by the validator client when the connected beacon node is only optimistically synced:
  #3968

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
18f37b94347e67abfc0bcebb25ccc806ae0d6b0fd22185a27ae5ac3415a30791d003235c77e5873c88c7f79681c74d83bc8873a4f367896f3e303b42164a5954  nimbus_beacon_node
bb6f75cc591b18b6cee9740cbde45b5440c7ab495e1bfbfca69c1c4ab9ea83cd59a12a504436cce382be40c3f1a455391a8b7deb7f9872befdb754c4cf680895  nimbus_validator_client
# Linux ARM64
a35f86847b9b0c6560a76865f777d5e746b13ed0a55b0607d6a4368849259df28c55ab092c513a62c437c63d9d417adaa22ae008995e4dcb0a5922ce13af4743  nimbus_beacon_node
36c7c1f486edbf886dade44f0a09c2e08815acf9ae47adb6797299e2d9dab8c780be85a87dae35732aecc46ef6d98f93ce2c4f3619efcc68856efac20b7ae035  nimbus_validator_client
# Linux ARM
bf8f2ddef1faa466ddb30533ba575a13d2b9f25b0f644f4d1f90a068d9386e5e02ec9c23b38a1230ce263d27581625cc6a2742f922bcdc21bc7ff173fbb7ba12  nimbus_beacon_node
391155ee4dc54f2bec084a4e304f4938695dbe2d5af3a15f67d7f7449a228958ababfc857a84765fa680f6b25f5da3b2ff743784b50a9f6301dc85e97f0cf015  nimbus_validator_client
# Windows AMD64
fa8a416c8cafa490db54f05068db92d68607012da0628b261c48ceaa52229fc7b5c987279fe3dd6098c5a6a245c18d443426f701f8bc6a9da36aea28e64e6911  nimbus_beacon_node.exe
a620f9d0077abd354198f03d5b7a0f5f356ea8fe428f60db352f86f5b422e945ab5cc6d15f42ae203ae6aec1047a08797e45639fdd3d64cc1daa6deddff04b71  nimbus_validator_client.exe
# macOS AMD64
f1e5365e225cf3c8c8d4d26359ba96c3dc2156bae5884410886de40e44f5d9e095fe89cb2746165958fb4817c770772cfc63edf88587cd27038acd3009bf5281  nimbus_beacon_node
5336c374ef9213a77abe5bc9a65e160444ee345a9a81bbed05d74d7f26ed15c51ef9f43a66345ae501780da5587171c9200a6bd721ef0e62f293a83e9464ba89  nimbus_validator_client
# macOS ARM64
1671a124406b9c4a30845d9a343cb8687cb6305aa5b0702733fb0842eb3abe65b64cca35cae6cdd1536369088ae0d4d697a5998b327d999cb53c6ae630ae4ff4  nimbus_beacon_node
041b15cb4193b5c89a4506963964a7fa65b18400b2a0a727b68651d57b172a42bd1ebe38a74ad921cd00ed14eddd77b21317d905e46f7d4c7962ca9645976c95  nimbus_validator_client

v22.7.0

Notes

Nimbus v22.7.0 is a low urgency release packing everything necessary for the upcoming Prater/Goerli merge and introducing the Nimbus validator client (currently in BETA).

Other Improvements

• Support for fee recipient management through the Keymanager API and
  through the /eth/v1/validator/prepare_beacon_proposer Beacon API end-point:
  #3864
  #3901

• Support for the post-merge optimistic sync specification:
  #3793

• More comprehensive spec-compliance in our fork-choice implementation:
  #3849

• More spec-compliant handling of QUANTITY values within the Engine API responses:
  status-im/nim-web3#55
  #3844

• The Slot end log message now includes information regarding current and
  upcoming sync committee duties to help you identify the most appropriate
  time to restart the client during an upgrade:
  #3854

• Specifying a WEB3_URL environment variable is no longer mandatory
  when launching beacon nodes with the run-*-beacon-node.sh scripts:
  #3810

• The --finalized-checkpoint-state and the --finalized-checkpoint-block
  command-line parameters can no longer be used with certain invalid inputs:
  #3858

• Specifying --network=goerli is now equivalent to specifying --network=prater:
  #3874

Fixes

• A risk for invalid block proposals during high forking activity in the
  network due to inappropriate inclusion of attestations from other forks:
  #3893

• Interrupted tracking of deposits, triggered by a non-responsive web3 end-point:
  #3905

• Inappropriate error returned by the REST API when broadcasting of Gossip
  messages is not immediately possible:
  #3843

• Rare conditions under which P2P connections were closed inappropriately:
  #3795

• Potential inaccuracies in the next_action_wait metric:
  #3862

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
9d9298d07324fdbaa41ee16831ce6c8d2e89ede794b9790ac6932e1f6df6259d006d804e5b535f0704aa677e5d2daf6109305203ca73f5bab2728a0df35700a0  nimbus_beacon_node
7d5b3a9841a69a6de51e0e4b98beff95f4e68bd17636fc40a759829b0c48d3ffad1d103f5c0331ffc4025d3e8263850a8ef1577c2c4f5bc8f5918de1dbc58f3c  nimbus_validator_client
# Linux ARM64
173cc0fe2fc57851af619b2a6a377401cdcc9e7e7aa767676020158eab51a6481124ce1824ceb5b78283c678269fc4290752286c0dc61dd7a76dda6b88c98617  nimbus_beacon_node
3f63dc044788f4fc87188e6a99c7959f782bcf709d48c8f6a71e5b3c2847a8c0b22698d05736b57572f480cbacbf5405b164237a9b2e8ba84a4e0d2ad31afd42  nimbus_validator_client
# Linux ARM
b8ae04f042b0f375ac5ca2275387f48b9aa0fd7c68aefd1643cc3a0b2bdda298fb96bdd679e98e44735c4b98699ef381242dad799b161a564337e26be70d4fc9  nimbus_beacon_node
31da748a1370e2a3567c23e67993608899b6e9a9aace2c9ea9b456eb833a694ff3b0fda0ddc70e9bf347e499fdfa55b17b0a961bafa478d558975a638c699cf5  nimbus_validator_client
# Windows AMD64
5225c011f016f901da12c35066be22e7d5aabe7a111a3d30d64c7d22a715f7174460302a5f2367cf632384df7be8a9a4665cfd95ba485f22562e28598332ac6d  nimbus_beacon_node.exe
c7f143c61693b04d9fefb37bbcec0a96089b0afef4ddab036b7c29cebc5dad74a9d4d136632cc15f75e04eff96ab054721f06b14fc4e2ac03059bd4629380a82  nimbus_validator_client.exe
# macOS AMD64
371654cc4a78b877e33bb3e1b19fc7e5e2ddd68b40dc5df72de0e75ef9459fb5572e1a25ae7cfcf4a9dbb8abc461fd948b154dfeb0fb5b1d8198debc448e0b28  nimbus_beacon_node
e180c728f6e98d8a4b65b2ddad39d1e47fe1e6182a889f9f3b3dad3e3ce450c6766ae4bb62c7d359a168f989a6cd9ca3921a6244742e37ceb64f07f512411eea  nimbus_validator_client
# macOS ARM64
5cd0c88999ad818b52dc5e7092000dbf498bffaa23591d085d6a398d6b26c6d428da6410ebb4a8090e58ef2b41a82e883ba3ad8987613454aa2060a2a41c752e  nimbus_beacon_node
847edba8ada0022c79d8e52d358f5b1024191fbcb60af9baf1c0b4a348f7ef86c605434a0d3600fad9f59a8fdf2ececeb0e732b4c6699cb089ea2f0d1f5c1b3a  nimbus_validator_client

v22.6.1

Notes

Nimbus v22.6.1 is a low-urgency release which comes pre-configured with the correct TTD value for the Sepolia network and improves the behavior of Nimbus in merge testnets.

Improvement

• Allow testing the Engine API JWT credentials even before the merge.
  #3786

Fixes

• Lack of detection of the connected execution client's network when attached to the Engine API port.
  #3804

• Logic error leading to a premature start of the exchange transition configuration Engine API requests.
  #3809

• Inappropriate inclusion of the execution_optimistic field in REST responses before the merge.
  #3807

---

Nimbus v22.6.0 (low-urgency) brings support for the merge testnets Ropsten and Sepolia (please stay tuned for TTD announcements for the latter) and a lot of polish where we've taken the time to address a long list of UX improvements and bug fixes suggested or reported by our users. We are deeply grateful to everybody who contributed valuable feedback for this release.

Improvements (v22.6.0)

• TTD detection and Panda art for the merge!
  #3670
  #3745

• The execution layer priority fees recipient address can be configured individually for each validator.
  #3652

• Through better defaults, the parameters --rest-url, --trusted-node-url can be omitted if the targeted node is running on the same machine.
  #3689

• Improved spec-compliance with the Beacon API and the Engine API as defined after the merge.
  #3679
  #3780

• The custom error code 1031 will signal a detected doppelganger on the network. This can be handled in the Nimbus's service supervisor to prevent an automatic restart.
  #3728

• The Nimbus status bar can be configured to display the current version number.
  #3747

• Specifying the --terminal-total-difficulty-override parameter is no longer necessary for the Ropsten network.
  #3754

• Built-in support for the Sepolia network which will launch on June 20th and reach TTD shortly after.
  #3762

• More robust syncing with the connected execution layer node in Bellatrix-enabled networks.
  #3759

• The web3 test command is now compatible with nodes that have been configured to serve only the Engine API.
  #3761

Fixes (v22.6.0)

• A rare crash triggered when using a HTTP web3 URL.
  #3669

• ERA checkpoint sync failing with "Backfill block must have a summary".
  #3675

• Incorrect sync progress indicator shortly after a trusted node sync
  #3736

• Incorrect values returned by the /eth/v1/node/syncing API under rare circumstances.
  #3720

• Misleading log message when an attestation was not delivered to any peer.
  #3737

• Incorrect handling of case-sensitive web3 URLs.
  #3757

• Incorrect encoding of the current_epoch_participation and previous_epoch_participation fields in the REST requests returning BeaconState results.
  #3776

• Incorrect URL for the Keymanager delete keystores request.
  #3727

• Non-standard encoding required by the Keymanager API for the import keystores request.
  #3768

• A significant source of omitted events in the REST events API.
  #3664

• Incorrect parsing of the weak-subjectivity-checkpoint parameter.
  #3765

• Lack of support for trailing commas in lists and inline tables in the TOML config files.
  status-im/nim-toml-serialization#47

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
39429e5c9ed0e09211ed6b41dec2b35b2e13a02eb5869f845b38c5acbe28d7144446e6d836a01ad468589e8cc32b6024d05cbe4cb4c71db7b72def71037bd687  nimbus_beacon_node
# Linux ARM64
34e8789b26837b262a7b0d045013440c2b1f56202d25c2d20d29eea64566c9da5824f963e1d5a18ee35a769f3878b2106d1ac727ab2b6f4269bc9e84ca552559  nimbus_beacon_node
# Linux ARM
12ee6d8d70318766d9e18a7c8f040b5e69deb11347f15f1d5466dd8c5ecb078c827de3dd43e0557cdd30524405abfdde33dbbcdcfe9585321cee982a9cfb29e1  nimbus_beacon_node
# Windows AMD64
b90e89069cf6e84d0d202730dc54b13ee9e4193f5c335feb9350144dc9d1faff87653a2b01ff2135597d2ca40cad3821bfcf489a9d016db300341506478a55fa  nimbus_beacon_node.exe
# macOS AMD64
443070f8d5587eb3db77cf095563feb4a1b242bd2838d8a7eb2ad5ae0e8efe5d6651356d7acc0333c99a73fee7be73d39206966c3717497785b7d5bd9c076bb0  nimbus_beacon_node
# macOS ARM64
10017c6f47e233c34b49f6b12bc53f92daab3311fb2e310a9bca3197a6b9c94b5f42a415dee6a342694277edcc6dc77eb77cb39cde974bc5b7734f98d5b830a2  nimbus_beacon_node

v22.6.0

Notes

Nimbus v22.6.0 (low-urgency) brings support for the merge testnets Ropsten and Sepolia (please stay tuned for TTD announcements for the latter) and a lot of polish where we've taken the time to address a long list of UX improvements and bug fixes suggested or reported by our users. We are deeply grateful to everybody who contributed valuable feedback for this release.

Improvements

• TTD detection and Panda art for the merge!
  #3670
  #3745

• The execution layer priority fees recipient address can be configured individually for each validator.
  #3652

• Through better defaults, the parameters --rest-url, --trusted-node-url can be omitted if the targeted node is running on the same machine.
  #3689

• Improved spec-compliance with the Beacon API and the Engine API as defined after the merge.
  #3679
  #3780

• The custom error code 1031 will signal a detected doppelganger on the network. This can be handled in the Nimbus's service supervisor to prevent an automatic restart.
  #3728

• The Nimbus status bar can be configured to display the current version number.
  #3747

• Specifying the --terminal-total-difficulty-override parameter is no longer necessary for the Ropsten network.
  #3754

• Built-in support for the Sepolia network which will launch on June 20th and reach TTD shortly after.
  #3762

• More robust syncing with the connected execution layer node in Bellatrix-enabled networks.
  #3759

• The web3 test command is now compatible with nodes that have been configured to serve only the Engine API.
  #3761

Fixes

• A rare crash triggered when using a HTTP web3 URL.
  #3669

• ERA checkpoint sync failing with "Backfill block must have a summary".
  #3675

• Incorrect sync progress indicator shortly after a trusted node sync
  #3736

• Incorrect values returned by the /eth/v1/node/syncing API under rare circumstances.
  #3720

• Misleading log message when an attestation was not delivered to any peer.
  #3737

• Incorrect handling of case-sensitive web3 URLs.
  #3757

• Incorrect encoding of the current_epoch_participation and previous_epoch_participation fields in the REST requests returning BeaconState results.
  #3776

• Incorrect URL for the Keymanager delete keystores request.
  #3727

• Non-standard encoding required by the Keymanager API for the import keystores request.
  #3768

• A significant source of omitted events in the REST events API.
  #3664

• Incorrect parsing of the weak-subjectivity-checkpoint parameter.
  #3765

• Lack of support for trailing commas in lists and inline tables in the TOML config files.
  status-im/nim-toml-serialization#47

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
40b5954163ef1f028063b76bc1e7e1caf4ee80edab3e16078742a6bb9eb8dd28c06223211faac2c641b64e72ca524ecb4d5809038d350e42cb3151ea6f39244e  nimbus_beacon_node
# Linux ARM64
fa280275911a64d0504c91c519ec11414387a1d3c7b2dfe4edd1d4e22ea80afc440448f0c8dd25f243087e9c40b862563dcc61c820883a86af0db45b12936b27  nimbus_beacon_node
# Linux ARM
4cc71e010387fc260de9639de97c4bb17d037cb1ff23eef6d1fe0fabdda87f268d389b5c838f6add57915633a577465ebec665bb673b266e742bd14bd2622ec4  nimbus_beacon_node
# Windows AMD64
b30250e1a338042a7aa813c49e9bde6e06efdea57dbb23cfdd4262b07328fef31e2d5ca705f12e13f7a113906ebff673275fa508bc1e2812a4adaa6c47899859  nimbus_beacon_node.exe
# macOS AMD64
e2116916655f81870546aaadef5210836ede6a60ec8413b31c31b778f2524cc7ace27e5e7c049e9a7334eef3ceb51b6336c9602db3de5b6ce803f5ac58be405f  nimbus_beacon_node
# macOS ARM64
dc824c4372ee2d7e2743f74463418e45c27d2251f4a63a7c65a980b9a76c4f742f1c90fae285aa083b6ab3bf35b4c3f9023183fcb781883b15a27244eea7ed10  nimbus_beacon_node

v22.5.2

Notes

Nimbus v22.5.2 is a medium-urgency maintenance release updating Ropsten testnet support as well as updating the fork choice rule to use the latest proposer boost score.

If you are running validators, this upgrade will prevent you from voting for blocks that later get orphaned -- as happened with the deep reorg.

Fixes:

• Modify proposer boost from 70% to 40% to improve network consensus
  14dc385

• Increase Ropsten TTD to prevent it from being readily triggered by mining
  #3668

Improvements (v22.5.1):

• More spec-compliant handling of JSON fields in REST (for better compatibility with added and optional fields)
  #3647

• Support for the Ropsten testnet (intended for merge testing)
  #3648

Nimbus v22.5.2 builds on Nimbus v22.5.0 and v22.5.1 -- low-urgency maintenance releases implementing the proposer boosting fork-choice policy and compliant with the latest Bellatrix specifications. v22.5.2 also provides an early preview of our built-in support for BLS threshold signatures (via regular Web3Signer instances): this marks the first step of our long-term secret-shared validators roadmap which enables node operators and staking pools to deploy Nimbus in secure high availability setups.

Fixes (v22.5.1):

• Restore compatibility with certain Web3 endpoints
  #3645

Fixes (v22.5.0):

• The potential for missed block proposals in the case where an invalid deposit is submitted to the deposit contract
  #3607
  #3639

• A crash triggered by the use of Web3Signer remote keystores
  #3616

• A rare crash triggered when Nimbus is performing a large number of concurrent HTTP requests
  status-im/nim-chronos#272
  status-im/nim-chronos#273

Improvements (v22.5.0):

• A safer fork-choice algorithm which implements the proposer boosting policy
  ethereum/consensus-specs#2353
  #3565

• A completely revamped snappy implementation which brings significant speed-ups
  #3564

• Support for the latest Bellatrix specifications (a.k.a. The Merge) + all Kiln testnets
  #3590

• An initial release fеaturing a preview of built-in support for distributed keystores, (part of our secret-shared validators roadmap)
  #3616

• Reduced CPU usage when serving blocks to other syncing clients
  #3598

• A more spec-compliant implementation of the /eth/v1/config/spec REST end-point (implementing the v1.1.10 version of the spec)
  #3614

• Improved compatibility with all versions of Web3Signer
  #3640

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
32229f537af416abd4c7ad9afa78029a587028155751d889bfed8323948f16b1c90d358087d977decd0fad719a7e1bf69377ae7c7521b1ea00d7ba78a4aef80a  nimbus_beacon_node
# Linux ARM64
d61f657551d5f91d06633f22fa65594ed0c4b78322e8b9abd118a5fca0730ffffdd6c5c25fc56556a703d2950e945cf0748dc8d411add23ab3f08c6deaaba42f  nimbus_beacon_node
# Linux ARM
1bc074644fb4cc0aa4b41eaf10c11d4a5a8fd8976b20fa05b2d1632715573f8407c6fe35a08ac4c891ea8c69568da9b6669054d3379d4e7955e7a0911dae1db3  nimbus_beacon_node
# Windows AMD64
64f4a4bbe7d6de00af58dec6c9d2abef25a6e7ff2acf698939ea3e034d404dc2e562e4910aef7d4eb64aecf546cf3b7f2d851a0c310d8a52b68da4c639c1ebe7  nimbus_beacon_node.exe
# macOS AMD64
8dbf0c1904a4ac1790dbf4a638d2d1d7bb19e637801b3c56955d03b51ff11ba35748f6209eb3873920f0db497a76841c1cb27b2e8d6de44a9d0e2c826af92de8  nimbus_beacon_node
# macOS ARM64
45191d3f6709c3f4ec03cf9b3dd6e2a7a5b0d2ed24477a14a6a93bc6acba357dbc26b3d041e54e2907663a023ff6eceb66286894b492ce226fd99a1d47993d7e  nimbus_beacon_node