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
-
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
andprevious_epoch_participation
fields in the REST requests returningBeaconState
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