Notes
Nimbus v22.12.0
is a medium-urgency
release which improves the doppelganger detection in the Nimbus validator client through the use of standardized APIs that are compatible with all third-party beacon nodes. Furthermore, it addresses several inconsistencies in the behavior between the stand-alone beacon node and the validator client. This release also allows users of trusted node sync to skip downloading the entire history of validator deposits by syncing against a server that supports the standardized /eth/v1/beacon/deposit_snapshot
REST endpoint.
Improvements
-
60% more efficient block replaying speed brings faster REST responses and
more resilience on the network in the face of heavy forking activity and
non-finalization: -
Support for obtaining a deposit snapshot during trusted node sync from
servers supporting the standardized/eth/v1/beacon/deposit_snapshot
REST endpoint:https://nimbus.guide/trusted-node-sync.html#skip-syncing-the-history-of-deposits
#4303 -
Official docker images for the Nimbus validator client are now available:
https://hub.docker.com/r/statusim/nimbus-validator-client
#4439 -
The
skip_randao_verification
query parameter is now also supported in
the/eth/v1/validator/blinded_blocks/{slot}
API endpoint: -
The doppelganger detection in the Nimbus validator client is now based on
the standardized/eth/v1/validator/liveness/{epoch}
REST endpoint: -
The validator client will now use with the standard exit code
129
in
case of detected doppelganger on the network:
Fixes
-
A potential false-positive in the doppelganger detection logic:
-
A potential hang in trusted node sync:
Breaking changes:
-
The built-in support for the Ropsten testnet has been removed:
You can still connect to the Ropsten network by specifying its
metadata directory on the command line through the--network
parameter. -
The
statusim/nimbus-eth2
docker image no longer includes the
nimbus_validator_client
binary and the shell scripts included
in the release tarballs. Please use the new dedicated image for
the Nimbus validator client.
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
9e1bb1c14138ccee7569317adbbb325e298d04037b71fd76303fd5e8c37fdadc313ec31c3f4b92733aa5b4db022114f3056224e3fece2f51031b92ea9e23c14e nimbus_beacon_node
570455dbeded82bbfe498debfd01741d12fdf675b2821c1cd8044d8a8b921b5cdfcce0db97e9eff926dda4d2c1310d98b82175bebc80ca545d9aa489ff7736b5 nimbus_validator_client
# Linux ARM64
01ff1cfac6e4cdf9e5eb291e71cc6327f4d7708f15ff6d640fe900a6860166b64818557220c39ac17b68698dd135559a3f841265050e88a2a93790cfc44e5921 nimbus_beacon_node
829e8b2e518f0c48d0662e6977ac6cf0c8042d6ba23c69d2c8ca5796fdbc7a2073708be36c8787f128f4ffaacb6a531eec8efe3a4c72b00801a1f845e4aa54f9 nimbus_validator_client
# Linux ARM
85c5e1533c3aa45499d7f5072a7736ea6b8736f9f0ca6eb1067c8f5c984b4e96def556343cf4a84122999c2defb26f5b6d478ad3f6b1ce2569d9a7a43b1eb91d nimbus_beacon_node
f3bc28ac26d05bc75c758844d476e1b3cf92b362b7898297b3aba0de436f64d22ce334a299858688e99d5a473b4e26605911ce3c4c5ae5cc61d7088556eb25ea nimbus_validator_client
# Windows AMD64
3f0a7a2a4f80bf1764f165cd1f8b4aca2a3a45808b018cfdd93815082f8f8fdc6c89e903eac79a2bce3f4b1f9f15ba09f2ecfc8860c6b7eb3bffd77cf16d0bdd nimbus_beacon_node.exe
bf8b75618178deb59f4e3ad53cae49bb8ab365442a92f34dc6fa1e4ab2d38b359b98e51af60fa72e7f1a3498731ea3cfbdb2e399bdae15958eb8af8ace6bc1ca nimbus_validator_client.exe
# macOS ARM64
e0e47366330515fd59722eb851c8f7f6c4354dac4e25f8c354bff9fa86efd8948c52901ae9d99373ba4ed366735cf5a8776744fa128d5548c4fd1db4778f69b3 nimbus_beacon_node
bd0b8cd9346b561ce1d8e1e91f29517d873c2eec2fb8355e46b3eaafde1d388507c78d3c682a07175d8efb3f84ec63c40dcc166416d8497e022ce0e7083e5a05 nimbus_validator_client