|
| 1 | +2022-12-21 v22.12.0 |
| 2 | +=================== |
| 3 | + |
| 4 | +Nimbus `v22.12.0` is a `medium-urgency` release which improves the doppelganger detection in the Nimbus validator 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. |
| 5 | + |
| 6 | +### Improvements |
| 7 | + |
| 8 | +* 60% more efficient block replaying speed brings faster REST responses and |
| 9 | + more resilience on the network in the face of heavy forking activity and |
| 10 | + non-finalization: |
| 11 | + |
| 12 | + https://github.com/status-im/nimbus-eth2/pull/4435 |
| 13 | + |
| 14 | +* Support for obtaining a deposit snapshot during trusted node sync from |
| 15 | + servers supporting the standardized `/eth/v1/beacon/deposit_snapshot` |
| 16 | + REST endpoint: |
| 17 | + |
| 18 | + https://github.com/status-im/nimbus-eth2/pull/4303 |
| 19 | + |
| 20 | +* Official docker images for the Nimbus validator client are now available: |
| 21 | + |
| 22 | + https://hub.docker.com/r/statusim/nimbus-validator-client |
| 23 | + https://github.com/status-im/nimbus-eth2/pull/4439 |
| 24 | + |
| 25 | +* The `skip_randao_verification` query parameter is now also supported in |
| 26 | + the `/eth/v1/validator/blinded_blocks/{slot}` API endpoint: |
| 27 | + |
| 28 | + https://github.com/status-im/nimbus-eth2/pull/4435 |
| 29 | + |
| 30 | +* The doppelganger detection in the Nimbus validator client is now based on |
| 31 | + the standardized `/eth/v1/validator/liveness/{epoch}` REST endpoint: |
| 32 | + |
| 33 | + https://github.com/status-im/nimbus-eth2/pull/4381 |
| 34 | + |
| 35 | +* The validator client will now use with the standard exit code `129` in |
| 36 | + case of detected doppelganger on the network: |
| 37 | + |
| 38 | + https://github.com/status-im/nimbus-eth2/pull/4398 |
| 39 | + |
| 40 | +### Fixes |
| 41 | + |
| 42 | +* A potential false-positive in the doppelganger detection logic: |
| 43 | + |
| 44 | + https://github.com/status-im/nimbus-eth2/pull/4398 |
| 45 | + |
| 46 | +* A potential hang in trusted node sync: |
| 47 | + |
| 48 | + https://github.com/status-im/nimbus-eth2/pull/4303 |
| 49 | + |
| 50 | +### Breaking changes: |
| 51 | + |
| 52 | +* The built-in support for the Ropsten testnet has been removed: |
| 53 | + |
| 54 | + https://github.com/status-im/nimbus-eth2/pull/4280 |
| 55 | + |
| 56 | + You can still connect to the Ropsten network by specifying its |
| 57 | + metadata directory on the command line through the `--network` |
| 58 | + parameter. |
| 59 | + |
| 60 | +* The `statusim/nimbus-eth2` docker image no longer includes the |
| 61 | + `nimbus_validator_client` binary and the shell scripts included |
| 62 | + in the release tarballs. Please use the new dedicated image for |
| 63 | + the Nimbus validator client. |
| 64 | + |
| 65 | + |
1 | 66 | 2022-12-12 v22.11.1 |
2 | 67 | =================== |
3 | 68 |
|
|
0 commit comments