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/specREST 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