Skip to content

v23.11.0

Compare
Choose a tag to compare
@github-actions github-actions released this 29 Nov 00:04
· 1013 commits to stable since this release
3a527d6

Notes

Nimbus v23.11.0 is a low-urgency upgrade bringing enhanced support for the Obol DVT middleware, further profit optimisations for the Nimbus validator client and a simplified and safe alternative to the trusted node sync.

Improvements

  • The new options external-beacon-api-url, trusted-block-root and trusted-state-root enable simple bootstrapping through the light client protocol and a non-trusted Beacon API provider:
    https://nimbus.guide/start-syncing.html#checkpoint-sync
    #5545

  • Improved scoring algorithms allow the Nimbus validator client to maximize block rewards when working with multiple beacon nodes:
    #5447

  • Nimbus now supports the /eth/v1/validator/beacon_committee_selections and /eth/v1/validator/sync_committee_selections Beacon API endpoints used by the Charon Obol middleware:
    #5375

  • Efficient bulk write operations to the slashing protection database bring significant performance improvements when operating very large number of validators on a single machine (e.g. more than 10K):
    #5604

  • Nimbus now disconnects peers who are behaving poorly with respect to the beacon chain request/response protocols and peers who are exceeding the GossipSub rate limits:
    #5579
    #5482

  • The Nimbus guide now features light and dark themes:
    #5564

  • Nimbus now honours the MIN_EPOCHS_FOR_BLOCK_REQUESTS network configuration parameter:
    #5590

Fixes

  • The REST API endpoint /eth/v1/node/peers_count was producing an incorrectly encoded numeric response:
    #5548

  • The REST API endpoint eth/v2/beacon/blocks was not handling the broadcast_validation parameter in accordance to the spec:
    #5531

  • The validator client slashing database was not pruned:
    #5551

  • Light clients following the event stream of light client updates delivered through the REST API or the P2P protocols were at risk of getting stuck due to missing notifications for certain key events:
    #5602
    ethereum/consensus-specs#3549

  • Regression in v23.10.0 was preventing the Nimbus validator client from registering its validators with the external builder when no validators have been attached to the associated beacon node, effectively disabling the usage of the builder:
    #5603

  • Nimbus was not retrying certain syncing requests after receiving an invalid response from a peer:
    #5615

  • A theoretical possibility where Nimbus may fail to start after a clean shutdown has been addressed:
    #5617

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
1f53f58373fa3540028ff17f2a46254f4d9236f844a01fb548359e3241bd9e9791abc3637b474b4e834a08c36d259b84032db01975944d5eb92aef4fbab14821  nimbus_beacon_node
efd1d5f0261b30cfb7e81c3e19ae5f2e2828a1af37a6f85c3151545a1725c68003d7331390ab4b24ac583cf62ccae448755b607c4717a7ec660bb95b4981d9a3  nimbus_validator_client
# Linux ARM64
27a2572216afead921a3c59ab1582ba3b0a06a53c753ac46a3aee4afe0122d01e2ddc4436b2518993369db06e3eff5fab88c1613dd79f1668b55be15b77802aa  nimbus_beacon_node
4affb3c9fb1c3fa83f99e6f806967db2a5fb1b474a4613ab4747d73fe6c0ed2e54391b6b8495cf438d50ee3b41ee46b824e4128bb4a9606e612a18bc0908998b  nimbus_validator_client
# Linux ARM
83b5a99eb3bc98ebfa0a6c0c609c837e3e582e03a1728487dcdcfdca937d3185c6b4ca71ca2eb835b47840ff87b965286a2266ec876f1e0cff66d71e9d87d059  nimbus_beacon_node
9a13849a1c72ca30adf54c87abaa603f1028b82f6eec5d0f4baca0e914ae422e86b42e8b9688f8031488032aa71d8819e0ccdea76d5f43bfd02d233dced8536a  nimbus_validator_client
# Windows AMD64
625ac9fabc65679f484c0988ceb664c51c5e3749ac84ad90426d8029ba49590585f377f0fdeba92ff7330a43335f9068c03c09f628a44053a6c42e202b06a699  nimbus_beacon_node.exe
78aa38439e6e6dbec7c68c33ce4e316bc06da9983409828ea61aa014d794bea968b482c954d38055f4ca36f12e8b5287d3afaa78b2c3650cb535ab1a127f30cb  nimbus_validator_client.exe
# macOS AMD64
9f6d4b66cc9ee5334c1675e748c0bc99a1fae55a15ed5ac4db3d6ef287bc2ebaccda85984f613991d35f7c86c87c857281ab80aace02abaf1e94828a2690085a  nimbus_beacon_node
df7b676f451cd9bb05c6f55c2a1eaf5f166fdc7592e1f2b6d54c81f4c0234b6788d936a872d38dd922bd6bdd54e5276bc6d032d83540e76fb93ba65fee765a21  nimbus_validator_client
# macOS ARM64
1a8efc60b0cdedf0f931ba15509393c268285cd8f1fe3f21f123f241c83fa79befd5bd7aaae99a43ed6a87f69a9a1a8bcef37f1b9ca2c488cbaa124725111fbd  nimbus_beacon_node
96dd77e672aac8d92d6339b89891260d35d18d5938ae97f1126eb3f8fc86e25fafb506caf1f900479a17c762f76ad71b57bafb49d848627d2244d16075b45ee5  nimbus_validator_client