|
| 1 | +2023-02-20 v24.2.1 |
| 2 | +================== |
| 3 | + |
| 4 | +Nimbus `v24.2.1` is a `medium-urgency` release that includes full support for the upcoming Ethereum mainnet Deneb hard-fork that will be executed on 13th of March. The same support is also provided for Gnosis Chain where the hard-fork will be executed on 11th of March. Other stability and performance improvements make this release a compelling upgrade for all Nimbus users. |
| 5 | + |
| 6 | +### Improvements |
| 7 | + |
| 8 | +* The Deneb hard-fork has been scheduled for Mainnet and Gnosis Chain: |
| 9 | + https://github.com/status-im/nimbus-eth2/pull/5868 |
| 10 | + |
| 11 | +* The Nimbus validator client now uses the `/eth/v3/validator/blocks/{slot}` Beacon API endpoint when the configured beacon node supports it: |
| 12 | + https://github.com/status-im/nimbus-eth2/pull/5842 |
| 13 | + |
| 14 | +* The list of bootstrap nodes for Mainnet has been updated: |
| 15 | + https://github.com/status-im/nimbus-eth2/pull/5848 |
| 16 | + |
| 17 | +* Improved use of buffering reduces the risk of EL request timeouts: |
| 18 | + https://github.com/status-im/nimbus-eth2/pull/5893 |
| 19 | + |
| 20 | +### Fixes |
| 21 | + |
| 22 | +* A regression in the implementation of `eth_getLogs` was preventing Nimbus from syncing deposits correctly: |
| 23 | + https://github.com/status-im/nimbus-eth2/pull/5857 |
| 24 | + |
| 25 | +* A performance regression was causing high CPU load during the backfill process after checkpoint sync: |
| 26 | + https://github.com/status-im/nimbus-eth2/pull/5869 |
| 27 | + |
| 28 | +* Under certain conditions, the backfill process after checkpoint sync could fail to persist the starting checkpoint block: |
| 29 | + https://github.com/status-im/nimbus-eth2/pull/5863 |
| 30 | + |
| 31 | +* Under certain conditions, valid blocks with blobs that are not observed yet were permanently considered unviable for inclusion in the blockchain: |
| 32 | + https://github.com/status-im/nimbus-eth2/pull/5858 |
| 33 | + |
| 34 | + * The Nimbus validator client was not tracking DNS record changes when dynamic host names are used instead of IP addresses: |
| 35 | + https://github.com/status-im/nimbus-eth2/pull/5846 |
| 36 | + |
| 37 | + * The REST server was becoming unresponsive under certain rare conditions: |
| 38 | + https://github.com/status-im/nimbus-eth2/pull/5892 |
| 39 | + |
| 40 | + |
1 | 41 | 2023-02-02 v24.2.0 |
2 | 42 | ================== |
3 | 43 |
|
|
0 commit comments