v23.9.0

Notes

Nimbus v23.9.0 is a low-urgency upgrade providing full support for the upcoming Holešky testnet and simplifying the required configuration for using remote signers.

We've been hard at work researching and developing a GossipSub protocol upgrade, designed to vastly improve bandwidth and latency, especially when dealing with the upcoming larger EIP-4844 blob messages. This release introduces the initial steps towards this upgrade, along with CPU optimizations and enhanced DDoS protection.

Improvements

• The GossipSub implementation of Nimbus now consumes less bandwidth and CPU cycles, while improving upon the existing DoS protections through better peer scoring:
  #5229

• The new --web3-signer-url command-line option can be used to connect Nimbus to one or more remote signers without requiring any remote keystore files to be created. The list of validators attached to each remote signer is obtained automatically through the /api/v1/eth2/publicKeys Web3Signer API endpoint:
  #5366
  #5385
  #5389

• Nimbus now supports the upcoming Holešky testnet:
  https://nimbus.guide/holesky.html
  #5337

• Faster validator registry processing reduces the time spent by Nimbus in state transitions and replays:
  #5412

Fixes

• The deposits exit command was failing due to incorrect parsing of certain fields in the response of the /eth/v1/config/spec endpoint:
  #5370
  #5371

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
af10131c8315e46bdef127e9f7263b7cef6fb2acf8445a2277c5738dc692405e66b1c5a66918ea0e396dca122f14c291388f76a62ed5e8fdd38dd8a265418a1d  nimbus_beacon_node
ce0f66b8011c48eaba1d658dba3439abb922515d651f33d5105ea71425e594ca05b0c1355aeefba63f80091628e6dfadc28494acc18f7f7819ad40416e6ded98  nimbus_validator_client
# Linux ARM64
0ffd1f026f4c48f37f46c88fd83a259a9271a630aaf782b2d429b98a1fe48e8e8b2fe03e39f2146a5d9cd641de829e468bd8d77938f8cf9f6604d537444cf199  nimbus_beacon_node
6c52f08f93b5859b6b45415dfc9c4713152134f8f2c966b9a0a3c979d8d580c23c2bf58a42363eccfb66cafc8971c62808a4394cb129761231c2c1386da0744d  nimbus_validator_client
# Linux ARM
04b6a364e235bcea357327a43f92a017295a845b34e2d3ad0f4090d151fe5b3855fdc232a421d1b42007ad4427c12cc897728ddc16668f0fc7357fdb4de9ae4c  nimbus_beacon_node
5b3fca105eb4fddbdf267b2d03d4e40537dfcd3b202ce7151ac0ea7896bb8d95258e407efc47b1b59fa0fcba7172fafa010034fdd53f39c0272ab20aca0a7da0  nimbus_validator_client
# macOS AMD64
4d83c4ed111c1d4b01bd01be300f84bc57b70b40f8ecb84d3465ffbc94b1e46bfa520b3782aca479e0ac0e726b99cfd609112132ca3da8b9ae44774188ecc16b  nimbus_beacon_node
4bcfe1e24e88e523d28447f90d97d4a33d410946fae3e5158fb58920118f176643766c3c19a32aa01e76b1ff4096cd1c5d1421f3e97ebf9130fc9681e6d38a67  nimbus_validator_client
# macOS ARM64
63c9907070424ab38658bc817646c97bad859e112b34de11feb060155e7dd8d66e6c2443a5ff975d49cc4fee741371c5eccd2b582323ec7528e05827e04f17e3  nimbus_beacon_node
9797ee153645d9a273869634476ac07c1560cd9b2cac8a3158079da1e193cb5ebb234a8c2da7118da398df257ec85bea19699af12c3d15aa0541b4e168f88ff5  nimbus_validator_client
# Windows AMD64
2495d8069bd6a1c077ae9cb51525a3d7663337b6bbe9353d31dfc862efa3337dc227494e7e3aca255e4f33739a46b4aa0e8152330bdcf2ca5e3a0589982f4971  nimbus_beacon_node.exe
dfe6b9e61bf9e599aaa01f9ff69aa8711cf01532bd04f1300a855b7a4e8abd79371b3ca9d504237a82f935ab0fe1b563bc631d706d68759769e04414f15d64e0  nimbus_validator_client.exe```

v23.8.0

Notes

Nimbus v23.8.0 is a low-urgency upgrade focusing on performance and stability improvements, aiming to address the increasing number of validators on mainnet and upcoming testnets such as Holesky.

Please note that this version enables the new attestation subnet subscription logic, proposed in the Ethereum 1.4 consensus spec. This will significantly reduce the CPU usage and the consumed network bandwidth on beacon nodes with many validators, but it will slightly increase them on nodes with a single validator. The --subscribe-all-subnets option can still be used on powerful hardware configurations to produce potentially more profitable blocks by processing all attestations directly instead of relying on aggregators.

The upgraded BLST library now identifies your CPU model and selects the most efficient instruction set at run-time which significantly speeds up docker and binary builds. We have tested this on a wide range of hardware, but should the CPU incorrectly advertise extensions it does not have, a downgrade might be necessary while we investigate.

Improvements

• Optimised algorithms and improved thread scheduling strategy allow Nimbus to process 40% more incoming attestations on typical hardware configurations:
  #5288
  #5176

• Faster state replays and lower latency Beacon API responses are now possible due to lower overhead when loading any kind of data from the Nimbus database. This was achieved through more efficient SSZ deserialization routines, the elimination of redundant CRC checks during data decompression and more precise cache invalidation:
  #5207
  #5264
  #5282

• A more optimised SSZ hash tree root implementation brings faster state replays, block processing and other performance-critical operations in Nimbus:
  status-im/nim-ssz-serialization#53
  #5292

• Nimbus now performs less memory allocations during state transitions, reducing the risk of delays induced by Nim garbage collection:
  #5235

• The BLST library has been upgraded to its latest version. Nimbus is now using a more optimal approach to aggregate signature verification:
  #5272
  #5268

• Nimbus now supports the Chiado Gnosis testnet:
  #5208

• BearSSL has been upgraded to version 0.2.1:
  #5298

Fixes

• Nimbus was not compliant with the latest Web3Signer specification when requesting block signatures:
  #5294

• The Nimbus beacon node was frequently crashing immediately after block proposal when using a validator client and an external builder:
  #5295

• The Nimbus validator client was crashing in certain situations after a request to the beacon node has timed out:
  #5297

• Nimbus was failing to load a built-in genesis state of a supported network on certain ARM CPUs:
  #5244

• When optimistically synced, Nimbus was sending unnecessary forkChoiceUpdated notifications for already finalized blocks:
  #5248

Removed functionality

• The builder API is no longer supported in network simulations and custom testnets, based on the Bellatrix specification:
  #5162
  #5203
  #5251
  #5262
  #5272

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
8a1895410ced10c0a05d1bf8d4b8fda193a397b3d0cce2dfc9c70205a60b9a9add114feac314d4e7ac6d430226c351620e685ffacb0f4aeadff9141a8504a85a  nimbus_beacon_node
61b5e8929cf12cb542126fe1f128353ae3b888669c130766a3929cdf5dd0d8bc668e3c6aa7930acfc0047a05ca0d608db04ab8e6ccf2dd1f521299f3385088a8  nimbus_validator_client
# Linux ARM64
542ceaef146c6e8aa5878dafa95230ed5c43a82b79db9b8e6eaf4abb10bbdc1c062b863d13001c3a1633f702582e7b8bd0c25d4463e8f7168efdf67b6256b3eb  nimbus_beacon_node
7a513c39f735abf349f7f55574277f6d0d8df915c1c9c0ae7df0839d224bbe783f02647bb4d590d87256dabe978cc4a090d8855dce39c98ce162f166c800446e  nimbus_validator_client
# Linux ARM
57c2479109f5702ae78b626f4331e3df49c47620c71ec6cc8bf0499fe6677bd19cc973af103025bd192b88e63396b49e4bb8f4a5186deabfddbf75723549fdd7  nimbus_beacon_node
ca6272f4e0e934a8d32f8981e3a30f12d4b8a14fa8434b1d4ae5a3d47de1dbd6943f6d06849f17767fa2d84457bf8e3b7cdbc2e85876740e576c5aec8e3efdd8  nimbus_validator_client
# Windows AMD64
d2ad068620a1e00dc2a269cfcadc6cca2930a83e3ecbd66e0afb07821dbb6cd63c93b219a2164e69ea26bae0faa25f2899abb21f504c68c50b8b6a488915b15a  nimbus_beacon_node.exe
96c9fcde57647215ab366fd8b0d68576fcdc087af703864fc0c035f0e4c9044b067660862229a7b8fcd726c1d67cd89151572814c990ac7a959de74d99110fe0  nimbus_validator_client.exe
# macOS AMD64
35be189add3b7326b26ad0ab5f8b6e46c797b18cdf62b3fac6be4005c16fd997c9618aa3d5f9e5e7a8f1988ac2fd0f829ff146456f96fe19118559762f855474  nimbus_beacon_node
49f311c058f2b80c5060261502440acd8a74484548a31859b452e3abc61137f84954e35266ed505dec99a59054d020930d0d3aaa37da71f264398107f7853b44  nimbus_validator_client
# macOS ARM64
e449ddec85170273e14ec6f18d8d3c82e56f5160d48b00815b2c209889f34f8bf63e22bd8c8bed38ab5a0867357198676f8223c7445585cb89a920d98da33677  nimbus_beacon_node
699fb534e3afeb7ea5e630d3d0879565ba256942fb1b492efbb14f240eb43ce32d3eea48b580195fdd4632f0f92c95aed3f9f595a5a394ecbe75d057c6ce20d9  nimbus_validator_client

v23.7.0

Notes

Nimbus v23.7.0 is a low-urgency upgrade, bringing advanced profit optimisation capabilities to the Nimbus validator client and addressing risk factors that can contribute to poorer validator performance.

Improvements

• The Nimbus validator client now uses a scoring algorithm capable of selecting the most optimal attestation data when working with multiple beacon nodes:
  #5101

• The Nimbus validator client now synchronizes its clock with the Nimbus beacon node in order to eliminate any risks for poor validator performance stemming from de-synchronized clocks:
  #4846

• The /eth/v1/beacon/states/{state_id}/* family of REST end-points now support queries by state root as long as the state is within the most recent 8192 slots (approximately 27 hours):
  #5155

• Improved validation of blocks during syncing allows Nimbus to optimize the initial syncing target of the execution layer node:
  #5169

• The Nimbus light client is now available a C library for easy reuse and embedding in other software (alpha release):
  #5122

Fixes

• Due to multiple reports of slow start-up times on certain hardware configurations, caused by the one-time initial pruning performed by Nimbus v23.6.0 and v23.6.1, this functionality has been temporarily disabled:
  #5191

• The block monitoring performed by the Nimbus validator client was permanently interrupted in certain situations after a timed out request to the beacon node:
  #5109

• Nimbus now uses the most up-to-date bootstrap nodes for the Gnosis chain:
  #5175

• Nimbus has addressed a minor risk for missed block proposals at epoch boundaries due to multiple compounding risk factors:
  #5195
  #5196
  #5194

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
25390784dab218dc811effa3772c8ddd6c8041b8cbee740be646a56422b19287b9c1412193c56c3b63e55e3d0f2dc923813d142d73cc16af23073e738365fed5  nimbus_beacon_node
ffb93432497da2b3b203271f47a4583beb333fb295df580788b5bcaf6944270d99d7afa7cd3a782657ec8e124f0af387a1cdc4389bdcbf9d92874dc2f2cb48d7  nimbus_validator_client
# Linux ARM64
21820baa0c00e6ef85c22c0f992ba76b4fd1490e598d7cbcc2fec6c0e535d87ccc6870bdd3266fab6ef386fdc3049a87a400f507abb282c8d2cb8f5a1e3c0415  nimbus_beacon_node
0e271c8020e8bebaf74c93daf28aa8bbd7272cfe80b7e9dc2f313350cc8040e416bc28706171bf9f5238b2f6810f62e4dc7619ee151ab18ba4529944043a731e  nimbus_validator_client
# Linux ARM
c743418170e60beb61468ff9eb1adac2db0ed7c0195c10295892d94974ef7a1fab07aed8c40ca023606997079c427e01578a2ab0c79887674ab34aa9049204ab  nimbus_beacon_node
f5a32605e079d441e5bf07f87a19ae7ad050c170190116e93555f924762f44857ff50503b19d1657f3e6da79ca21b4ac68355558b327a1dddd5ac3f707a95ab6  nimbus_validator_client
# Windows AMD64
6b813134ee23941281d605467bf8a59bc78607ca463e7f30a85daec71851b72802cdb76c953287cfaaa7948689927deeccc4fbbce8323fc84b4784cb15843b78  nimbus_beacon_node.exe
224f1e5d9ec2e3e78f1103f327d8c8fb9c25623f762542df989ccd9ecbbe73a048bbbee940419366feafe17d18b3651687a492ebc8a2f0d1f5491ff9fdfdbf63  nimbus_validator_client.exe
# macOS AMD64
270db5a0dcdcf4e9bcf821dff46f7d1c7d4e3dcb0bc2a10729c5ef6e9d98ab568bc401e4319bfd983816fb51be387c26026ae3489bbc72481270ffd3c4662b68  nimbus_beacon_node
341f1e1a2406e06aa36d0f9560f711a10ee231c8114ac39190299cadfc31ca3be55419595c0ccb38bc505c19c855c362834ad65291015d0f0c79db9fcc29a545  nimbus_validator_client
# macOS ARM64
5f99de10c73420c8cc7c341e4022b9bafe6d75f2244bd2642bb255b6e047557e76b1f30d1d37ad5e10b6e304be5e4a7ae01969b74da9bbaf55c83d33678fefbe  nimbus_beacon_node
d67de0ef59060d747f2dd48cdd6f7294e65fa3e44dd56bd6d140c318b3944576ae37f4480f1a35faada3e4a61d95f3a007bdfc57f48aa49c0ce4375f7592d243  nimbus_validator_client

v23.6.1

Notes

Nimbus v23.6.1 is a low-urgency point release significantly improving the performance of database pruning on Nimbus instances that have accumulated history prior to April 2021 (Nimbus 1.1.0). Affected users are advised to upgrade as soon as possible in order to reduce the risk of missed attestations and blocks.

Fixes

• The legacy Nimbus database is not subjected to pruning due to the high I/O cost of the operations:
  #5116

---

Nimbus v23.6.0 was 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
ae06cdcb1717d5ad5bcd9d1ee996215c8318c47af9270d0cc7783012fe4a8cce10cb1fb42c357ba5f41c543064a47923b51258111b7f3b05e5dbabe725234bf0  nimbus_beacon_node
27ca76d0349e109d401e46309d486000705a5a2a992875db69353709bd4f3cde32fd7abc702af8301998e7b30d5f38bee8fc65b830895c03de1171e8d0e0e563  nimbus_validator_client
# Linux ARM64
f1c71a3c78575f2d68e61347670abf03e99ef7e7cfc36df93a842a435a5215b93a9e154884c41b7f0f6fb677fbaaa45d54dcdceac12a413e1a19e5224060b38b  nimbus_beacon_node
77a0e6cc6d9408c560693edae0ae6ab34ee8ba0a17413e40f4877ef3503a39f10a8a428f5a982c20d1ef0f36545e5fb92da9442166bf3ab50f7a6585f397bada  nimbus_validator_client
# Linux ARM
904d0663f7a921319a91b40d1191284dde7934a689e2d6d117316fad5301d9deed019e0481e6d2b3cbe40431bf04fd5c4f17f5c11aa97f4d4564a19d95c1c6e0  nimbus_beacon_node
2e236f397d5535fdce6d7b319e7e570e2878660f9d2f9c067fe4044f6dea7050d5ebc5b07cf0469edd176bc58ec22b2c1c49f646cefb3cb8b6e6d27172963a02  nimbus_validator_client
# Windows AMD64
d77bfd279d3b46e5348d970d160d962894d349b63ed5c734e667471644ff69a8650a33b919391d5ca23739d91339032f47450c0685a570475e539aeb46b81516  nimbus_beacon_node.exe
61d10bd63a74e21511cb452a8637ee7b25ca5a6edce05ee0865daceeb86a4f0175004b641aaf3621ba4b6c2b6cbb7c27acd6b6ab48b86e24664a0fb3f8a6a832  nimbus_validator_client.exe
# macOS AMD64
fbf9c9bf9dc1df8d4133aaddc5996f4b358f586814285c2e069942dad4aec5522fbe88bc3757568fb8cc13ea862982ebd9bb55fde42be73d0da1536cbfdf4146  nimbus_beacon_node
eee44ebeb15c0082cf4f40e29c6355bb18cb9c7eebc2e90ca3c2c8801bfe106f4baec2a2f954d922bed66bae5fabe77e64b3ca4777475f19e9342c595a9c8c7e  nimbus_validator_client
# macOS ARM64
bfa9480496248069fe0473a870e99681e31d9d8efff294cc6d463ff7e19df589fb0c301075a638b0248c52e886e84313bf0c8722ed436ae582c5b860875e67a0  nimbus_beacon_node
cbaf4ae03c865fab8f60f6e12a5d080787bf6fd4c12c7150c599b3c30972f73d57f6f1c8e66e867933c6886549d85d0f0ab4e067a5be435572f83be136f972c3  nimbus_validator_client

v23.6.0

Notes

Nimbus v23.6.0 is a medium-urgency 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

v23.5.1

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

v23.5.0

Notes

Nimbus v23.5.0 is 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 attestations:

  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
c26c0990709680867b9f3dc61dbd6d2f25e11dd7f984c3e4cfe6c2244c9da5d701efb055d5bd7359773265f1d27f269d3b24db00febddace05b8bdbc9bd1b867  nimbus_beacon_node
72da4c0594a9db4ad48784e7123b038b8b6593c6b4a8e216c73beaae194acbe686288bd009769de1c753200095ccfd21dd700ad15eeaa5d6a60319301d0347ed  nimbus_validator_client
# Linux ARM64
be7836c917f81c60c4ca900f23bc7dbcd06917725f29afbbe7ad02b3586bacc618cb5a8f2b37fc570379e402483529efb4078830bf7384b705fe437ea8738f94  nimbus_beacon_node
9befc070a3a2e3d2865fd115071992ccde3e29e8653b02df0158e404a687028fd21681b3b3d124bb969e8a63f2f3006c6309d1e153c8d972eddfdd52910c158c  nimbus_validator_client
# Linux ARM
f8e20b63e268ff9368146d3af374fb20e25f2dc739e437a898e663a50f266b63e5ec3aa7b6f89b4d5a1927fe9fa8ce6cc9c11a588307bb858dfd0f1224b66cf9  nimbus_beacon_node
934030b7b673e4a51216a64b8f697079954ce736afc23b098d9939ba5e401bc4cf25452d6d9732acb89b33fa6a2e7ee90b512ab21bc8fdb8007355989a3e73a2  nimbus_validator_client
# Windows AMD64
b45870c16b1d91a6f2592a910fbb027eb256df153373e3c9f9262d399c35f20945a29ef060026ffd00822dff56429229048cba3196ff1fbb2ff37dd05375db6a  nimbus_beacon_node.exe
a2ea06f7d91a27baa91a488cf44f445e52bb2dbfc83ac84dde32b7e4d0af5f5c44fd6a276d255367079a1262c5a9e71fbbf20a1e9bda89cd3618d79ea32e889f  nimbus_validator_client.exe
# macOS AMD64
049e746d3b98c29291aaa7c8cc16e8f51b4da191f88fdd390718dfbc312cd41549cc88e740146012c58dddc4b5f8d7055b78fe5f9cb5792c8e4aecb5abf5084e  nimbus_beacon_node
fc90f4f58635975b982c8c5b8d336d1da60d0fcbc3f48ec0ffa8ff6ad0bac52a730ad320ea87310d3df5271e10ba1ffac1a60a9b061102f6b32c3428b659c78a  nimbus_validator_client
# macOS ARM64
bbfa0be53077fa1068a464be941dd59d2dce719ebfb906d30166e4a882848de376b174234340a635ab89dd1cf92fedc5a1df1d63b9a2cbdd94aad882255c7113  nimbus_beacon_node
5a2a359935052cb54b2c098774802e164286d5c4115da171498f8f2d7e98284c9180ae4774a32f4a414cc548f340bd0d6db0ea184ea20228d75632def0752ffe  nimbus_validator_client

v23.4.0

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

v23.3.2

Notes

Nimbus v23.3.2 is a low-urgency, but mandatory upgrade providing full-support for the upcoming Capella hard-fork on Mainnet. Please upgrade at your earliest convenience - before the 12th of April.

Improvements

• The deposits exit can now be executed with a path to a keystore file that was generated by deposit-staking-cli or ethdo. All users are advised to use this method for exiting, due to a known issue preventing the other formerly supported methods from working:

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

• The metrics beacon_light_client_finality_update_received, beacon_light_client_finality_update_dropped, beacon_light_client_optimistic_update_received and beacon_light_client_optimistic_update_dropped provide information regarding the observed light client gossip traffic:

  #4745

• Nimbus now recognizes the /eth/v1/validator/beacon_committee_selections and /eth/v1/validator/sync_committee_selections Beacon API end-points in accordance to the latest spec:

  #4760

Fixes

• Nimbus will no longer report warnings such as "Connection to EL node degraded" when paired with an execution node that hasn't been synced up to the deployment block of the validator deposit contract:

  #4761

• Nimbus was sporadically triggering an inappropriate assertion error under normal operating conditions:

  #4759

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
bc2ff0f8f0f40609a638f01848c213f477f3391f20a253fbbc9fc017785f3cf0b28938e7daaa7b5635f012874fd98dc6de58f691507d6a5683904111a1d0c845  nimbus_beacon_node
5f72566f8a160ded321b294b3c7b1faaff532b4c78a8ce8ceb53eee1ed404d1bc5a0581059ece2b933e5af4ceaa4210d563c4e7659e764f374ffa9b480e2fac0  nimbus_validator_client
# Linux ARM64
c4d350ed0a73b252ce5cf04ee0788b732f10c6eefb820cdd0b2d465b4a885838c7f068f67e2908cda4bcb4bc137f597bc104657c77aaa17907c847a70b45e891  nimbus_beacon_node
0b543e1aecaca037e821cc40b7cd5c3c31c9db69e2d3372196b0352930a1c4d206e338fc61304b59c00ed4487ef85fa01cdda348a3b7f446bbd8f8c17d34697c  nimbus_validator_client
# Linux ARM
abdbe3e0842efadc995bd04c9d8ec1c92813462e47c3690bdfd60fe06494a227817e182fb1391698e82939f39f5ee7723a976602a7ab101615c2307293204cf2  nimbus_beacon_node
1562df16fb7d5e9f0187690506629cad86086acc7a7e11cb5d3ba6864f483d9f6ffe0caea8f04e21799a0ad3720ab4349849ebf7087f120c70cfadde28b87d5e  nimbus_validator_client
# Windows AMD64
35a034af122f3b522ebc9c2676fc9651afe02a652b42632378e290870859da5ba3cc21ce1bf69e65f3ec19e83b03f6bbd1f72de7c3aaa67dc5ed2a2121204383  nimbus_beacon_node.exe
d4c373ea6630e3752aae5d117cff48b89f33a192fb60cb35a0ad75b8a5ab57b2dc432bc93a6097548f29d3b531290c380c864dabf609bcec11ed15295ab52cce  nimbus_validator_client.exe
# macOS ARM64
467816cefb43d5231a113deb1c675ae6381ef04423dd497e53ad88ecc267873e79b0f96a1fae6756389dc05465514d53826779f52b0f771ed931afe8335e2fb2  nimbus_beacon_node
3ef3b2b679517d28708f46d24026630d69cd3bfc55617dfa9bd10f76984e451db839b626843cda0bd22d4b8095a7396944acdc3477c4b9d3e05423f5743f7ffb  nimbus_validator_client

v23.3.1

Notes

Nimbus v23.3.1 is a medium-urgency point release addressing a number of accidental configuration handling breaking changes that were shipped in the v23.3.0 release. It also improves the stability of Nimbus when paired with a Besu execution client and improves the fault-tolerance when driving multiple execution clients.

Fixes

• Nimbus was performing eth_getLogs request with parameters that were exceeding the default --rpc-max-logs-range=1000 limit on Besu. This was a non-fatal issue that resulted in slower deposit syncing speed and the frequent warning message "Connection to EL node degraded". The limit will be increased in the next mainnet release of Besu, but Nimbus v23.3.1 honours the existing limit at the cost of a slightly slower syncing speed with all other execution clients:

  6fb48ac

• v23.3.0 did not support Engine API URLs which don't specify a protocol in the URL (e.g. http, https, ws or wss). v23.3.1 is backwards-compatible with all previous Nimbus releases:

  3a35809

• v23.3.0 produced a parsing error on TOML configuration files that specify the web3-url parameter as an array of strings. v23.3.1 is backwards-compatible with all previous Nimbus releases and introduces a new more convenient way for specifying the Engine API configuration in TOML:

  https://nimbus.guide/eth1.html#running-multiple-execution-clients
  46f4826

• v23.3.0 removed the hidden configuration option --web3-force-polling which remained in use by some users. v23.3.1 restores the option as a deprecated one. Please note that all hidden configuration options are intended for use only by the Nimbus development team for testing purposes:

  ee610cb

• The release addresses a potential crash triggered by Engine API connections experiencing frequent error responses:

  d899a6a

• The release addresses a potential issue where a single non-synced execution client may cause the Nimbus sync state to revert to synced/opt, even when all validator duties can be performed through the remaining execution clients that are still synced:

  d899a6a

---

Nimbus v23.3.0 was low-urgency upgrade bringing full support for the upcoming Capella hard-fork on the Goerli testnet. Keep an eye out for future mainnet releases!

Improvements

• You can increase the resilience of your setup and eliminate any downtime during upgrade procedures of the execution client by allowing your beacon node to manage multiple execution clients. To enable this mode, just specify multiple URLs through the --el option (alias of --web3-url) when starting your beacon node:

  ./run-mainnet-beacon-node.sh \
    --el=http://127.0.0.1:8551 \
    --el=ws://other:8551 \
    --jwt-secret=/tmp/jwtsecret

  As long as any of execution clients remains operational and fully synced, Nimbus will keep performing all validator duties. To carry out an upgrade procedure without any downtime, just restart the execution clients one by one, waiting for each instance to re-sync before moving to the next one.

  If you use this mode with different execution client implementations, Nimbus will act as an execution layer consensus violation detector, preventing the publishing of blocks that may trigger a catastrophic partitioning in the network.

  #4465
  https://nimbus.guide/eth1.html

• The metrics engine_api_responses, engine_api_request_duration_seconds and engine_api_timeouts provide statistics about latency and response status codes for all requests sent to each individual execution layer URL:

  #4465
  #4707

• Nimbus will now attempt to connect to a locally running execution client even when the options --el and --jwt-secret are not specified. This is made possible by the following proposed standard:

  ethereum/execution-apis#302

  Please note that the standard hasn't been implemented in any execution client yet.

• Nimbus now support the latest version of the Builder API, adding support for the Capella hard-fork:

  #4643

• Improved diagnostic messages and more spec-compliant behavior of the Nimbus validator client when being paired with a non-synced or optimistically synced beacon nodes:

  #4643
  #4657
  #4673

• The Sqlite3 database engine has been upgraded to version 3.40.1:

  #4649

Fixes

• The doppelganger detection now acts safer after a period of lost network connectivity

  #4616

• The doppelganger detection now acts safer in the presence of out-of-order responses from the beacon node:

  #4691

• Nimbus can now export ERA files for the Sepolia network:

  #4689

• The --history=prune mode will no longer interfere with serving light client data for the full retention period as mandated by the spec:

  #4702

• Nimbus now downloads a longer range of recent execution blocks in order to avoid potential situations where our Eth1Data votes fail to agree with the honest majority in the network:

  #4588

• Nimbus has addressed a potential interruption of deposit syncing when connected to Geth over WebSocket:

  #4708

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
ecd3fab28cba8d5646df6c03f1f2c40d53ecaf05341d2fdd9089b318d7ecedef1b8943349d44cf5a7338bc7cd37a87626dba0d15b0b799a2ff072b6e98a8b861  nimbus_beacon_node
4fbaa0ecde30ca00cb3b09391f8a3f9a8f60cef9fadccf818c454791e7d8592a537c944df0220bc4cea7874e9fd95b1ae709c00adb3b60434ae95013b5454f08  nimbus_validator_client
# Linux ARM64
ae917453bbc079835b1272603bf5967dfc5a6c327e9898c9b0d6462ee26d84e88f1feb18c03070e26a2f94f0a0e1495a21ecd139d3c90ddacae5d3750670a160  nimbus_beacon_node
527844aff387720be24c07d8201ab12a1f14b3b461e649510a2008a59b905b1f78b24ec753c88fcfd66badc0302d1171e0c3b45f78a3258d2bb28be5d52f8724  nimbus_validator_client
# Linux ARM
4b85fcf2f096a9c62f945e4aa4ff7146726928dffed905bd5a42394270775821dd58509065285606b3387748a95e9212067ecad59eb704092e2505bad9e05c90  nimbus_beacon_node
6b3b65609d0bf990ea79db9b86d824e1c8fc0824c431fb82a5262db3b557bc5f5dcf55883735152024cbb390faf8f22a9cd96f5bb149e70af245338282789ca0  nimbus_validator_client
# Windows AMD64
3f307a52989717e615398f65c92b1b100f6b5aabb6f567acd992600d1bc481d1177a5bee987e7ea47d5578392f917e2b7f27b33de8d6924ab3158be7196936b4  nimbus_beacon_node.exe
1ba7bb62874d91c55ee01e2b71dedfa2c976bf8a35aea78349e6e880ce87471204a9d0db38274b6efa332b7531b30f0ab25476ce0998bf34172e07fc12162663  nimbus_validator_client.exe
# macOS ARM64
90e61d554fb6d057ed388fd5740be8bd6067b9da158dd86c43398e887fd806a52e39f006ac40c575ceabcd5771d0bac03b9327fe072d451173ed05ee8219de36  nimbus_beacon_node
24207c2ecb851339a78cd1be7d84784bac5796a4d7f0ce42c9050ef297cd50abe5dcd76d3b135cdc89bea479ea9bf8ece2b1402a77ec240be862c26d5827f06f  nimbus_validator_client