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

v23.3.0

Notes

Nimbus v23.3.0 is 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
70b56b802e57be9b0aa4e576ad9055775f95adc15c2cc23376cc3f97684bf52b8c84fa31194ba0c3f6bb5fdb8872d8edf446e6925959f11e6db5e9648e5210fe  nimbus_beacon_node
8718aa14417008a122fc67269e0a0dbef606aedec3fdf1bc2b7bd89935bd785d5d09d0eacd148169e3920b948456fad3a0077bf96819820af2d0cb5026631dd0  nimbus_validator_client
# Linux ARM64
1f4f9371610c8e3c7fdcae509a7d1b0f2169221c796a528bf15452dcb5b0ba0784feb1bcdfebf26674d6e89cef04519f0f3cd089f5a486eac68a409317fa7ef4  nimbus_beacon_node
670baab845834962f90ba515d75e8353e16a1937403fdb886bccf41caa6deb0b62186c32862faa474235f975db3197c1fe8319d61f45d17bbae60e5edbbe9322  nimbus_validator_client
# Linux ARM
0fbf0925c4d12d3c97accfcab87d5a18b9d6846a032be2bcb3d3c8fa9c43b5d46f6cbd9cbc2ba200b8dff113e7b120cb1aad87c05ffa9b12694d3d4625e3bbfa  nimbus_beacon_node
25b0279c3d83042c9ad7fa1df5c3d26d145167fc51f63c5a37524599c8527f51a22c482b65b0786f7d50d66fd06a287f402667c69aa025776119f728dc1d6b96  nimbus_validator_client
# Windows AMD64
294aa8b58c45b80b26686909bdc8f4ce3b3ba1511209a6383dd73b600b1a32675c4de1981028d5f1cf9575a59ef28abac39c73f455357df06a0ca20a73c00e48  nimbus_beacon_node.exe
a8c0093f9cbf02e4e7019ab388bb19c8133c5e10240f0a968a2850aec9fb96e11f69ac8909f6ab9f855a8755934888165484d43ca2f35047af8c7c45ca148466  nimbus_validator_client.exe
# macOS ARM64
af59df6a78cb971863e6efb81d363a96d2935d0bd1fed530d53d06b39b8963e1da01191b350bbdabcf112c4a1ce36c0946f9db3995bfbf36f99d23d726dbb322  nimbus_beacon_node
b2856143952a08f3308ad41b3374f6e350a79381dc44c7fbeb8c49c9873398bcda1bca61ca80713781758e7ed90f095e70f7c4d6cea1fee899756e4e1b91f1cc  nimbus_validator_client

v23.2.0

Notes

Nimbus v23.2.0 is a low-urgency upgrade providing full support for the upcoming
Capella hard-fork on the Sepolia testnet. Keep an eye out for future mainnet releases!

Improvements

• Status now provides an APT repository that will host the latest version of the
  Nimbus beacon node and validator client software:
  https://apt.status.im/

• The deposits import command now provides the option --method=single-salt which
  will significantly improve the keystore loading speed on start-up on beacon nodes
  and validator clients running with a very large number of validators. Please see
  the documentation provided in the Nimbus guide in order to understand the security
  implications of using the option:
  https://nimbus.guide/keys.html#optimised-import-for-a-large-number-of-validators
  #4372

• More efficient sync committee caching strategies bring 20-30% of syncing
  speed improvement post Altair:
  #4592

• Nimbus performs fewer interactions with the EL node during optimistic syncing
  which further improves the syncing speed:
  #4591

• The Keymanager API now supports all gas_limit end-points:
  https://ethereum.github.io/keymanager-APIs/#/Gas%20Limit
  #4612

• Nimbus serves light client updates up to the retention period mandated by
  the spec even when pruning is enabled:
  #4499

• The Linux packages of Nimbus no longer depend on lsb-release:
  #4597

• The list of bootstrap nodes for the Gnosis network has been expanded:
  #4603

• Nimbus now performs fewer forkchoiceUpdated Engine API calls with lower risk
  of reporting conflicting data to the EL node:
  #4609
  #4614
  #4623

Fixes

• Nimbus will no longer suffer from performance issues when a large number of
  non-active validators are imported in the beacon node or the validator client:
  #4590

• Nimbus will no longer crash when it fails to resolve the hostname of a remote
  validator imported through the Keymanager API:
  #4590

• The Nimbus validator client won't attempt to perform sync committee duties when
  the attached beacon node is only optimistically synced:
  #4622

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
f9a694ed11ef47612c56db5e7c7738956b85619cfd5df57d81b442d224d582ee1ad35d2caefc36da158cdf8ea474e50d244db61b3ebcd29233b6bfd5aacfae72  nimbus_beacon_node
84cec09bed52e347ea4c793fdac54e1c63af6803f1a47ec066ecf175e09a2ead707ea8f807a749d850f4a86e9e4136bf6335aa8fb58000846160a05957959ffb  nimbus_validator_client
# Linux ARM64
42a4dc5043fd11612ebb1cb0e7b075a16f7b6ca875b6c2dfdd5135eb30a7f79e4c8767659dc027a70ea439bbc8d8b6e69c9d672e4ba4de62e59d56710b539f69  nimbus_beacon_node
4597fb3b5386218b7d27e70647127c2ddcc861c4044425555b11cdc64879dc2d6887dcc8a5d97354ff5d8157e8f5fc240a1658be7c19e67b3484b05be085d6dd  nimbus_validator_client
# Linux ARM
a259637b31695d33e4da57e010b9c57652918a26d8ea57dd8f54966dd93018c8cc0b4cef6b9e28f3df5c8e4543892a6c8435fc8c52767da9c46a6f1a4fadaa58  nimbus_beacon_node
6a214cc3a2ca1166c142f71b6d2fc363a93dc99ccc04e89417f7f2ef5cc0fb277e727118fd8a5c5e7c8a9587adaa88a139c34d79bee79ea4530902f730f91a0e  nimbus_validator_client
# Windows AMD64
2b37b70739f19e7ff19b799a0bd85bbb52bf91994f0cf6357f6e1e2df47c489dd6667cfdbf3fb8406dad59af7e263f251828c04c64dc0dd8a218814cb12e0411  nimbus_beacon_node.exe
6a7deced63cfb7f09e5bc99bdfe9182cd299e94cb74980c5a914710bd9829067e235ea4e28ec071fdf7ee95b9e20209313f5f7b70518fe9d0da1e466881a5120  nimbus_validator_client.exe
# macOS ARM64
7db94cc35fcfe8c918ea81248151a36763c7a01f26efcfd60ed0f7a2c96864ad24c247caf4d290f07faca857bd71e82c669db92a8580c079fbf4c8f63ba3e0ba  nimbus_beacon_node
2d24c0a29f86a9d99473ea0b40629d36e394a2fa270f3f77ec6fc67d90cadb5977a757d7088141cb739741e36dd136e7dca2eac00d5793d856d69a15c33e9139  nimbus_validator_client

v23.1.1

Notes

Nimbus v23.1.1 is a high-urgency hotfix for users who have already enabled block
history pruning after upgrading to v23.1.0. It fixes an issue where the client may
fail to start after the database has been pruned.

Fixes:

• A crash on start-up after running the client with --history:prune option - "backfill block must have a summary".
  #4554

• The validator-monitor-details option was accidentally enabled by default in v23.1.0,
  which lead to significant increase in resource usage.

---

Nimbus v23.1.0 was a low-urgency upgrade, introducing support for on-the-fly database pruning making the storage requirements of Nimbus much more predictable on long-term time scales. When pruning is enabled, a typical beacon node expected to consume around 60 to 70 GB of storage. To take advantage of the new functionality without facing any downtime, users are advised to sync a fresh node through trusted node sync which now features a quicker history backfilling implementation.

Improvements (v23.1.0)

• After a trusted node sync, Nimbus requires less time to complete the block
  backfilling process by downloading the minimum number of historical blocks
  mandated by the spec:

  #4421

• Nimbus is able to sync in optimistic mode with the network even when not
  paired with an execution layer client. Please note that this mode is not
  suitable for validating:

  #4458

• A new --history=<archive|prune> configuration parameter controls the
  retention of old historic blocks in the database of the client. Enabling
  pruning on an existing installation will introduce a significant delay
  on the first run, while history pruning is taking place, so we recommend
  starting with a fresh database by executing a trusted node sync:

  https://nimbus.guide/history.html
  #4445

• The validator monitor is now considered out of BETA and enabled by default.
  To keep the number of created metrics to a reasonable level on installations
  with large number of validators, the default implies the previous behavior
  of the validator-monitor-totals flag:

  #4468

• Full support for the latest Capella/Shanghai devnets:

  https://notes.ethereum.org/@bbusa/Zhejiang#Nimbus

Fixes (v23.1.0)

• Out of date metadata for the Gnosis network bootstrap nodes:

  #4460

• Potential hanging of the client caused by inappropriate activation
  of the TTD block detection on beacon nodes created after the merge:

  #4486

• Inappropriate case-sensitivity in the --log-level parameter, accidentally introduced in the 22.12.0 release.

  #4523

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
671bb6cd47cb623c3072a8a589e141017ec7de8f6909bd5c2b5efad0d8f9a11be22e37cf4fca7e79964a4079590ad00644758b8b94df5cd18fb57d71b7359063  nimbus_beacon_node
1c31a0d2a74c15120186378be1e87ded8a196ed4c9d7f983c986eaa5ab2cd6b25aeb7bc70298556cd46dd98b41600c6e662fab120920091e6f75487a7873e2a8  nimbus_validator_client
# Linux ARM64
7385038f194c1c54e23312b4e9049bef4115854153d12ed0a6d417b959c2c409f8855b46a04ddd4373e4d2c6a139a9fe32acbafd3d5ba43e2b4dac70c31b4dec  nimbus_beacon_node
7d2ecf63287baec9ceafc70fd6006da6460f6db05681755e70ee7003bf74d9fda8892d9faed839445991756894ae54001daf104a19f006a5a5689e3e84481ef3  nimbus_validator_client
# Linux ARM
87da1b94a3cde812039a1d9fa2867c3fc9f7a36d682b2bfa220a3c7fe9aa43921695e39484c3060aebae30868d9760128cd3f53f35b9c11c9f133e0bd5385b18  nimbus_beacon_node
19a18cadd471836cad7bd8a206326e2aa9a04f285f20a2ae1373c655aa91821bd895baf03b62767dd9ee594d2b3a6a770986f534c7cd78201c29ad10c329f344  nimbus_validator_client
# Windows AMD64
763026fe40ba43193a595ca217ba6171ccd94010afa3455f2a099a28564ec2c596c59fb1faae5d08a117d5c31e791803c3c4ae5dfd6ff8f5b1baf78ed8577709  nimbus_beacon_node.exe
5b239a8f0c6599eda9246e82eea7a85947d3e035fd65f6cb2bfe6300fb1b1aa23d491db6ef5f6f72ad845ad7ae120c3cbf3b341c14d40e91492d9c2c5b9224b3  nimbus_validator_client.exe
# macOS ARM64
012d592fd343f906806b8e0450a53f0cc2f8ff59be34f38aa100d766df24f4733256cad5c2ea435a25fa4afd167a1b2dfe1cb53f9a9f44b1986d961cb0bd41ce  nimbus_beacon_node
9b8ef7c4cabd26c83ee34426e274d157219440572b54d316dd9b3948c45775372fff1cd446097918be951f1aaa43ec8bdb75dc88b2a971a431320717785caaa9  nimbus_validator_client

v23.1.0

Notes

Nimbus v23.1.0 is a low-urgency upgrade, introducing support for on-the-fly database pruning making the storage requirements of Nimbus much more predictable on long-term time scales. When pruning is enabled, a typical beacon node expected to consume around 60 to 70 GB of storage. To take advantage of the new functionality without facing any downtime, users are advised to sync a fresh node through trusted node sync which now features a quicker history backfilling implementation.

Improvements

• After a trusted node sync, Nimbus requires less time to complete the block
  backfilling process by downloading the minimum number of historical blocks
  mandated by the spec:

  #4421

• Nimbus is able to sync in optimistic mode with the network even when not
  paired with an execution layer client. Please note that this mode is not
  suitable for validating:

  #4458

• A new --history=<archive|prune> configuration parameter controls the
  retention of old historic blocks in the database of the client. Enabling
  pruning on an existing installation will introduce a significant delay
  on the first run, while history pruning is taking place, so we recommend
  starting with a fresh database by executing a trusted node sync:

  https://nimbus.guide/history.html
  #4445

• The validator monitor is now considered out of BETA and enabled by default.
  To keep the number of created metrics to a reasonable level on installations
  with large number of validators, the default implies the previous behavior
  of the validator-monitor-totals flag:

  #4468

• Full support for the latest Capella/Shanghai devnets:

  https://notes.ethereum.org/@bbusa/Zhejiang#Nimbus

Fixes

• Out of date metadata for the Gnosis network bootstrap nodes:

  #4460

• Potential hanging of the client caused by inappropriate activation
  of the TTD block detection on beacon nodes created after the merge:

  #4486

• Inappropriate case-sensitivity in the --log-level parameter, accidentally introduced in the 22.12.0 release.

  #4523

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
7f362aa740007b4d84991c6b1ddd7d309b2b5a33969841a87f6c681976322078f5efddec85428363c822a35eaf5520605cc974edb58863b7e5506568459a473e  nimbus_beacon_node
d79df66d12ce904044a7fb2d4e8b86a722ba46b617b02bdd836aa710531ddf45fd5fb10d2f34403d24da59adc1d01d13d28670f0fce795b08aac7640de2fb4d6  nimbus_validator_client
# Linux ARM64
162a55dff1bd54b84e5aa3106e11c7a32866e7645f835f2a098d2db0ba1a3f0bd6e1a437ba9370d6f99acb38e43d8a5972b2fdf92fd87211b7cef1b15707cb14  nimbus_beacon_node
14bf497efc89427b9e636faeb2969edf24b1325be3fcd997de702e1ca18987fea6fb4a0a3e314a087287aa2d8ecb365745b4e1d00f64d2922bb96a056b58b2e2  nimbus_validator_client
# Linux ARM
f93ec36d94faa4aa045d363b27cf782ff0399d57aad9937ba3f0f22a0435873366f873987ead181e4c254938a2f539496f2aecda27686c2f63d037d7c19b3fdf  nimbus_beacon_node
c043d90d2b3fa32deb7ddb6735ee2941b641bacf9ed7dbc3093768c712df24b3c44dc7e50c45fbe772ca910dc88778c0a1a027bf0fdadc4e6c9a69aadd35fdb5  nimbus_validator_client
# Windows AMD64
98aec384a734f464544bad4741ed72458312b18b927b7cc1e98c4b1beb71d778f8de0d8e025fb0e29f813648e1696aedce794319ece834b8196e7c91a4b16d34  nimbus_beacon_node.exe
4c21b7e3411d7d2edec48ab1db98f73b2b80a191357c778c7cb88a35012398f04e7b2c1ba6cb34e26df477d167d70f4bbc196fa1c27fd9bb0e8dd07115e410b5  nimbus_validator_client.exe
# macOS ARM64
b68cf04e4f480dae3dff511a0359f7001d32853df0202108f0c1b62d100c30749a388b9fda78ead6e3ee2e26f527466f405851b0269c16a32f94442e357d2e9d  nimbus_beacon_node
09e93ccc56e0f4bc00730c008dd878f10cce4fa9a221de5865d938968daa80b6afa2f3fc03765bc8f70e7410dfa42567b6ef368c4831f2f9f1e52b894a950f06  nimbus_validator_client

v22.12.0

Notes

Nimbus v22.12.0 is a medium-urgency release which improves the doppelganger detection in the Nimbus validator client through the use of standardized APIs that are compatible with all third-party beacon nodes. Furthermore, it addresses several inconsistencies in the behavior between the stand-alone beacon node and the validator client. This release also allows users of trusted node sync to skip downloading the entire history of validator deposits by syncing against a server that supports the standardized /eth/v1/beacon/deposit_snapshot REST endpoint.

Improvements

• 60% more efficient block replaying speed brings faster REST responses and
  more resilience on the network in the face of heavy forking activity and
  non-finalization:

  #4435

• Support for obtaining a deposit snapshot during trusted node sync from
  servers supporting the standardized /eth/v1/beacon/deposit_snapshot
  REST endpoint:

  https://nimbus.guide/trusted-node-sync.html#skip-syncing-the-history-of-deposits
  #4303

• Official docker images for the Nimbus validator client are now available:

  https://hub.docker.com/r/statusim/nimbus-validator-client
  #4439

• The skip_randao_verification query parameter is now also supported in
  the /eth/v1/validator/blinded_blocks/{slot} API endpoint:

  #4435

• The doppelganger detection in the Nimbus validator client is now based on
  the standardized /eth/v1/validator/liveness/{epoch} REST endpoint:

  #4381

• The validator client will now use with the standard exit code 129 in
  case of detected doppelganger on the network:

  #4398

Fixes

• A potential false-positive in the doppelganger detection logic:

  #4398

• A potential hang in trusted node sync:

  #4303

Breaking changes:

• The built-in support for the Ropsten testnet has been removed:

  #4280

  You can still connect to the Ropsten network by specifying its
  metadata directory on the command line through the --network
  parameter.

• The statusim/nimbus-eth2 docker image no longer includes the
  nimbus_validator_client binary and the shell scripts included
  in the release tarballs. Please use the new dedicated image for
  the Nimbus validator client.

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
c6e211548d5932a8aa809142d760c33b383262ab3ed19ef8e7924e386f294d006db24b75ab98db8b2e6da82733775ed833882fbc752c2662ff43107bfcb1a80f  build/nimbus_beacon_node
fdeffb77e7db46d19c221dcf789576ae35d1f02ce69229079891a04e3ccf3b552cfaf696e4471a033fa494470b8b80df1b479dd58c9687d73fba93af05f5eb3b  build/nimbus_validator_client
# Linux ARM64
08948874428b42fa57218a77e0686431e07ad945c96b7845500fcc14963380c56e264aa298cc6f6d94f425f8d2353153b1c2fdffa9f9a78d99145daab389a608  build/nimbus_beacon_node
edc20ee3a13149ee63f6f63d44576a504d0511663c9208e5595ab72c052aa526eb7d884cce1872192852f75187c7eee00751309e8eb7ab530972f3d0a7fdd6f3  build/nimbus_validator_client
# Linux ARM
5e13e1a81fd4b34ac611834785c8c993b2808f897575022d524355450e20cee589176a3b0034725a84c1e8355502e80f581a04c34dc2263dc79c9760b262832b  build/nimbus_beacon_node
6b3c6dfb22c4b96c918dbbf7e7443f0ff6d82fad885528325117743ea18167441d5f80d91d384e102d15077875f96c9ab36a654a56f623ca18e27cb14d42444f  build/nimbus_validator_client
# macOS ARM64
dabc3ee91b34d717daa88c0cdce0e719c58c7ad50bf39c8ffa426eabf1a72b6f8ea1c459554af29006fccaa3292fe695daf8be4dcd698f0b81a21ce80924e2e3  build/nimbus_beacon_node
84eb8ff8ceac1dda8f0e52aa6fb3386c5203a55f35e128209b806f242f57813519a17a82475c29dbe4c4ed7c6ae0a64ebe1301e8b036949f7a495f1cf86e6ff9  build/nimbus_validator_client
# Windows AMD64
c56aab64244212a46a0eae61c2eff47618699ee75bad973a9f3f58575504124cb3a726ccb93ffa4012c29c4a872e4d707893ad3f658f0b35bd2612424f7c5d8a  build/nimbus_beacon_node.exe
9dac6538ced29da554e08176d12a44cf9d817e0e3117859ddf861371eb338874608b1f64525fb0bc8b192e4ddeb8f42d0c63de1eabbbafdcf95410c6c8e7b4d7  build/nimbus_validator_client.exe

v22.11.1

Notes

Nimbus v22.11.1 is a high-urgency hotfix for all users who are running validators backed by remote keystores and web3signer. This update addresses a compatibility issue that may result in missed block proposals. If you are not using a remote signer, you can safely skip this release.

Fixes

• Incompatible encoding used in the web3signer block signing requests after the merge:
  #4407

• Ignored graffiti option of the validator client:
  #4417

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
1d496c8e6e02470cd59217041c26b1ce457af4a46f38adac45d30695320ad25218178108346ef153eff66dd7898a446c1003a6b59ebdef0173602552523a6dcd  nimbus_beacon_node
1197d3f96049d2091916135869587ebdb9ed71439cb679427b37ee8fa5e96291ad50cda7428b804566c0eb013455ffa0cc21ca03f2aa0ac69da95010bf30f60c  nimbus_validator_client
# Linux ARM64
765b0b552d112a14659eb99a988fd5e13085af78de94ec01f03a7418d0a9d0ee043d4265822ca0401fa868760bba16ad7ee204712184622eefdeace0c5e096ea  nimbus_beacon_node
eb9a82c8ca5724b0a8f3ef6f091d225cf9969aa35292192c3b986630ab9febe83ff8895f66bf41bb09262809fd649ff2bc884f5c1f13197658c41bcc51aa2c20  nimbus_validator_client
# Linux ARM
825d4bba0e5499eb2e25e493e436762c62356f85432195ccf91b4b67bdc92e0923642ed7f9ea95ab2de8d2487ecf9e1d185b38a3ed59bedf45617e78da16e9ea  nimbus_beacon_node
282bf52dceaca693848f801b08a3eaf44a7732d41c07aa99a8522fa69bd084740396decd9052cff2a7e596be5e3d3f48fe378dd2d62b24ecb8328c2d826cea28  nimbus_validator_client
# Windows AMD64
1aba746af65d62a4358d52bfb409da9b41a18b3fb93ea22e6b9e43b8d458fc64969e48cd9966e7ca4b662cfdb451b1f309f7760acce2dfa580b75555c3ba630a  nimbus_beacon_node.exe
863ec432b0472ea17f407d6dea6dc267368631032ca56945cb3bad163dcd958d7aad225e14326f08e7481ebeb8e67a7a1f9cc9e5dc21a7baabfe8d3daefa5c42  nimbus_validator_client.exe
# macOS ARM64
a643058c359ff3a288b2bb826f5a2181046a7a97e66ddebfdf520e1aae798e547496d50cd4feb933899660d63d33ebeaa0937cc6998bf308b7849366a4e0ce42  nimbus_beacon_node
cec0f3ead6cea121d37b6506a4089c92f9373108c1039112a5451f0a1ef3314f73fb245d96f7c8d5a75757c3415856892c3fa669feddd959b12f82911dc2e192  nimbus_validator_client

v22.11.0

Notes

Nimbus v22.11.0 is a low-urgency release, bringing the first
production-ready version of the Nimbus validator client.
The validator client will enable advanced users such as professional
institutional operators to take advantage of features such as support
for redundant beacon nodes, enhanced validator privacy and
distributed keystores. Meanwhile, existing users still can use
the streamlined stand-alone beacon node setup, as this mode of
operation will continue to be supported and improved.

Improvements

• The Nimbus validator client graduates from BETA to production-ready
  status after numerous improvements and fixes:

  https://nimbus.guide/validator-client.html

• The Nimbus beacon node is now compatible with validator clients
  taking advantage of the /eth/v1/beacon/blinded_blocks end-point:

  #4286

• The validator keystore loading during start-up is now 3x faster:

  #4301

• The doppelganger detection now protects validators added
  on the fly through the Keymanager API:

  #4304

• Fine-tuned internal task scheduling can provide better
  quality-of-service protections for performing all validator
  duties in the presence of syncing peers performing large
  number of concurrent block download requests:

  #4254

• The --optimistic mode of the beacon node allows you to
  stay synced with the network even without an execution layer
  node:

  https://nimbus.guide/optimistic-sync.html#optimistic-mode
  #4262

  Please note that this mode is less secure and intended only
  for non-critical information retrieval through the Beacon API.

• The Nimbus build for the Gnosis chain (available when compiling
  from source) has full support for the upcoming merge:

  #4330
  https://forum.gnosis.io/t/gip-16-gnosis-chain-xdai-gnosis-merge/1904

• The stand-alone light client (available when compiling from source)
  now preserves progress between restarts:

  #4371

Fixes

• A small risk for missing block proposals was present under heavy
  forking activity in the network due to potential inclusion of
  inappropriate attestations in the produced blocks:

  #4273

• A new batching approach for the registration of validators in the
  builder network will prevent the creation of requests of excessive
  size that might be rejected by the network. This was a problem
  affecting testnet nodes running with thousands of validators:

  #4364

Deprecated features

• The --finalized-checkpoint-block has been deprecated.
  The client will now download only the latest finalized state
  during trusted node sync:

  #4251

• The end-points /eth/v1/beacon/blocks/{block_id},
  /eth/v1/debug/beacon/states/{state_id}, and
  /eth/v1/validator/blocks/{slot} have been deprecated
  since they are no longer usable since the Altair hard-fork:

  #4279

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
fb8295ca0dc7d2394660b778a9081a46a4df877890d581f52fb9420e6e1160685b66ea254d0504851fd7367baed716e16d5e1c44249e4be7030cd89e14ca4067  nimbus_beacon_node
363aa43371b1e341db1f7f6c22f04c95705046537aba149688ca424aecbb42368576beae02e8204a5effbfda6af5153b45011da55c5b8b7ad69f4ac518a9c294  nimbus_validator_client
# Linux ARM64
f6c7e45afee8c18311ced3fb5004984e72eb283c3732ab065a6187513c21c7ae1d91f13252df3fbdc8f9c8fc21123c50891a747c26da9bcd266e9201fa89420a  nimbus_beacon_node
aad960e51b977a9d966da88d5b946ea9c754e65cf2a6acef8d0d5bde93712dfa3164c5db076fc2e82db7e87f24a72e7058ee7fff7b2127a9faf4e00e56ccd7f9  nimbus_validator_client
# Linux ARM
8f6698fb928d7e5a66584157cebba84d291f5a80d83411117e4e739a9349823e3609789c210625f593f5791e6c343687bb7ce0af2fbe58231b20a9740349fa45  nimbus_beacon_node
04f5b8c3bc873a9fd8ea52dc1060f9af61ae20666e8616328a601a453058f1c78618e2111797daee40a6fce6998c40ff3b02b79ae5837351cebb398bac128e06  nimbus_validator_client
# Windows AMD64
abedd5cb7f090ecc711aa825c5e72738995d7729be854bf2eefb784259c4b9207227f4beca6f1cb3e792c86945f7741ba0efa1fc046a43fca1fe46adbcdcc965  nimbus_beacon_node.exe
f4e2e773f4b29dd99293c9d13592c268b9eb63be199bd6750cec6db199baf78c099f718aa67b65fa046dfd6320c49955e00629ba77a5e87dc871b1066179a9c7  nimbus_validator_client.exe
# macOS ARM64
cc585c3afc21371ec12f983c9af3b53fa527ec980ae46484bfd014255754b9e6cc929f746f5a40752fff63d6777eb6c59027b92cafaad4625b4a966a03be5abd  nimbus_beacon_node
087b4216346d525a5ed95a260b8bcb5883391e794c2a266d7079fe60d9ae661458e2dadb5051f74a777e96a5d535137f0d5fbd69bbec3edc0d16c7027a45ce59  nimbus_validator_client

v22.10.1

Notes

Nimbus v22.10.1 is a low-urgency point release introducing support for the official light client REST API and improving the stability of Nimbus when paired with an external block builder.

Improvements

• Support for the official light client REST API:
  ethereum/beacon-APIs#247
  #4213
  #4232

Fixes:

• Nimbus was slowly leaking file descriptors when paired with an external builder:
  #4235

• Nimbus could potentially crash under a poor network connectivity to the external builder:
  #4222

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
0dfdd9da633fe94ece739f42bfddf579a5a28e8846ec72e9f503c938258b91a9bc4f82f67ea36239686e3a4c717bae0ed81da6ab30171f00c531d370868c9190  nimbus_beacon_node
46a848e58ddf89fc8de0bbdae2f82208a3507f4d45aadd527d22b59a7fac05b0a357de610289a728090df10c9cc3cb8e685eedf6429275b24f4ede56caa12612  nimbus_validator_client
# Linux ARM64
ed8ef60d39c96e2ade545afdc79763c7256006955adca4e690465e0e28a69be1b40590404744310490eb6c1e91c5c07baef2a681bb8c195f9c7b186873dde941  nimbus_beacon_node
ecaeb027603321693a84791985ed1a02a7f50dce61596b03a11a047251e9d1c60884adc914338e30e9bc320c21aa7d02f80ade5fd6044938fb2e012e269dcfe4  nimbus_validator_client
# Linux ARM
db829e58507eb897ae091c17606085351a05cfab28a1bf921c91b4b79cec7261ba364455b48f7139c68b88c29c69b690c5ef87dcbd2598ee278f4c6c908c8677  nimbus_beacon_node
d910aa025c80b029cb2a94b2d6f6c5057eb85fbc686d11d9406501f6d412f347db8362c5736c78ee6310a2d020b5553c9e0c6445a094c30bee0c71d09b16cfda  nimbus_validator_client
# Windows AMD64
1003714d43affc266a9f187713a3fa5fbcc33c1a37917b86e629cd023c7438488586cca47c5d7f23ec5306148b9783754ff44f5aee7c093e737044d6c5b61800  nimbus_beacon_node.exe
3a971873addbffc69a724ca4a0d63eef6da9f36d69ee5ed8323fe452e7935f77476e56db22c748dd5ed45f5ff48330d4a62476a70c6aa07cd86ce40789793ef3  nimbus_validator_client.exe
# macOS AMD64
e83685fcb0e714e607f28c35867776bad664cac1b3339a74924b4f90dbb14277e5bbe3a0ef937518a7eb34444993d584d4be03bd4dffb8bea614e610df550316  nimbus_beacon_node
43cb05ad5a073ce1e811fae2c93a74d7de80b69556455eabcf48cc751412eb448f747c4c0c2fda6fd018f75c462f83ad112550525b9ffd902e4b5e30666a031a  nimbus_validator_client
# macOS ARM64
d7acfc2b1f43785ce54238ddbed5792e50548c5037a83f71c930f7e869c2b15f3fe3c841f0dbaaa4315f2166283cd96c7d25721b8500318d115d6fe4c33bba99  nimbus_beacon_node
7057c8a896b1b345849ccb6ed55d23fb5a3bfe8d9ca2dc49e72e44a818d65cc9bde4639fe2b20cf8f76995d4f13db9f0d90efc82a091351d720387ffd24dbcdd  nimbus_validator_client