Nightly build ("unstable" branch)

SHA512 checksums

# Linux AMD64
ba862d22b0286f18c81ddf739ca7a4c532e68c1fc5cee9407d9201e373829151380a1e58369d3c2a80db1e04d29f0bf9a27460382dce137b8a53cc1d51a5eeae  nimbus_beacon_node
796cf566479e545e80cd6a7ec95a10bcc9241cb8b75e015c5f1fab5c37efe6260810249428a6417c0e340de730cb6f0e68dd642182e965ba8a9e444ffb8891e9  nimbus_validator_client
# Linux ARM64
51f4b0ad19423120ff89517494379abf50bda7242de3c20fbeec1d36250f7954caed2b54e4bacbb7c2264005b7c7283cef2b5eda9c66100bb9c5b0a2d152fc48  nimbus_beacon_node
85b2cf78748d8e8e044f26529b9568ae18e322e0557c8e9ac584c55579e44edd6ffc117d0e0db782a0c0763f8db25ca565f761322fbed82f7fb9c929b8d783a2  nimbus_validator_client
# Linux ARM
1058c56d453c41741c9e169a6a2c0d1c37b59f34c40771a8aa354a6a843ada68b13ba13908048ca9962c58754f0e1ca37ab7c1ddbfec49a1497d0f5db4b168f9  nimbus_beacon_node
a65b2f114e76d9532988854ef73b1bda01fb667f7e56575fdfaf7d7acc3c3e929fa2c3cc2e1ba59accb90e78a4276b06326f567d9feab5af9186b48ab57f73fe  nimbus_validator_client
# Windows AMD64
2da4f2f211c5b9827f9a6a27dbb852677d91e04cae8709b703bbb3a86f737948c6dacfa44f9f7352fc2437f71cd51bf3083fee0ce8f16839d9a000945b2458e3  nimbus_beacon_node.exe
47862d1a7998f8cc168221a3249e9fbde6d13e754b05829b263869d4059ca76984404c25a1bc7bf898d527bdf86bc2858a832a8475b0919dbc9eefbe4cb0c6e7  nimbus_validator_client.exe
# macOS AMD64
d81d8d5282dfe3205d6b7f949536a46ff9e23eccdb4bc5844fadeb657722d21b935dc25eba02cab289a84799b86f4ef6679a3020ab5774cc1d634fdd88a07194  nimbus_beacon_node
c104acf3f1c75c43e851fc63e1aecb7827ab54809df3b32feb2ab188f661c14c8135428b8a80cc3035448cff9ed52ae29dabaea38b2ff53707a95f4e643dc454  nimbus_validator_client
# macOS ARM64
0842c6e471df522c1a2f6fd7405c1ff55aecb948e6339357130d5ea9e94acf6aee5075080b51ec5ee23b074a9dd28989b0de1b53b6e7da71bc2c98c2dfb61911  nimbus_beacon_node
7d3959fd0d0d4c96ce71275dcef987a8b373b5fe0e592d570c34c00dad8c3ad7014c447921c06651dacfdc71d75987b987092f19e47b4c07a100669b91640ae1  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

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