Skip to content

Releases: status-im/nimbus-eth2

v22.6.0

20 Jun 21:05
@github-actions github-actions
v22.6.0
88532c6
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.6.0

Notes

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

Improvements

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

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

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

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

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

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

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

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

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

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

Fixes

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

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

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

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

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

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

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

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

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

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

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

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

Urgency guidelines

low-urgency: update at your own convenience, sometime within our normal update cycle of two weeks

medium-urgency: may contain an important stability fix, it is better to update sooner rather than later

high-urgency: update as soon as you can, this is a critical update required for Nimbus to function correctly

SHA512 checksums

# Linux AMD64
40b5954163ef1f028063b76bc1e7e1caf4ee80edab3e16078742a6bb9eb8dd28c06223211faac2c641b64e72ca524ecb4d5809038d350e42cb3151ea6f39244e  nimbus_beacon_node
# Linux ARM64
fa280275911a64d0504c91c519ec11414387a1d3c7b2dfe4edd1d4e22ea80afc440448f0c8dd25f243087e9c40b862563dcc61c820883a86af0db45b12936b27  nimbus_beacon_node
# Linux ARM
4cc71e010387fc260de9639de97c4bb17d037cb1ff23eef6d1fe0fabdda87f268d389b5c838f6add57915633a577465ebec665bb673b266e742bd14bd2622ec4  nimbus_beacon_node
# Windows AMD64
b30250e1a338042a7aa813c49e9bde6e06efdea57dbb23cfdd4262b07328fef31e2d5ca705f12e13f7a113906ebff673275fa508bc1e2812a4adaa6c47899859  nimbus_beacon_node.exe
# macOS AMD64
e2116916655f81870546aaadef5210836ede6a60ec8413b31c31b778f2524cc7ace27e5e7c049e9a7334eef3ceb51b6336c9602db3de5b6ce803f5ac58be405f  nimbus_beacon_node
# macOS ARM64
dc824c4372ee2d7e2743f74463418e45c27d2251f4a63a7c65a980b9a76c4f742f1c90fae285aa083b6ab3bf35b4c3f9023183fcb781883b15a27244eea7ed10  nimbus_beacon_node
Loading

v22.5.2

30 May 19:26
@github-actions github-actions
v22.5.2
f124f22
This commit was signed with the committer’s verified signature.
tersec
GPG key ID: 3D7A11A0156519DC
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.5.2

Notes

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

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

Fixes:

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

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

Improvements (v22.5.1):

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

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

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

Fixes (v22.5.1):

  • Restore compatibility with certain Web3 endpoints
    #3645

Fixes (v22.5.0):

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

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

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

Improvements (v22.5.0):

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

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

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

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

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

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

  • Improved compatibility with all versions of Web3Signer
    #3640

Urgency guidelines

low-urgency: update at your own convenience, sometime within our normal update cycle of two weeks

medium-urgency: may contain an important stability fix, it is better to update sooner rather than later

high-urgency: update as soon as you can, this is a critical update required for Nimbus to function correctly

SHA512 checksums

# Linux AMD64
32229f537af416abd4c7ad9afa78029a587028155751d889bfed8323948f16b1c90d358087d977decd0fad719a7e1bf69377ae7c7521b1ea00d7ba78a4aef80a  nimbus_beacon_node
# Linux ARM64
d61f657551d5f91d06633f22fa65594ed0c4b78322e8b9abd118a5fca0730ffffdd6c5c25fc56556a703d2950e945cf0748dc8d411add23ab3f08c6deaaba42f  nimbus_beacon_node
# Linux ARM
1bc074644fb4cc0aa4b41eaf10c11d4a5a8fd8976b20fa05b2d1632715573f8407c6fe35a08ac4c891ea8c69568da9b6669054d3379d4e7955e7a0911dae1db3  nimbus_beacon_node
# Windows AMD64
64f4a4bbe7d6de00af58dec6c9d2abef25a6e7ff2acf698939ea3e034d404dc2e562e4910aef7d4eb64aecf546cf3b7f2d851a0c310d8a52b68da4c639c1ebe7  nimbus_beacon_node.exe
# macOS AMD64
8dbf0c1904a4ac1790dbf4a638d2d1d7bb19e637801b3c56955d03b51ff11ba35748f6209eb3873920f0db497a76841c1cb27b2e8d6de44a9d0e2c826af92de8  nimbus_beacon_node
# macOS ARM64
45191d3f6709c3f4ec03cf9b3dd6e2a7a5b0d2ed24477a14a6a93bc6acba357dbc26b3d041e54e2907663a023ff6eceb66286894b492ce226fd99a1d47993d7e  nimbus_beacon_node
Loading

v22.5.1

21 May 12:04
@github-actions github-actions
v22.5.1
f7eff8f
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.5.1

Notes

Nimbus v22.5.1 is a low-urgency maintenance release addressing a Web3 compatibility regression and introducing Ropsten testnet support.

Improvements:

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

  • Support for the Ropsten testnet, intended for merge testing
    #3648

Fixes:

  • Restore compatibility with certain Web3 endpoints
    #3645

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

Improvements (v22.5.0):

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

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

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

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

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

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

  • Improved compatibility with all versions of Web3Signer
    #3640

Fixes (v22.5.0):

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

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

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

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included README.md file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
7a80e1b3c24bd78dcdf7d156a7d13d180a96c31a7df2602112bb609d3e74ac125b76d6307377bd7964194164f64bb1ec6132266972467c825396afdc90c909b7  nimbus_beacon_node
# Linux ARM64
ab3761ae4819e41db0da1de0ed5d360c1f37cd401ac4bf8881a7ad5e1d2d11fa7d564a4a83ebce909e52c137b1382ec46a72f21d520810e8b299aa827439fa55  nimbus_beacon_node
# Linux ARM
575c36ef732c9f7b5623328f60577d809ae6c2e7241019d1181312c9703632618d3747fd71b310939378b113d351a3e4311fa65b5ddfce7753cd474241894567  nimbus_beacon_node
# Windows AMD64
9e6fda690648fd83c36db160c16e6a6f4d05f675a88e9007e67dac86e6ab6fb6316b4d3695c0ff549ba8f1cea4f1cfe517e7cb1cf548897dd2425581038c38d5  nimbus_beacon_node.exe
# macOS AMD64
c01081ded0250d5497c15d0c734f67f962f6cc5ce77157305ea3f734a7e6891b41352525b26102e0b2b68613027f202497ed5c5296002075337d057385a81568  nimbus_beacon_node
# macOS ARM64
18b7fcca1f3f0824ffae5d6db92b3d9e160efca3c1eb75f5da42ed22a726935ca3d525e36d7739d9072e5fe6409c03c477980363d9026ee8ebe87103b9545c57  nimbus_beacon_node
Loading

v22.5.0

19 May 11:13
@github-actions github-actions
v22.5.0
a359dbe
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.5.0

Notes

N.B. If you are using Infura as your web3 provider you should skip this upgrade

Nimbus v22.5.0 is a low-urgency maintenance release. It implements the proposer boosting fork-choice policy and is compliant with the latest Bellatrix specifications. It also provides an early preview of our built-in support for BLS threshold signatures (via regular Web3Signer instances): this marks the first step of our long-term secret-shared validators roadmap which enables node operators / staking pools to deploy Nimbus in secure high availability setups (~100% uptime).

Improvements:

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

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

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

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

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

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

  • Improved compatibility with all versions of Web3Signer
    #3640

Fixes:

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

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

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

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included README.md file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
35e815d006962115eba3ce255244b0ecd273fd6ca4935372368286d80946159bd9b6f3dc4f5c4c8c0b3a76c60eb6f258e392b4c88baeba5f900ae38883a34807  nimbus_beacon_node
# Linux ARM64
292f0ba49e5844fe8e0c0b44a774b2d861acdc9671a8b8b77d505c5ca24b97f55d43b6a8e9495b6302514b0ca45213d7d950921d3bf7cf24d011d7d206c4b33c  nimbus_beacon_node
# Linux ARM
3d5a124d016868a211215bddb3e1016229e7c391e66a6df931409b1b50d202e1753437180d16e0d1068683711b613f43e42b887caca9367f22da7d9efb16658d  nimbus_beacon_node
# Windows AMD64
96c283ebd5bc29f019621a4acfac02d3e3fc2752c7e7cd206858c4338c5ddbe46bdf8a4148842160a172383183ff31d0089bee257ba615fa217219fcb0c436b6  nimbus_beacon_node.exe
# macOS AMD64
92f82ba85aa242af8301fad4b2d9511ed161113b58ab916f585c08e884b5144f990b6e9c894496e823b56a01ec805fd0f775b2ece174e7bfd5a234247929ea8e  nimbus_beacon_node
# macOS ARM64
7737d0ec1549a7772107b837796707088bb52f1e69c450889d7ccaa64dd004213b7f8b0edc1348ec5e284a664c5a9a7dcfd430450a2073cfd4fd240c2bae25ba  nimbus_beacon_node
Loading

v22.4.0

12 Apr 08:53
@github-actions github-actions
v22.4.0
039bece
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.4.0

Notes

Nimbus v22.4.0 is a low-urgency upgrade which contains numerous fixes, optimisations, and a better user experience around trusted node sync. It lays the foundations for upcoming the merge hard-fork which will be fully supported in our next release (v22.5.0).

Improved:

  • All CPU cores are now used by default: this was previously enabled by passing --num-threads:0 on the command-line
    #3493

  • 250 MB reduction in memory usage: thanks to more efficient data structures for the finalized portion of the chain history
    #3513

  • Higher performance historic queries (using REST API) after trusted node sync: Nimbus now re-indexes the backfilled chain of blocks
    #3452

  • Broadcasted attestations are more likely to be included in blocks by other nodes: thanks to a tweak to the attestation sending time
    #3518

  • The REST API now only returns current and relevant information in response to VC queries: in other words, information from the recent non-finalized portion of the chain history
    #3538

  • Better and more consistent gossip mesh health: the --max-peers option now works as a target that can be exceeded by the client temporarily in order to maintain good gossip mesh health; the newly introduced --hard-max-peers option now acts as the hard limit that should not be exceeded (default set to max-peers * 1.5)
    #3346

  • An ERA files developer preview: ERA files are an ultra-efficient long-term storage format for finalized chain history
    https://github.com/status-im/nimbus-eth2/blob/unstable/docs/e2store.md

Fixed:

  • Nimbus no longer crashes when a HTTP URL is specified as a --web3-url end-point:
    #3582

  • The REST end-point /eth/v1/beacon/headers is now able to return backfilled blocks:
    #3472

  • The Nimbus status bar has been disabled on Windows in order to avoid sporadic hangs in certain terminal emulators:
    #3484

  • A large start-up delay after backfilling:
    #3516

  • A rare problem which prevented the node from starting successfully after a trusted node sync:
    #3517

  • Confusing error messages when Nimbus lacks the necessary file system permissions to create its database:
    #3536

Removed:

  • The support for the Pyrmont testnet has been removed in order to reduce the Nimbus binary size:
    #3568

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
d5d4a8e7cf67b139b1472f45461cbc701bdfcae8735f47dd9927dd30d7d64e30ddcda0ac8ca30fb8cea25ba53df46fd9d2a52113b53f581aa76a7ede7dac34d4  nimbus_beacon_node
# Linux ARM64
836a68399674c5d2f42f26b2377bb5f259563c1e8eb15caadd9f068cc0ec8d2890e2339f00ff2e1004508b1e5992853005c5965f7089d6d92a7c6fb4edeaccb1  nimbus_beacon_node
# Linux ARM
6a9ca00473aeb9055ce3027279d57d09b6c032ec9b0300f0abd6052857fc744cdd759b2b6c136c6aa491aa532f009c79d128ac1257ed3ad3f97cfa477a20e057  nimbus_beacon_node
# Windows AMD64
2d0a9c306447869cd852566969da80b1dec9b337f55caea7f7942a0f5bdb2fbe19b3ceec3cc092b5f831559082030e5e8f8547546380a92fdf1d104037e48ad9  nimbus_beacon_node.exe
# macOS AMD64
7ca1b99931c4528f08c9f92919fa096f49c883b19154d77472789045720b75c718d1d5e598b3582085cf290fff9823152158db8400ec33ad3d26c60ebaf4f7f1  nimbus_beacon_node
# macOS ARM64
56a07350470379ced7eda0b6dcabb821f5112b419325042809b76d776d57a9cf8a81ce3bd4506d6541a52c2e2806ff2ccde41e95ea5d5606bdc6cf59cdf5d80b  nimbus_beacon_node
Loading

v22.3.0

10 Mar 17:15
@github-actions github-actions
v22.3.0
13b264d
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v22.3.0

Notes

Nimbus v22.3.0 is a low-urgency upgrade that marks the beginning of a more predictable release cadence for Nimbus. Going forward, we'll be publishing a new release each month, following a feature freeze period with intensified testing and monitoring of the introduced code changes on our dispersed fleet of mainnet validators.

Please note that the new versioning scheme is tied to the calendar. The number 22 indicates the year of the release (2022), while 3 is the month (March). The last digit is the patch number of the release and it will have a non-zero value only when we ship a hotfix during the month.

Improvements:

  • Nimbus can now run as a service on Windows: use the --run-as-service flag
    #3441

  • All command-line options can now be provided in a configuration file: use the --config-file flag
    #3442
    https://nimbus.guide/options.html

  • Lower CPU and bandwidth usage, thanks to better handling of already-seen attestation aggregates
    #3439

  • Reduced memory usage for nodes bootstrapped with trusted node sync
    #3429

We've fixed:

  • Reduced performance on Windows due to the use of a less efficient method for collecting stack traces
    #3466

  • Non-spec-compliant URLs in the Keymanager APIs for handling remote keystores
    4c01b77

  • Extremely slow slashing DB import for validators with long validation history: the import should be nearly instant now
    #3393

  • Validator index-out-of-bounds crash that was triggered upon certain requests to the /eth/v1/beacon/states/{state_id}/validators/{validator_id} API
    #3463

  • An off-by-one logic error preventing sync committee messages to be published in the first slot of each sync committee period
    542e645

Deprecated features:

  • The JSON-RPC service (--rpc flag) option is now deprecated. It's scheduled for removal in version v22.6 (i.e. June of this year). If you are currently relying on the JSON-RPC API, please consider switching to the official REST API.

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
a8840d114daa9ce6b7a6d988309e44158f20f86edd3930fd6fb45beed9d49f63fd20974cd419cc83b374e4d204376fc1bd51cdab268bef7474ef7752584a24ed  nimbus_beacon_node
# Linux ARM64
3223ec7a42ec6775449b5eaaa0aa42a0d2eb1470151613f699e5e5d3a11164fec579343196b67684b6d489bcf6495bea8457bac3e411e62347a6dfe487260600  nimbus_beacon_node
# Linux ARM
9d399ef30e2a2bb9fc6b5e3f9f3667234b1be1dd8d2ba6b40d57ad7288d8e824c8da260ff65af39edb7815c0c820b4c669b205b012bb940ae9514e23b606b85c  nimbus_beacon_node
# Windows AMD64
4e91f72df61f5931e0254bd6b69f73ff5e68d89dbfb3556ade765360c96a4da5eef1dfba59ae0abe24fec864bc99e8ddbde2b4429bc8aac45cc3447a2b79c11f  nimbus_beacon_node
# macOS AMD64
0d97c9aa7dcbb46e0bdfef82d6e415ea7814180ec658573d067a694379f73a8535839728c9d65f2d7123ff600faa73b4ad9128a49a3a22fcdd5090e211ed246d  nimbus_beacon_node
# macOS ARM64
d48562eeb48973589598b685212f16ea66d96528684020bf0726ce33735cc184e50e548914ba26703f70d2defafe4083dd6735a4e494336f8b3d1a5ff8963952  nimbus_beacon_node
Loading

v1.7.0

16 Feb 11:24
@github-actions github-actions
v1.7.0
8e03300
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.7.0

Notes

Nimbus v1.7.0 is a low-urgency feature-packed upgrade, which brings support for trusted node sync (also known as checkpoint sync) and HTTPS web3 providers.

Of particular note: the Keymanager API now supports remote keystores (a.k.a web3signer keystores).

Breaking changes

  • Nimbus will no longer rewrite HTTP(S) web3 URLs to their respective WebSocket analogues. Please review your setup to ensure you are using the right web3 protocol for your endpoint.

  • The peer scoring has been further tuned. As such the --max-peers should not be set below 70. Note that Lowering max-peers does not significantly improve bandwidth usage, but does increase the risk of missed attestations.

Improvements:

  • Trusted node sync: #3326

  • Full support for HTTP and HTTPS web3 URLs: #3354

    • Nimbus now treats the first --web3-url as a primary and preferred web3 provider. Any extra URLs are treated as fallback providers (to be used only when the primary is offline). As soon as the primary is usable again, Nimbus will switch back to it.

  • The Keymanager API now supports management of remote keystores (also known as web3signer keystores): #3360

  • The typical memory usage of Nimbus on mainnet is now below 1GB (thanks to 128MB of savings): #3293

  • Faster beacon node startup-times: #3320

  • The REST API is now compatible with CORS-enabled clients (e.g. browsers): #3378

    • Use the --rest-allow-origin and/or --keymanager-allow-origin parameters to specify the allowed origin.

  • A new --rest-url parameter for the deposits exit command: #3344, #3318

    • You can now issue exits using any beacon node which provides the official REST API. The Nimbus-specific JSON-RPC API will be deprecated in our next release, with a view to completely phasing it out over the next few months.

  • The REST API will now return JSON data by default which simplifies testing the API with curl.

    • The notable exception here is when the client requests SSZ data by supplying an Accept: application/octet-stream header.

  • Fairer request capping strategy for block sync requests and reduced CPU usage when serving them: #3358

  • More accurate Nim GC memory usage metrics.

  • BLST upgrade (latest version): #3364

  • The web3 test command now provides more data about the selected provided: #3354

We've fixed:

  • Unnecessary CPU and bandwidth usage: #3308
    • The result of staying subscribed to sync committee topics even when the client is not acting as a validator within that committee.
  • Excessive logging on beacon nodes with large numbers of validators (in particular, those with --validator-monitor-totals enabled): #3332
  • Deviations from the spec in the REST API; this led to sub-optimal performance when Nimbus was paired with Vouch.
  • Naming inconsistencies in the "totals" metrics (this was produced by the validator monitor).
  • Non-compliant implementation of the /eth/v1/node/health API (we were not producing HTTP status codes as mandated by the spec).
  • Unnecessary restarts of the Eth1 syncing progress when the web3 provider connection was lost during sync: #3354

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
95f1695dd7404ee2413b71e2f3f00ba7faf3c3b3e07a9ca538ae5ab9fe99f6663e881e6a041bd6a7cacaf859f2ae096af69d54d24058ae2a6dad6979af393e0b  nimbus_beacon_node
# Linux ARM64
74637a15356df71c8a29df0046b3458d24d74b0c5b5f595d34b6770bb2be1d8fd852bac3b9a4161db7f5c4dd8396ce96c3cc65dd4f9564856fa7162a2c96712d  nimbus_beacon_node
# Linux ARM
925be9b11e0cbc428a75fe8c729970a61d902a2a9f43f909fba4ba96eb0030c88a489038f2da0d8584f0a36046e95a6deed7f09c707ad966e048a916a4c282bf  nimbus_beacon_node
# Windows AMD64
848ea73a62b51ee5997e475d8eb89908e3057ebd70af3b837dd9d3b6ef520c3baf184535f400e45c5dc7ac627338665cccf4e69d9bf4860d285117168d2241c3  nimbus_beacon_node
# macOS AMD64
66872afb28f415eb3e5cab7e863b0d05d23274f1adec911530c1a63c656ff6930311fac00aa4b2227fb60e45606c81c5ab93403f1bc7029581197c5d078ec1e4  nimbus_beacon_node
# macOS ARM64
75ec522bd8800d289139f000bc19c70ff78fcce42c0579f7ee27654645190232ebd6ffcc0bf86f1a22ccc9098337488c32ddf50d816b35bf1770fd734f1435d9  nimbus_beacon_node
Loading

v1.6.0

14 Jan 14:17
@github-actions github-actions
v1.6.0
bef13b6
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.6.0

Notes

Nimbus v1.6.0 is a low-urgency performance optimisation release with improved peer management.

v1.6.0 adds support for the Keymanager API (currently in BETA):
https://nimbus.guide/keymanager-api.html

As well as a comprehensive set of metrics for validator performance monitoring:
https://nimbus.guide/validator-monitor.html

Improvements:

  • Tuned peer management: reduces the likelihood of missed attestations
    • If you've seen frequent "No peers for topic" in your logs, this release will help
  • Improved buffer management in the networking layer: reduces both CPU and memory usage.
  • Further optimised batch verification of gossip messages: provides a 2-fold improvement in throughput.
  • Comprehensive set of metrics for live validator performance monitoring in Grafana and support for producing detailed historic reward analysis in ncli_db (note that ncli_db is available only when compiling from source at the moment).
  • Support for the new Keymanager API: add, remove, and migrate validators on the fly (BETA).
  • Blazingly fast historical traversals in the REST API for beacon chain data mining: state caching brings up to a 10x speed-up in some common usage patterns (e.g. obtaining historic data slot by slot or epoch by epoch).
  • 3x speed-up in snappy compression and decompression.
  • Support for obtaining JSON payloads from the REST API.

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
3f1ec9512a4cf6852d7d26d3a997ebc6304c797a412605eaf908f4ba43f5c3acda4019e92ef4f18e5258e5c4178e2f64c18cbf4877b330719cff46ca29aa54fc  nimbus_beacon_node
# Linux ARM64
02b19c3d69b1c4073a3b3e2e9f935abd5254505f8a1735e65ca3208385c8b22aa6a9600c212818b33a2f0900ad3f0ba3018c1c9155ccad3f4b4599c2b1d30d99  nimbus_beacon_node
# Linux ARM
1e9bf23e985330bb23c5c7337502ad9cb3f84b3561488a4e764af30a3a40f54bc96c61367304bdded2ce8b356af7430e01627e86a36250aa2d223d59ed8a5b7e  nimbus_beacon_node
# Windows AMD64
61afc2a66626f0f0c1f7edafab6dafa410a95619c55e7c3d8c0b5daecff8fe5809350e9f4c4336f0f847736fce82a53f1f0fcc8783c8525aed1b1c9255ee379d  nimbus_beacon_node
# macOS AMD64
4866bdc1a00b32eeeab685f51a5ae02a5424a99d155966d520a13cc021a5b65c000e33dcdafc912b3516cac3972ed317ddc2f21505a2d26f84ae00d39bee5d82  nimbus_beacon_node
# macOS ARM64
4bdfeb94e7c0c65035df8ce824618093c12d05a7bdc731567066fcba5def394289fab483404df28285bced402dadeabfba458b78e3af9a116a1cf76de754284d  nimbus_beacon_node
Loading

v1.5.5

06 Dec 17:35
@github-actions github-actions
v1.5.5
f0f9735
This commit was signed with the committer’s verified signature.
zah
GPG key ID: C8936F8A3073D609
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.5.5

Notes

Nimbus v1.5.5 is a medium-urgency bugfix release which contains a number of significant optimisations; of particular note is a 6x speed-up in epoch processing and 2x speed up in Altair block processing.

In addition, v1.5.5 adds support for the web3signer protocol (currently in BETA). This allows staking pools and other providers with an advanced key handling strategy to use Nimbus.

We've fixed:

  • The potential for missed block proposals when a third-party validator client (with at least one imported validator) was used with a Nimbus beacon node (with no imported validators): this happened because the --web3-url parameter was mistakenly ignored when running without an in-beacon-node validator
  • A rare condition in which the REST service became unavailable
  • Inappropriate error messages produced by the REST API: when a validator client published the same attestations or sync committee messages through multiple beacon nodes.

Improvements:

  • 6x speed-up in epoch processing: #3089
  • 2x speed up in Altair block processing: #3115
  • A 12% (minimum) reduction in the outgoing GossipSub traffic: #3112
  • Across the board performance improvements in the REST API: #3092
  • The REST API can now report sync committee information for the next sync period: #3133
  • Added support for the web3signer protocol (beta release): #3077

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
69f28f514ea8694d954b845ff71fddd85c533b988dd67eda44ad39e8005e3ee87f50f8ef3f8ad9df1ba4c5fcff6ff59d34016b30f84f8c71e88da5c2509f4654  nimbus_beacon_node
# Linux ARM64
80d3d4f6531625751f0e0c0d0ad55d923533316df4b72e4764d1b0ee68f71af64e219bc3faa4a793055caf067b52723171d3cfd6e6088ae054a5dc57ae3d137e  nimbus_beacon_node
# Linux ARM
0c6129a909180e73640f408396d3601057c9b3f5391eca4dc082f7fed687a66ef623939b5d2ff249cbdf39d5c6c3ba2682cb43b43665a62a3a0991075e9bba07  nimbus_beacon_node
# Windows AMD64
0fc234f95cdb0e72baeb1d550333eadb4b87e421e25c38e422709d8ca7a8ca2ca49e67567d93ea2c9803dbbad8ed81fd52df63ce28a946781f798bec95c4b3a5  nimbus_beacon_node
# macOS AMD64
8893dead29b03c4c5f5254c85daf3d3cc5a19d9c77177df73c2bcd06f5c3e307ce73288b6eaa14fe9647369c3a80ddb30ba29d943ce5107e4f4bb15c93fe77c0  nimbus_beacon_node
# macOS ARM64
b51bd5aa2d783661c76230a6cc1830548caee86b9439300d52ecb9d14ecb4ad78f353357c9560e7dd6354fd339f3cc98fe92e03a84c485520ed8a9764605c149  nimbus_beacon_node
Loading

v1.5.4

10 Nov 14:06
@github-actions github-actions
v1.5.4
This tag was signed with the committer’s verified signature.
stefantalpalaru Ștefan Talpalaru
GPG key ID: CBF7934204F1B6F9
Verified
Learn about vigilant mode.
b1218c6
This commit was signed with the committer’s verified signature.
stefantalpalaru Ștefan Talpalaru
GPG key ID: CBF7934204F1B6F9
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.5.4

Nimbus v1.5.4 is a medium-urgency hotfix release. It addresses an important issue which, in rare cases, can lead to the loss of attestations and sync committee messages. This can, in turn, lead to a reduction in rewards.

Please upgrade at your earliest convenience.

N.B there has not been a 1.5.3 release. We have skipped straight to 1.5.4 (which contains a last minute fix to the build system).

We've fixed:

  • A rare issue during the construction of sync committee contributions: invalid BLS aggregate signatures were being produced under certain conditions; this had the potential to negatively affect the peer score of the node, and impact its ability to deliver gossip messages

  • A non-spec-compliant implementation of the /eth/v1/validator/duties/sync/{epoch} REST API

  • A crash in the /eth/v2/debug/beacon/states REST API call on systems with limited stack space

  • A regression in Libp2p (incoming clients had no shortAgent, breaking the metrics)

Improvements:

  • A nice little performance improvement for block verification and replay

  • Improved error messages in the REST API

  • The /eth/v1/config/spec REST API now returns more information regarding spec config parameters

  • More flexible logging options: the log format can now be specified at run-time; see https://nimbus.guide/logging.html for more

    • Please note that the --log-file option is now deprecated and may be removed in a future release (if you wish to log to a file, we recommend redirecting the standard output)

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
f189f642f40848d2b25bef28a98547e8b9dd2aec7cdaf7e2a38b04c2a8aa187b0b0769e709ce0be5ee21f987f3c1534351e6b7640671305027c3c64a7d0aa68a  nimbus_beacon_node
# Linux ARM64
bf1b6370d21b28201f64e0e04d8890e01d27a12366c470096b94e946b4885e6a913d3c246fed87eddbc3f5b98c5b602345ad9a421d2410f3cecad7cc791d1341  nimbus_beacon_node
# Linux ARM
1c12da2e23b24a690dab7fc86c1d9b0e5db72e87f6fb25d34f2630f7e5bf9bd974c8f110a6d6166373d32ba12609eb97646054cf9e19e499db3566e446d17a0d  nimbus_beacon_node
# Windows AMD64
73772ea4b34875e0720fc5ba62e517eb8989cefa824f5095b157dfd5757187fe7e19a1f591c367072f29e183a8d5381e59f79d9e505c5800b119c75c7991698c  nimbus_beacon_node
# macOS AMD64
2531ea8b3d6344e15668926c9da13507860e195810daa7a22bdddb964e610ae980d1bf35bd60431c060de28fe1e36aad98dd63743447f291ff11024c0b28be29  nimbus_beacon_node
# macOS ARM64
138e14199000cead14e857d00651d064e42e83c5d19da968236f7a4310f2565b39683ebc2b769d88465bcf68b7ece122839033ee68da94e6ffeaa8a528d51f94  nimbus_beacon_node
Loading