Skip to content

Releases: status-im/nimbus-eth2

v24.1.2

24 Jan 22:55
6c63a54

Choose a tag to compare

Notes

Nimbus v24.1.2 is a low-urgency point release bringing full support for the upcoming Cancun-Deneb hard-fork on the networks Sepolia, Chiado (Gnosis Chain testnet) and Holešky.

Improvements

  • Nimbus v24.1.2 includes full support for the upcoming Deneb hard-fork in the networks Sepolia (30 Jan), Chiado (31 Jan) and Holešky (7 Feb):
    #5795
    #5725
    #5772
    #5796

  • Nimbus no longer skips attestations during brief loss of connectivity to the execution client by attesting to the last known valid block:
    #5313

  • The /eth/v1/events Beacon API endpoint now reports blob_sidecar events:
    #5728
    ethereum/beacon-APIs#350

  • The Nimbus status bar and the "Slot start" log message now indicate the time of the next hard-fork in networks where it's already scheduled:
    #5761
    #5751
    #5731

Fixes

  • The HTTP headers eth-consensus-block-value and eth-execution-payload-value supplied to the /eth/v3/validator/blocks/{slot} endpoint were not using decimal encoding:
    #5741

  • Block headers within light client updates in Deneb-transitioned networks had incorrect zero values for the blob_gas_used field:
    #5763

  • Incomplete responses to blobSidecarsByRange requests were inappropriately preventing the client from achieving the maximum possible syncing speed:
    #5766

  • The Nimbus validator client was not implementing the strategy of using the withdrawal address of the validator as a fee recipient address when one is not explicitly specified. This was resulting in a failure to register any validators obtained from a --web3-signer-url with the configured --payload-builder-url when the --suggested-fee-recipient option is not provided:
    #5781
    #5730

  • The /eth/v1/beacon/states/{state_id}/validators Beacon API endpoint was not compliant with the spec in the absence of the optional status field in the request:
    #5762
    #5758

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
ff9c10c29d514175ad03faafa38b2bfd9b94b1ac27d2033c76ed760fa362a921793d0a4b0e651f9657ac9eb7806e5ee75a8c8a6b30410bf094e1280c5ba0a152  nimbus_beacon_node
d6b4faa06f1e47b5b64344a8d8d13a10dff8b85be5465eb3983bd89c04a8245391cf58e0d963d7dd8dff8751b87dd9e3f1684225d8d39cdfbdc4756fe062c92e  nimbus_validator_client
# Linux ARM64
c4a1b311608fd6fe01f14adb3a03d0586b7f947df8bcab94ba68bd773fd500caa1d87de723af59fdc882e8fb0d69c83cf7d6ad2b7a7bab57d03bf0e2d9422f35  nimbus_beacon_node
a0d5d1bb1bdcee9de2ce026afb0f882eccf367dc061fa9bbd016b9c0815266cd608f542ffea27fae757d4110ca552943ac0a392dfe4a14a1438cd605044f2e79  nimbus_validator_client
# Linux ARM
807054e211aae987a466eb4514b3e62f73ac5604cac8f892b8140a3606053a54b713b00f457ba52be859970af72f8c592ff032db0fe798bbd0ae49875b35480c  nimbus_beacon_node
e32613b72d8f993fc915f9a1406d4309fff7ae86067d8dd669596ed6e78efe6ec24cc2f077489df4d75229e2764c7d5f381e6c8de828a9eff3181c8e963b1fe8  nimbus_validator_client
# Windows AMD64
c3899c37c255f7cb2b255b62783240e62d76336ea78aa661406d549f56a1aeb1c1b4c043c7c4d151b5d502b46927482cdc6f249059e4ad04fe3b643e57310147  nimbus_beacon_node.exe
8225abb4784882eeb29bba8e01c1841d4842a36f65a3cc4834f64a4f01ac46fe27de15eaae7cb3abb88c21c41a91c3d6d42c9e6d1abdf3052eb1900473b0fdaf  nimbus_validator_client.exe
# macOS AMD64
19be881788bebb5f3bbf9c2930f9d42f8b43a46b22eb7759d2dde88b4e0db581682b0d238df994681450d41f585a5141f6945c2d58ae8277b6b639ce522f50a8  nimbus_beacon_node
10fdaa3b3d6c248f9f84b8695af396745aa607e87edbd013403ea69dd344e8ef01ea35bb86ad6083111f61371a2ce7872dbe33bd8a5e04c4d9d948d8881d1193  nimbus_validator_client
# macOS ARM64
580f18031f5925c7b1aa0e1fcce65d9ce341e2bfd5d58a41c4f52234143a58303c6f4b53e30a185673890ac87aafcbabc530c9740279bc94511274bcf1c942bf  nimbus_beacon_node
2e9a4666c29d35cb510df94d131ae36ebdfc7f1dfed76b0fa25a240d321fad4506650d2cf9aad8e412fb0acf97acf896c51b36fbee5181b05f54c2ca82b977bd  nimbus_validator_client

v24.1.1

08 Jan 17:57
0e63f8f

Choose a tag to compare

Notes

Nimbus v24.1.1 is a hotfix addressing a problem introduced in the v24.1.0 release. Nimbus was crashing immediately after being connected to an execution layer node which is not fully synced. All users of v24.1.0 are advised to upgrade at their earliest convenience.


Nimbus v24.1.0 was a low-urgency upgrade bringing full support for the upcoming Cancun-Deneb hard-fork on the Goerli testnet and introducing the /eth/v3/validator/blocks/{slot} Beacon API end-point that greatly simplifies the implementation of profit-optimising validator clients.

Improvements

  • Nimbus now includes the latest Goerli-Prater metadata, scheduling the Cancun-Deneb hard-fork:
    #5680

  • The Nimbus beacon node now supports the /eth/v3/validator/blocks/{slot} Beacon API end-point:
    #5474
    https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Validator/produceBlockV3

  • Nimbus now accepts POST requests to the /eth/v1/beacon/states/{state_id}/validators and /eth/v1/beacon/states/{state_id}/validator_balances Beacon API end-points:
    #5632
    ethereum/beacon-APIs#367

  • Nimbus now follows the latest specification regarding the deprecated /eth/v1/validator/blinded_blocks/{slot} Beacon API end-point:
    #5639

  • Nimbus now uses the latest set of bootstrap nodes for the Gnosis chain:
    #5656

Fixes

  • Nimbus was sending unnecessary redundant forkChoiceUpdated notifications to the execution layer:
    #5635

  • Nimbus was returning incorrect responses on requests for blocks at empty slots when working with ERA files:
    #5641

  • The Nimbus validator client was not sending Builder API registration messages at the correct time:
    #5663

  • Nimbus was ignoring a specified --jwt-secret option when no --el option was provided and the default localhost URL was being used:
    #5671
    #5665

Breaking Changes

  • Machine consumers of Nimbus logs should be updated, as the abbreviated value of the NOTICE log level has been renamed from NOT to NTC:
    #5634

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
e10dca823fa1d880f13ff0d6e6f6ecea41bb1e774e3897d021a0fcc1d4ca02f3100a7db0316f495d708a8b7c1ffc2076d1ef924151de0ee4fefb54a4854b267b  nimbus_beacon_node
f1b72938621ea5dbbd03a71bcfb4f0a762b37072808912d9fe0cda0ba246d9d60dcffa0c24a2ec9041e5efaee8205549d0ea19d609cc0244a3ee182996f038bd  nimbus_validator_client
# Linux ARM64
716b7b8772280a2939c210afce6e3f53c7a0a8f88db272ffabe3fb9fc16dffd76344eaca3e83f6e15f245503faf1d60075d98b1a7897bafcd1c888377d389d26  nimbus_beacon_node
7364dfbfe776f2abb41d143579f63a81abc115726cc80082449df5a1ba069c8d5996611398dbb0af898fc3e4ed121a2225ade7a338aeabd58808195b2a72106c  nimbus_validator_client
# Linux ARM
dbf45af0512bbb1750237a1ba8cfd03797139c3ba667c363e4bffd65b37f0654c1f256d3405f8bf79c09ae970bb6dc8fc098b81195ad38d22b549642b2bf444f  nimbus_beacon_node
10d3320003fe7172b2bdd2d15766f108e338aa3d25e81b04ba8a2ff92a8a35e7c84237b94fad774c3d3a90935182e5bca2677216000938481f98611e9d99164a  nimbus_validator_client
# Windows AMD64
a9c8f04854273068f8cd0960db957adfc6a3f1a2247b9226a77400174ad924ced73e5013d8f201cd02a2ae0806630e2ce5ba0e33a1de4efa15f78de5104622b7  nimbus_beacon_node.exe
83b57080ad6128e144337aeb237766959e8ede3b5711736a4f67ad9805ff7aa8fede8f9d47ea741677d421f5013381b337f3946bc0e3ae58028d5193f7ddb191  nimbus_validator_client.exe
# macOS AMD64
b4e429e28c860db9de9cd2beda7c33ee51da5f669759e3e7ff49282a6a6a97e57fe5b4713fd00e000da11e09e3aa269693b0bf81b05e52df3a5f713ce7ec54db  nimbus_beacon_node
11d79e30e4ea0daa35fe4ac76a7863d9d3665860d889552ec296b2527144c3a636f2ac49be374f20de3ad423016a0699682aaff6b6804448215da88844f5a2c3  nimbus_validator_client
# macOS ARM64
f1061d4fb64fe72b60ec1d4fd5bb6483fb80957a81d536b57d3b1cb193bbd78d4a948166680b621f3c55c24667a837f892e350122cb9611f595fa79a272299e4  nimbus_beacon_node
e92e0a14e36a3d9a6e0baadab7b631fd7913ed3b75475a7aca7f9c183df65acb11f740074938a58c713218791160b260f8c0feb33d8b2724610bc31250a6f011  nimbus_validator_client

v24.1.0

04 Jan 00:32
v24.1.0
00ba72a

Choose a tag to compare

Notes

Nimbus v24.1.0 is a low-urgency upgrade bringing full support for the upcoming Cancun-Deneb hard-fork on the Goerli testnet and introducing the /eth/v3/validator/blocks/{slot} Beacon API end-point that greatly simplifies the implementation of profit-optimising validator clients.

Improvements

  • Nimbus now includes the latest Goerli-Prater metadata, scheduling the Cancun-Deneb hard-fork:
    #5680

  • The Nimbus beacon node now supports the /eth/v3/validator/blocks/{slot} Beacon API end-point:
    #5474
    https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Validator/produceBlockV3

  • Nimbus now accepts POST requests to the /eth/v1/beacon/states/{state_id}/validators and /eth/v1/beacon/states/{state_id}/validator_balances Beacon API end-points:
    #5632
    ethereum/beacon-APIs#367

  • Nimbus now follows the latest specification regarding the deprecated /eth/v1/validator/blinded_blocks/{slot} Beacon API end-point:
    #5639

  • Nimbus now uses the latest set of bootstrap nodes for the Gnosis chain:
    #5656

Fixes

  • Nimbus was sending unnecessary redundant forkChoiceUpdated notifications to the execution layer:
    #5635

  • Nimbus was returning incorrect responses on requests for blocks at empty slots when working with ERA files:
    #5641

  • The Nimbus validator client was not sending Builder API registration messages at the correct time:
    #5663

  • Nimbus was ignoring a specified --jwt-secret option when no --el option was provided and the default localhost URL was being used:
    #5671
    #5665

Breaking Changes

  • Machine consumers of Nimbus logs should be updated, as the abbreviated value of the NOTICE log level has been renamed from NOT to NTC:
    #5634

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
8c1ea1698f968cc34c31d093fc961ca955d329323edafe4fa4d2eb7f900774e05330863d2df8b95f9003ccba10e327e9d4de28865aaf8b65babbc10a3b707e87  nimbus_beacon_node
409ab9fa13d243e04c047369d4d0199eed416210c5faa70d3c99d7b737a2e40378b96b5e924263ce54acab7f632d3033993d499e7522301be72ea6b123fc6da3  nimbus_validator_client
# Linux ARM64
2138e821334f5990faee962b4e87021da7771307cca5124be7007c469e8887460ea84ad095e76d90baaecf4243235be74d47ea0922f693ea45c81a9bd1da3113  nimbus_beacon_node
16dc0cc729a389faa1abb1d27b686d891cdbd521be5dd9065be1dac4d24c31487da6c01a4517b94cd56f2692d102487d27214944a124672de29e790d42854b4e  nimbus_validator_client
# Linux ARM
6ebdd22e58e5818ee5ca3beac8dd6960af01e8c2e2f75872fdded50bef80c60afc6d6797cd24153727165c3b801f51dfcf8cc3d5ac30e86eac176d7f99b9b787  nimbus_beacon_node
8b415e8695e5d0f2183c62b3bc6ce035c4c14adb3d0956c03da80f94b2327cbcaeb5945e024619441855d1ba598c7b1cf1ed89b18c5665fe4fd7354802e52320  nimbus_validator_client
# Windows AMD64
723dce1d69623e3842f0456c29f27ad09ec5927d06e2aaa03a93f74c272f8b5dd026f83bbd10f7d1132862f37b7b4cc21c4c432461a5640e0312844ccbac3e93  nimbus_beacon_node.exe
216754aa6e645efcb85389af94c83a6148248451f389d3e21821942f84ffe5c04143cbb681b81c20a9d87cad68df8fb737e7f9992a12c04041d036cea76a439d  nimbus_validator_client.exe
# macOS AMD64
62731fb8eca5562425c6f002728957a80039573fe79fe4a16103d90b469e344f70b7ffa3e0f4c96d4cccc2266338e710c81afa9f88ce38725e0ec82e214f1e45  nimbus_beacon_node
db4815ea32a6841ecaad41c6ca012e1d6fff6ca649396f08377f29089999f426e41d5849ee90336b0b76cc1e6dbb6203cf2135b04d2a999b370a425e3221801f  nimbus_validator_client
# macOS ARM64
fd35d820a21bc1f9b56a17aa8d38af9d772c1ddd27508aab8db5a69034a87232cbcf1ab7333a40d4a84816711b6af751c9fdf6f47a61b646634d6dde09845f9b  nimbus_beacon_node
2189b5a46f813afa3c630dd782fc1d8e840919ba7088901cd8e8a337d91fccf2987dd8f59625b9b0e5d1e9a1c9f4cc95efc2bfa29050e1672fcdb2f0479c7883  nimbus_validator_client

v23.11.0

29 Nov 00:04
3a527d6

Choose a tag to compare

Notes

Nimbus v23.11.0 is a low-urgency upgrade bringing enhanced support for the Obol DVT middleware, further profit optimisations for the Nimbus validator client and a simplified and safe alternative to the trusted node sync.

Improvements

  • The new options external-beacon-api-url, trusted-block-root and trusted-state-root enable simple bootstrapping through the light client protocol and a non-trusted Beacon API provider:
    https://nimbus.guide/start-syncing.html#checkpoint-sync
    #5545

  • Improved scoring algorithms allow the Nimbus validator client to maximize block rewards when working with multiple beacon nodes:
    #5447

  • Nimbus now supports the /eth/v1/validator/beacon_committee_selections and /eth/v1/validator/sync_committee_selections Beacon API endpoints used by the Charon Obol middleware:
    #5375

  • Efficient bulk write operations to the slashing protection database bring significant performance improvements when operating very large number of validators on a single machine (e.g. more than 10K):
    #5604

  • Nimbus now disconnects peers who are behaving poorly with respect to the beacon chain request/response protocols and peers who are exceeding the GossipSub rate limits:
    #5579
    #5482

  • The Nimbus guide now features light and dark themes:
    #5564

  • Nimbus now honours the MIN_EPOCHS_FOR_BLOCK_REQUESTS network configuration parameter:
    #5590

Fixes

  • The REST API endpoint /eth/v1/node/peers_count was producing an incorrectly encoded numeric response:
    #5548

  • The REST API endpoint eth/v2/beacon/blocks was not handling the broadcast_validation parameter in accordance to the spec:
    #5531

  • The validator client slashing database was not pruned:
    #5551

  • Light clients following the event stream of light client updates delivered through the REST API or the P2P protocols were at risk of getting stuck due to missing notifications for certain key events:
    #5602
    ethereum/consensus-specs#3549

  • Regression in v23.10.0 was preventing the Nimbus validator client from registering its validators with the external builder when no validators have been attached to the associated beacon node, effectively disabling the usage of the builder:
    #5603

  • Nimbus was not retrying certain syncing requests after receiving an invalid response from a peer:
    #5615

  • A theoretical possibility where Nimbus may fail to start after a clean shutdown has been addressed:
    #5617

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
1f53f58373fa3540028ff17f2a46254f4d9236f844a01fb548359e3241bd9e9791abc3637b474b4e834a08c36d259b84032db01975944d5eb92aef4fbab14821  nimbus_beacon_node
efd1d5f0261b30cfb7e81c3e19ae5f2e2828a1af37a6f85c3151545a1725c68003d7331390ab4b24ac583cf62ccae448755b607c4717a7ec660bb95b4981d9a3  nimbus_validator_client
# Linux ARM64
27a2572216afead921a3c59ab1582ba3b0a06a53c753ac46a3aee4afe0122d01e2ddc4436b2518993369db06e3eff5fab88c1613dd79f1668b55be15b77802aa  nimbus_beacon_node
4affb3c9fb1c3fa83f99e6f806967db2a5fb1b474a4613ab4747d73fe6c0ed2e54391b6b8495cf438d50ee3b41ee46b824e4128bb4a9606e612a18bc0908998b  nimbus_validator_client
# Linux ARM
83b5a99eb3bc98ebfa0a6c0c609c837e3e582e03a1728487dcdcfdca937d3185c6b4ca71ca2eb835b47840ff87b965286a2266ec876f1e0cff66d71e9d87d059  nimbus_beacon_node
9a13849a1c72ca30adf54c87abaa603f1028b82f6eec5d0f4baca0e914ae422e86b42e8b9688f8031488032aa71d8819e0ccdea76d5f43bfd02d233dced8536a  nimbus_validator_client
# Windows AMD64
625ac9fabc65679f484c0988ceb664c51c5e3749ac84ad90426d8029ba49590585f377f0fdeba92ff7330a43335f9068c03c09f628a44053a6c42e202b06a699  nimbus_beacon_node.exe
78aa38439e6e6dbec7c68c33ce4e316bc06da9983409828ea61aa014d794bea968b482c954d38055f4ca36f12e8b5287d3afaa78b2c3650cb535ab1a127f30cb  nimbus_validator_client.exe
# macOS AMD64
9f6d4b66cc9ee5334c1675e748c0bc99a1fae55a15ed5ac4db3d6ef287bc2ebaccda85984f613991d35f7c86c87c857281ab80aace02abaf1e94828a2690085a  nimbus_beacon_node
df7b676f451cd9bb05c6f55c2a1eaf5f166fdc7592e1f2b6d54c81f4c0234b6788d936a872d38dd922bd6bdd54e5276bc6d032d83540e76fb93ba65fee765a21  nimbus_validator_client
# macOS ARM64
1a8efc60b0cdedf0f931ba15509393c268285cd8f1fe3f21f123f241c83fa79befd5bd7aaae99a43ed6a87f69a9a1a8bcef37f1b9ca2c488cbaa124725111fbd  nimbus_beacon_node
96dd77e672aac8d92d6339b89891260d35d18d5938ae97f1126eb3f8fc86e25fafb506caf1f900479a17c762f76ad71b57bafb49d848627d2244d16075b45ee5  nimbus_validator_client

v23.10.1

06 Nov 15:46
d19ffca

Choose a tag to compare

Notes

Nimbus v23.10.1 is a low-urgency hotfix release addressing a peer scoring issue introduced in the v23.10.0 release. The issue manifests under specific network circumstances as a buildup of gossip topics with a low number of peers. Affected users are advised to upgrade at their earliest convenience.

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
4cf9f5831d2f2d8b0c5719bd1ed03316fa88543c773316e69ece2c38613fc87ceb6c65b4dbef108c1ba7a21fc8d19761778e9f4349c8665a3303a63b4bd6469c  nimbus_beacon_node
7a3681ec69bc9b6c64b4b08610db4aadf60a5d6f0433fe0516dddd34d04e8e072cd1f1d45389b205b56572937758fee80aa99aebcd1056cc2e71c04a49120317  nimbus_validator_client
# Linux ARM64
0ae7da972f0eb2b79605fec50c6b4f59e6ac7032d19f0bccf722941b1161ed05892fe42062f3db6d87f674ab19b690c13008a7f0f10596b0f8d48e8ae85080d9  nimbus_beacon_node
867bae7c7e70653cb48974920aa7cfbeb4eead208812181dfabbfc4cd27fb890d7c1e21b2534f07974a23e0040d6d544d5b48cf1706b0326b4f2020db2a9351b  nimbus_validator_client
# Linux ARM
a1ef5db1a4cf90ddc025f5babcf4dc434aebec12707ec71aba4d5ee4050c8e4b0daab50de2064d44566552c126726590678c9b4260575e96ef27c9d5ccd395a5  nimbus_beacon_node
8b42c0046424ed305ac868f973f154b0cfa5c0ec8cf5ff97f68a77590f04dcd3d7704d0f6004c15e301501b0d8958177a135aea47126eeccc7f91938d70375af  nimbus_validator_client
# Windows AMD64
2f57d1e3452d8a8fa372fbbf776f3fe95b9910214b0cf0aa3b0f8145590fad5306f23690c6cc09ab3d5434b8cfdf3b381f58a82ad9dc77123409f0b32271ecb0  nimbus_beacon_node.exe
b06c4d936513b9a3486da34c221f3e8c53e53111795031d0191dc247c7acde2c838608331b61066178a0da950ad0022a9bd70714d818031f43a436ab6d1978cd  nimbus_validator_client.exe
# macOS AMD64
f04aa64f34be0dc2ebd1d9a96bd875720a048900ef0fda3e6096a20dae4686ef5ce35b83169dba241244ed88aadc04ba92b4b3614962ac8b80f0f0fd7a169b61  nimbus_beacon_node
f926af4725ddbea1aa2ee7726f3e59dbee100583e47456226945849e3ab57ef7d867b0f6f34fab7e7f28800ceda6336c5869b30da0c143e50d219a0716cb6869  nimbus_validator_client
# macOS ARM64
7dfcf4785114406f4720e82a6fa9db863467079a9a83123fb24c53d00395609e8f431a1ba53678f2c54ba55faafb35c0f92bda5fe64d12b30e58f10023cdb14d  nimbus_beacon_node
f89adb10a1369c9125dc77ffb2495535be02fee58a6a12170e294fd5320ecec15f40f7ad9e80bcb1496e178597a8561238a18eaa2d3ac5e8f5eef5b4ac7c8d25  nimbus_validator_client

v23.10.0

17 Oct 14:10
8b07f4f

Choose a tag to compare

Notes

Nimbus v23.10.0 is a low-urgency upgrade focusing on stability and performance improvements. The performance improvements will be most impactful on networks with a large number of validators such as the Holešky testnet.

Improvements

  • Faster attestation packing algorithm reduces the risk of orphaned block proposals:
    #5471

  • Nimbus now adjusts its own the file descriptor limits on start-up in order to reduce the risk of running out of file descriptors:
    #5436

  • The Keymanager API now imports keystores faster when they are encrypted with the same password and salt (this is typical for keystores produced by the staking-deposit-cli tool):
    #5443

  • The Beacon API now emits the spec-mandated finalized field on all relevant endpoints:
    #5422

  • Faster SSZ hashing speed reduces the overall CPU usage of the client:
    #5463

  • The list of mainnet bootstrap nodes has been expanded:
    #5472

  • A more efficient algorithm for calculating the list of block proposers during the epoch reduces the risk of missed validator duties during the first slot of the epoch:
    #5414

  • Nimbus now produces more detailed error messages when it fails to load validator keystores:
    #5480

  • The options --verifying-web3-signer-url and --proven-block-property can be used in place of --web3-signer-url to leverage the support for the experimental Verifying Web3Signer protocol extension:
    https://nimbus.guide/web3signer.html#verifying-web3signer
    #5504

Fixes

  • A rarely occurring file descriptor leak was degrading the performance of Nimbus over time in certain environments:
    #5394

  • Nimbus was not properly maintaining connectivity to peers specified through the --direct-peer option. Besides the format /ip4/<address>/tcp/<port>/p2p/<peerId-public-key>, the option now also accepts ENR addresses:
    #5427

  • Nimbus was rejecting some valid sync committee contributions during the first slot of every sync committee period (once per 27 hours):
    #5408

  • The Nimbus validator client will no longer crash when the indicated beacon node hostname cannot be resolved:
    #5388

  • The fork-choice algorithm was performing certain computations multiple times:
    #5437

  • Nimbus was sending unnecessary validator registrations to the builders when configured with multiple per-validator builder preferences:
    #5431

  • The Nimbus validator client was not able to process responses from a Teku beacon node replying to the /eth/v1/validator/liveness/{epoch} endpoint, due to the presence of additional non-standardized fields:
    #5418

  • The Beacon API was using non-compliant HTTP status codes in case of invalid requests to certain endpoints:
    #5422

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
8818443c1532e7bd9d6b46f16908238222e536d25d47f5b5b65d6edb41064b4cbf0ba4a36e3d2d32225a2af7bb0c363bd1fad944712de9ccfcc2cc8223657400  nimbus_beacon_node
e493288d010b802567381226deb244ae6d68ef80a36fd29a88b917ff7b0be7ebb7a55f52f4c80d1c7a1eb440863041bbeb3afdbe6010160a2bc54d1442480ff7  nimbus_validator_client
# Linux ARM64
cf807429fad047abd573b41ec7af40cd9dbc401ccfc98c75f9b8782c2acf37ebb7919479a5a1d4290057107da1704b6de185514776583f6b79132080010adc5e  nimbus_beacon_node
2444c594789587ab43d7309f9ae122b3893c8fde7b7e0a2e724dcfd15d18f1b15e1693cd34db7181cc55e4e5a0b8f7c454df0af94c565c72d21e25c78776173b  nimbus_validator_client
# Linux ARM
9fccc079cd043d4af381f60e01a9e11645c9a193655a04fe3c85ac681eb7af7c4f822f74dfc3793180d4e58fa4e7dc892dc52ad20722bd5cf9cd3ceafdc28fff  nimbus_beacon_node
83dbf314b85d091eb8cf0e188594f740e1141a9e43667f44bac957e1853bcc2d83d323d005e3f4c9e55c8894e84f6f34026222ec2fccbb16b5cd7e7b784801db  nimbus_validator_client
# Windows AMD64
c944c0c6f179be3f8afd62924c90bad9296b1415fb022254644fb6570e0f616a848a2270f994349633a1e47e157426828b14ccca5c8f18a5cc5efa6138be0eca  nimbus_beacon_node.exe
480efd2d7b98906d340f2460f732dc802ce901cbb381bebabc95d740fc69ecd4295782745fd821be17b63d841a7a4c8553d2e0cb0c9cebb97b48a4aa69815c80  nimbus_validator_client.exe
# macOS AMD64
129b1ceb58f1c70da1e06ed4517d9a794ae5b2f5decb9bfa794d5da2d7fd89957a5bfa4efe1cb2d12590eb8871a9ba9a4e279fb679a60ef634b437047f93315c  nimbus_beacon_node
4d5c87b0ffa0c81905f477501792e266ad9b7122fef6327559d0c122ef5c6ea5996a4256957f247e1673d5ed636b2eca55f787057e40719d2631cd001a02599c  nimbus_validator_client
# macOS ARM64
defb6771b93fa8b1536bb5c4381a68c9350ca41ea2d17aacf276ac072f5d80621af99d80bb23f95d7c1b958d08dbe18abfd9e8d73faf3303c4e53601bc3d7c8c  nimbus_beacon_node
25ad809e690b516af66c758dc39e1cc31d03fb843485ae74c1000b2467e82d2beb38e7271e3a88a4ef3156e4c0b4e8b9436edbd8b2654547c76f46cdbcc27f40  nimbus_validator_client

v23.9.1

25 Sep 23:30
cfa0268

Choose a tag to compare

Notes

Nimbus v23.9.1 is a low-urgency point release that corrects the Holešky testnet metadata after the failed start on 15th of September. If you want to participate in the network, please update your client before the genesis event on 28th of September, 12:00 UTC.

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
18da9e226b60cf200ce068b68b71ee0e99aa8cb329bc9d852eb673d7c7d5ee4a093dbc124675c215d0b21035241adc140c4de74c154677d515090d03deb14210  nimbus_beacon_node
75d15828b200131058b3a49320443e6a16ee74da5bf2abefe15559b6f9fc2987a3f8ae093f5128b424dfcda5bdb86ecda38f2b473a2a3fb74de88ab3cc1c57c1  nimbus_validator_client
# Linux ARM64
7a40d145919b9863fde1fd28f7dddcd1499f1192e562995c0e99501f1b77993f5f956cdba67850d2009400f08e40142f26fb62ed03dcf0bf9bc549f6f704dbf5  nimbus_beacon_node
97cf35b07ec4afcc0d9f5c0aa2d42251185c34dcaff520a432e1d6d8405f0772fcdabd6d2d94906057ea98c7db40da48962b775cee0d3e20e567bacd9ee5decd  nimbus_validator_client
# Linux ARM
6701b75d0c52e56117a29e1cacf54c812e48eb11d91530cdc9430f121910833cc5ec97e785c4a40c8686b59f5ee28c1ce67d0edc63c2adf4e838123be3a2ff31  nimbus_beacon_node
7eb29c02a6f0126734b2f05fbbccfb6e194c09dc0b19deb766e7f404fd555407cb05726fd53feb7febaeb9ae4d446b0f288fdad53a18fad00638a2b441030054  nimbus_validator_client
# Windows AMD64
08dd5b4ccc959d26066345a091b0d909e7e7e33ed19391d021895038f7863686b1c790344dfec1e354c53d57b2906188ed598f9475d658f9506507ad488891cb  nimbus_beacon_node.exe
06741a211841dfdfaba8a69e99f0273dc602ec1bdbad9f0dd22b75141c3f28e01eaf0d3d54ad537e2a005d83f4d1230f8538b8e769c78e799d1aeb7c5ba060c8  nimbus_validator_client.exe
# macOS AMD64
e7a64e5a42242d50d4b368e532a8acad2cad6c57f84536c06685a86b32e0024fd06ca7c5945bd1610cef1055584366d02d23ce156aebfc62eb851829cdef1557  nimbus_beacon_node
69704ae96fa34e91e404f99095d0186c6012f3b50313ae3865243bd6d30b5fe3a859fa179392d72cc40bf95fa32b72ae05314b1e88d1b05b5e0d4ab41139778e  nimbus_validator_client
# macOS ARM64
497d79a06d55005eb9ba8eb7f95df0831e99eb7abc5696e002af47795d42a7cca4bd653233721384819af4e41f1c6a2b125f0aa0b593bcc316d5b06319f4b3a5  nimbus_beacon_node
44ceea66868281e8de5bbc7a1b4d6f116f2cab58672f7ca1ad787fdf262082c8fb2ebb1eb6b3b9bb5ebbaf1c206a1de56ca65cb781fdd939b7a21deedd1816ad  nimbus_validator_client

v23.9.0

12 Sep 00:52
568e1fb

Choose a tag to compare

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

24 Aug 10:44
d014d0a

Choose a tag to compare

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

19 Jul 16:28
60f0a2f

Choose a tag to compare

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