v22.12.0
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_verificationquery 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
129in
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-eth2docker image no longer includes the
nimbus_validator_clientbinary 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
c6e211548d5932a8aa809142d760c33b383262ab3ed19ef8e7924e386f294d006db24b75ab98db8b2e6da82733775ed833882fbc752c2662ff43107bfcb1a80f build/nimbus_beacon_node
fdeffb77e7db46d19c221dcf789576ae35d1f02ce69229079891a04e3ccf3b552cfaf696e4471a033fa494470b8b80df1b479dd58c9687d73fba93af05f5eb3b build/nimbus_validator_client
# Linux ARM64
08948874428b42fa57218a77e0686431e07ad945c96b7845500fcc14963380c56e264aa298cc6f6d94f425f8d2353153b1c2fdffa9f9a78d99145daab389a608 build/nimbus_beacon_node
edc20ee3a13149ee63f6f63d44576a504d0511663c9208e5595ab72c052aa526eb7d884cce1872192852f75187c7eee00751309e8eb7ab530972f3d0a7fdd6f3 build/nimbus_validator_client
# Linux ARM
5e13e1a81fd4b34ac611834785c8c993b2808f897575022d524355450e20cee589176a3b0034725a84c1e8355502e80f581a04c34dc2263dc79c9760b262832b build/nimbus_beacon_node
6b3c6dfb22c4b96c918dbbf7e7443f0ff6d82fad885528325117743ea18167441d5f80d91d384e102d15077875f96c9ab36a654a56f623ca18e27cb14d42444f build/nimbus_validator_client
# macOS ARM64
dabc3ee91b34d717daa88c0cdce0e719c58c7ad50bf39c8ffa426eabf1a72b6f8ea1c459554af29006fccaa3292fe695daf8be4dcd698f0b81a21ce80924e2e3 build/nimbus_beacon_node
84eb8ff8ceac1dda8f0e52aa6fb3386c5203a55f35e128209b806f242f57813519a17a82475c29dbe4c4ed7c6ae0a64ebe1301e8b036949f7a495f1cf86e6ff9 build/nimbus_validator_client
# Windows AMD64
c56aab64244212a46a0eae61c2eff47618699ee75bad973a9f3f58575504124cb3a726ccb93ffa4012c29c4a872e4d707893ad3f658f0b35bd2612424f7c5d8a build/nimbus_beacon_node.exe
9dac6538ced29da554e08176d12a44cf9d817e0e3117859ddf861371eb338874608b1f64525fb0bc8b192e4ddeb8f42d0c63de1eabbbafdcf95410c6c8e7b4d7 build/nimbus_validator_client.exe