v1.5.0

Nimbus v1.5.0 is a medium-urgency but mandatory upgrade which adds support for the upcoming beacon chain Altair hard-fork.

Please upgrade at your earliest convenience - before the 27th of October.

N.B You must upgrade before October 27th in order to follow the mainnet beacon chain. Failure to do so will result in downtime penalties.

This is the first hard fork for the beacon chain, and while a significant amount of testing has been conducted in the run up to this release, we recommend users regularly monitor our announcement channels (discord and/or the newsletter) for potential updates.

To celebrate the feature complete release candidate of our REST API, we've opened up the ports on some of our fleet nodes - don't do this at home ;)

In order to interact with these, you should point your apps and tools to:

• http://unstable.mainnet.beacon-api.nimbus.team/ - mainnet data, the latest unstable branch
• http://unstable.prater.beacon-api.nimbus.team/ - prater testnet data, the latest unstable branch

Note that right now these are very much unstable testing instances. They may be unresponsive at times - so please do not rely on them for validation. We may also disable them at any time.

---

Notable changes

• Support for the Altair hard fork and the latest Ethereum consensus spec (v1.1.1)

• Our REST API is now feature complete, supporting the full Beacon API specification. This API should not be exposed to the public Internet as it includes multiple endpoints which could open your node to denial-of-service (DoS) attacks.

  • Known limitations: To use the REST API with a validator client, you need to enable the --subscribe-all-subnets option. This requirement will be removed in future versions.

• A new experimental --num-threads=X option allows Nimbus to take advantage of multiple CPU cores when verifying attestations. Set it to 1 to use one worker thread, 2 for two worker threads, etc. The default value is set to 1 in this release, but future versions will set it to 0 (this tells the client to use as many worker threads as there are CPU cores available). N.B .enabling anything other than 1 is considered experimental at this stage.

• Improved peer discovery logic that ensures good connectivity to all gossip subnets.

• A new version metric that makes it easy to keep track of client upgrades within Grafana dashboards.

• New metrics libp2p_peers_identity, libp2p_peers_traffic_read_total, libp2p_peers_traffic_write_total, subdivided through Prometheus labels by the client type of the peer (i.e. nimbus, prysm, teku, lodestar or lighthouse).

• BLST has been upgraded to the latest version (v0.3.5).

• The --network option now accepts a directory with custom network metadata in the format of the eth2-testnets repository. The SECONDS_PER_SLOT configuration value remains the only setting that must be supplied at compile-time through the -d:SECONDS_PER_SLOT=X nim compilation flag.

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

Binaries

Scroll to the bottom of this release and click on the tar.gz which corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

A note on peer count

If you don't allow for incoming connections, your peer count will be lower due to a new peer selection strategy. If you do have incoming connections set up, it's good practice to verify that all is working as expected - See the port-forwarding section of our guide for how to do this (metrics will tell you if you're actually getting connections).

To clarify, previously we would connect to spare peers for good measure - now, we delay setting up the connections until we need them, and end them if we don't.

SHA512 checksums

# Linux AMD64
d2871373e46689cef8b01a400110b6be4d179f415a1d218d384a252bc057b3dbd3ca842807f6292490df8800e3bcd8111206988b862bef218a46e5baeb276d5e  nimbus_beacon_node
# Linux ARM64
5f8135a727f7714613b3720e2fd4440edc85fa0080a6bef808a75009fa9bf59e3b060a119d7afabf11c0e27df87689a928f4d759dd5f094772051d52291276cc  nimbus_beacon_node
# Linux ARM
0cd4c3a45138bf22bee42b9cbbb78149d5ed1af425d3fa1aea02bc16ea01324f780a34f97b8ac0b82d31a5295785c735c3a2087fb2c4028f3e046adef4259d15  nimbus_beacon_node
# Windows AMD64
6a5732a9554edcdc8007a7b8696d20bb9d5fb4af9fcee5e4d8a07b627999ad03b7aa39ed9d346dcb1f7cb7b779da6d7e9bee6be3431873eab0efcf1599edcd24  nimbus_beacon_node
# macOS AMD64
956e14249580f75b8b15b1cef292beee84d1699b924878812da864f080ca53bbfad6ef2f9994f63df7a0c6a8829eb3da7c4c01393d6ac71842f80dd4c0d414b4  nimbus_beacon_node
# macOS ARM64
1dfd5a3e0f638ead603243479ff9278229c9bb6a3180ad242f46a5a16ae82752d6c517b23ea9b60f301beb5945f0f422d6c5cbb53c36c19364c1209fd5dc8d5d  nimbus_beacon_node

Altair beta build (rolling release, experimental)

SHA512 checksums

# Linux AMD64
ba0b8d8e6942ad26d4500ee907607c3d07b1b745819fa053efd39047943907640d83f74f0a0d02a8a7fc8fcf9707759c048ece7c5d70c158a74a305eeda92297  nimbus_beacon_node
# Linux ARM64
0381e02b8c144b4eebf727171e622c86c271b7ffce5f6d16c8a31b8ec25f7ac5335235149d76a6f6b9fe5fdd50ca150a54cfcd907a6edfe87005c18f71793c2d  nimbus_beacon_node
# Linux ARM
119199d08bfb8c37e3f75df2dd15fd30b3ca3c5f775fcd022253cc057d792eaf909312e8416dd6ca8b7ec263f4d12fa22281916608dc004cc54fb6283609a274  nimbus_beacon_node
# Windows AMD64
3fbb77028ae2e78e59a26017b600e626dc2d8c6fca8dd78a09f0a116160e51f8db0866cfea08f9009dc03f5f0c58ca89f6be366d14cfd5d3f767342b67e4ad31  nimbus_beacon_node
# macOS AMD64
1c25ae9bfc32b7743933e54f14ee605f0e94800cd450bba4982d85717241e82e2afc5b74ed398e04f3e657ffcffee7df4ee43119830fa34847acf43bd4e27162  nimbus_beacon_node
# macOS ARM64
1155b0f766e1198186dd61bdf88866024a363fd2f54313d75475a510b248cdc74f0c71d13062ab90fee6ca939fce08e7bcd4796b0a61bd13990cd72f789b2332  nimbus_beacon_node

v1.4.2

Notes

Nimbus v1.4.2 - "Upgrade procedure: Hotfix release"

This release is marked as low-urgency for all Nimbus users other than those who have updated directly to a v1.4.x version from a version earlier than v1.1.0 - for these users this is a high-urgency release.

Notable changes

This release fixes an issue in the upgrade procedure when upgrading from a version earlier than 1.1.0 to 1.4.x.

How can I tell if I've been affected?

If you've already upgraded to 1.4.1, you can tell that you've been affected if you're seeing the following WRN log:

 Received invalid sequence of blocks

To re-iterate, this issue only affects users who are upgrading from 1.0.12 or earlier (released on 2021-03-10), and have not run any release in between. Everyone else can ignore this release.

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

Binaries

Scroll to the bottom of this release and click on the tar.gz that corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
6d7343771f10d389c95f168d9216a1a45e3579a7fbc14ab307f9909afd03c8f2506080fff41d7b1860556158917a6a0737805037a0f74ea38e2599ddd6d4fb89  nimbus_beacon_node
# Linux ARM64
2d55b9575327e822232db7f84b934041f81af4a3cf05e932abca45ce249365e8292fe84d8e739d4c7bfdcd30c6270e7361bce040d78c9558bc38092f68ae3e92  nimbus_beacon_node
# Linux ARM
dced660ad674c8604fdd3fb873ac6cf2da3b272b301610d0b7d3f8ddd57ec82488b1aa68f702e972c12ecdde0f390e5198e9487d6309464ddc7ad6ec3f86b156  nimbus_beacon_node
# Windows AMD64
587e9eda46d45294619c49864b2cc12d612ed83b2562b469df475a6cb032577f6b3669f99e2cf4b39a8e2f512d6190f6a15145d4968029f465a32aa53720eadf  nimbus_beacon_node
# macOS AMD64
e59289bfee4f64621c9f33d8b8bf834dd787d87a8c31b27b9fe48f81820411246f883613df2a4273e820f176774c4c04c259916119b936d6b0c3725d3696cd77  nimbus_beacon_node
# macOS ARM64
27679594e3707d54890299c7583fa5fd9018dca2e38ede7520f5585256fc29afe2916de7db3a6b6cb192f2bcbceb6306da1e57e1563a7c3b6b71cbb247313a1a  nimbus_beacon_node

v1.4.1

Nimbus v1.4.1 - "Every attestation counts"

This release is marked as low-urgency

Notable changes

Nimbus v1.4.0 users might have noticed that they are missing a small number of (seemingly random) attestations since the update. Our investigation into the matter has showed that, due to v1.4.0's significant performance improvements, Nimbus validators occasionally send their first attestation for a new epoch before some peers are ready. These "slow" peers end up dropping early attestations because they're busy with the epoch transition.

It's a rare occurrence, since it requires a validator to be scheduled to attest in the first slot of an epoch and for the beacon node to only be connected to "slow" peers for the respective libp2p topic. If both these conditions are true, a premature attestation may be lost in time, like tears in the rain.

As a fix, we are using a larger send delay: #2705.

For those Nimbus v1.4.0 users who are concerned about reaching optimal attestation effectiveness, we encourage you to upgrade as soon as possible.

Other changes include log flushing and metrics fixes.

Full list:

• increase attestation wait time (#2705)
• ensure logs are printed without delays (#2669)
• fix metrics on Windows (#2707)

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

Binaries

Scroll to the bottom of this release and click on the tar.gz that corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see the included "README.md" file. See pre-built binaries documentation for more.

SHA512 checksums

# Linux AMD64
28a9becba518082355d51101f046d0b2369696c22206fcb5c3ff16f4b2c418815fb22ef21942989cd99a4ed3c0883e6aff768af0fa66093fa8daa379e892e715  nimbus_beacon_node
# Linux ARM64
19b891752d3870b4477cdb128507810c95802d89090a43d598b70e66e6ca898f2a9002c9e3808d7e2aebe14d549aaaa32fade0755ad294c7ed9ba3085365f248  nimbus_beacon_node
# Linux ARM
8c19c645ffe502342cee314f4859d53c4bf21d61e67b52270438091c700556270ae5de2751f76358396a178c082db2342a2f13138e43fe161d26a1cf2786173d  nimbus_beacon_node
# Windows AMD64
0ec49818908bcbbc1a1809f45239e95f683e51fb10d4ea6da2bc47e0c1caf190e7d1b843a82fefc23f4ec9a58ee4fb26e500faa280b69aad2c6db213bae38dde  nimbus_beacon_node
# macOS AMD64
3366b353cfee7d81128ab44965ff9ed9ec642145f0984dce1f9a96210ced64b547f8d86c103f18bfdaeeb4e3b72661c6843b248117a9a5aa8afcb31089582e2a  nimbus_beacon_node
# macOS ARM64
202d6bc08c40c24c10df09124141af2bb0d120feb95459be01abb2f3ad11f8ea3dd83d52f51b210cd77c01bef17d9f1efa372ef16a50619fbbe3f3d5d35e0788  nimbus_beacon_node

v1.4.0

Release notes

This release is marked as low-urgency - please update at your convenience.

It contains improvements to attestation effectiveness and CPU usage.

It also contains improvements to the RPC APIs, as suggested by DappNode and RocketPool, and in preparation for our refactored validator client.

Old Nimbus instances

A reminder that if you're running Nimbus with a version prior to 1.0.10 (March 2021) you are exposed to a vulnerability in our core cryptography library (this library is used by all eth2 clients). See this blst security advisory for more information. If you didn't update yet, please update as soon as you can.

Notable changes

We've added:

• Nightly builds for the very adventurous. (#2640)
  • We expect users of nightly builds to be comfortable providing debugging logs.

We've fixed:

• REST API endpoints (#2585, #2586)
  • /eth/v1/beacon/pool/attestations
  • /api/eth/v1/validator/aggregate_and_proofs
• Doppelganger detection: fixed false positive on fast restart (#2656)

We've improved

• Database read performance improvements during epoch transitions and startup (#2639, #2617)
• Better usage of caches, specially when validating attestations (#2631)

Commit log

v1.3.0...v1.4.0

Update 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

Binaries

Scroll to the bottom of this release and click on the tar.gz that corresponds to your OS and architecture: unpack the archive, read the README and run the binary directly (or through one of our provided wrapper scripts).

We've designed the build process to be reproducible. In practice, this means that anyone can verify that these exact binaries were produced from the corresponding source code commits. For more about the philosophy and importance of this feature see reproducible-builds.org.

For instructions on how to reproduce the build, see "README.md" inside the archive. See pre-built binaries documentation for more.

Update guide

For precise instructions on how to update, see our guide here:
https://nimbus.guide/keep-updated.html

SHA512 checksums

# Linux AMD64
536c15a4aba9164f1b72666625c95c68ae4d5019d3419a85465dfe669dd5a9d67ab67a0d46fbcc23a1a429efb61f417f16fe4e235623196043ac0fbb67fed962  nimbus_beacon_node
# Linux ARM64
0cdaa887e35c678fe54b185690786d209e108b95566189c2fe86afd3c6f0ad03e804e9ab14c356487921d816cb65186ee8799aa54b55238dd8f9754abf634437  nimbus_beacon_node
# Linux ARM
4eb7146bffa8f72aa26305640bb0b6531bdcdf9ea656c13489636eae6e30f5a016d90c090db4f18ebe1af1292f78309e2765f60fc75af43f88d63964893c31d3  nimbus_beacon_node
# Windows AMD64
1f24a3cc0c562b198c2f69277363765ba4c04e8552be3e239cedefbdc17fb713372c7aa4b4353ccf06ca69ba375266218d59e252055955e3a5d51eeb3e682e78  nimbus_beacon_node
# macOS AMD64
519cc5e98b5e8fc07987ccd5ac67cdad15ed92aa0926c0aa8c18c6f98bf294865f66191a27b5442bfe938225a6e7aac46564d544cbe47c5fcc0200238342d7c0  nimbus_beacon_node
# macOS ARM64
16853af7f01b8b56c7560d66f85b292950b6b48119413f1d84729f10b50620f11b7c64df4ab5898e73c4eb61885e92ea1a7f33b6b030c192c1cc6684bdaf1f60  nimbus_beacon_node

v1.3.0

Release notes

This release offers safer and easier options to migrate to Nimbus from other clients. It also brings further performance optimizations.

We've added:

• A new slashingdb sub-command with import and export options. This allows for safely migrating to Nimbus to/from another client (as per the EIP-3076 slashing protection interchange format). Please see the newly prepared migration guides for the details.

• A new ncli_db validatorPerf command. This can be used to create a report for the attestation performance of validators over time (please note that ncli_db is only available when compiling from source).

• Official binaries for macOS (AMD64 and ARM64)

• Pruning of the slashing protection database and a transition to more optimal queries. This results in a significant reduction to both disk and CPU usage on nodes with a large number of attached validators.

• A more consistent level of validation for the attestations received from both third-party sources and the REST and JSON-RPC APIs. This prevents invalid attestations from being broadcasted to the network.

• Performance tuning of attestation subnet transition timings and state snapshotting intervals. This results in improved CPU and bandwidth usage.

We've fixed:

• Problems in the GossipSub subnet walking logic which were causing unnecessary bandwidth and CPU costs.

SHA512 checksums

# Linux AMD64
e405b6a696520e16629cf9527b38d9d4963e9ecc0a0b3165c3379766f182ba6d6b0c259d311100d3d7d71eaf4924b2fc9c3f6e47981721c3335209532faa4ff0  nimbus_beacon_node
# Linux ARM64
bb8d77b418d287d88839fae61f7ff9c329e92f57b979af780ac27ea258c175271e8793d880c65d7b572f94de454174fee74f9bc5d65f831ac6f359e1a0d0925b  nimbus_beacon_node
# Linux ARM
455e2dce95faeeef19f0345b97a3f30cced2c9cf28909a3d9066e3146e0d98b1d3a7f72355b0e26bc9f180e99b5d884172245504abeabc8fe6257b73fda65dc3  nimbus_beacon_node
# Windows AMD64
10f2e506bcd981b0dc535fb408a858fb735e1bdf7c03beebf1a1fff33691586513c2ff997eeae7d381fdebb1cb0c4ea026c21c7363029f705bac9039d962f719  nimbus_beacon_node
# macOS AMD64
a2ecb6c0549ea91a3504cc46ab6d1347599ace46c279b3befe1d6c91e203fd60557b907270188846ba7368fced59ef541c64d5afe54e1e0a8941622e1ac61674  nimbus_beacon_node
# macOS ARM64
2bae3edb0a44e0ad8515f6fc1a6bcacea775c8d95269d27e92ea9b4b5ba821da929309c00173bdea475fbf0fd7e7cac76580ec0f02d7f1e8e60a82916519f182  nimbus_beacon_node

v1.2.2

This is a bugfix release which improves the stability of the REST API and addresses issues discovered during the mainnet incident of 24-25 April.

We've added:

• A more efficient attestation processing pipeline (less queuing).

We've fixed:

• Insufficient validation of third-party Eth1Data votes.

• Sporadic REST API connection interruptions (due to large request or
  result payloads).

• Incorrectly logged empty GossipSub IWANT messages.

• Libp2p grafting timer: unnecessary re-grafting which occasionally led to scoring penalties.

SHA512 checksums

# Linux AMD64
46ea21b11948832b43aac6017761d0f5906b9c73ad454428e6594cfa6b45b324353acf5cbff3eca1d32f738b1728f768253ec19d8e05a913c9924e9c8750b49b  nimbus_beacon_node
# Linux ARM64
6b9c54b6e5025768f53cd7658f0be6c08d168975713bd6c18e9f76f4c09d727f9969918766c14dcda46ad11c2f7f328a87975b487817d659df0e5221c082811d  nimbus_beacon_node
# Linux ARM
be0b19ee95851a1d848ae1fb71e71a3845da57936fafc9eaea9a2b9a82add4690a9103dc69800e95d8792ae65b1664aab98dba195ce7416866891cac73dc2e1b  nimbus_beacon_node
# Windows AMD64
d56587417d23729853b097c92f4415d9ad5c938a06de85321c556bcadac85fa0e6b1a2b131ad592d70eb436367aef08d7b0f9a3e3349e60a777c0cd20d77182b  nimbus_beacon_node

v1.2.1

This is a hotfix release that solves the database migration issue highlighted in the previous release (v1.2.0) -- this problem affected new Nimbus users who used v1.1.0 to sync with the network from genesis, essentially resetting their state database and causing them to start re-syncing from genesis.

If you have used an older version of Nimbus prior to upgrading to v1.1.0, you should not be affected.

If you were affected, you have a couple of options available to you:

1. If you have backed-up your database prior to upgrading to v1.2.0, you can restore the database from backup and execute the migration successfully after upgrading to this release.

2. If you haven't backed up your database, you can upgrade to this release at your convenience; rest assured it won't delete your sync history.

Please accept our sincerest apologies for any inconvenience we may have caused. We are reviewing our release testing policies to ensure that we cover a greater number of possible upgrade paths going forward 🙏

If you still haven't had a chance to upgrade to a 1.2 release, please note that upgrading is highly recommended for a number of compelling reasons that are worth repeating here:

If v1.1 was the big I/O update, v1.2 is all about the CPU - together, these updates help secure Nimbus against future network growth, and provide us with a higher security margin and substantial profitability improvements.

To highlight just one data point, CPU usage has been cut by up to 50% over v1.1.0 ( 🙏 batched attestation processing). This makes it the first release we can officially recommend for validating on a Raspberry Pi 4.

N.B. this release contains a critical stability fix so please make sure you upgrade!

New features:

• Beta support for the official Beacon Node REST API:
  https://ethereum.github.io/eth2.0-APIs/. Enable it by launching the client with the --rest:on command-line flag

• Batched attestation verification and other reforms -> massive reduction in overall CPU usage.

• Improved attestation aggregation logic -> denser aggregations which in turn improve the overall health of the network and improve block production.

• More efficient LibP2P connection handling code -> reduction in overall memory usage.

We've fixed:

• A critical stability issue in attestation processing.

• scripts/run-*-node.sh no longer prompts for a web3 provider URL when the --web3-url command-line option has already been specified.

SHA512 checksums

# Linux AMD64
6bbdad0d424aadfef9119277c00702b58e7c7f020a329a7baa7237144cc3fc49e252cdfcc146b5b8f384207be6253655b1daacb342fc255defec1d56c671a3df  nimbus_beacon_node
# Linux ARM64
ab759a3cf6eadaee97565d139e3546ef1a4716bede03d50aebe650b82624fc65020dc385d77e1afa78779537dd0173201121855fd64c61d74c8e5e29536b90ef  nimbus_beacon_node
# Linux ARM
aaa31248357a670c9ae3e4757c6f6b7f8b03cd5716d01ab519e17ab891d7b3fd08b1693f9639cec87634e8093106016730857256094515d0d648c3da50038279  nimbus_beacon_node
# Windows AMD64
7bf0bd09a297102f9724dad6912504e088be70908aeb1cb7f96ba7000dd34e780e59c40d188f4de890d09780e4ca2e5716d5684350e409e081c2020e1652bbcc  nimbus_beacon_node

v1.2.0

If v1.1.0 was the big I/O update, v1.2.0 is all about the CPU - together, these updates help secure Nimbus against future network growth, and provide us with a higher security margin and substantial profitability improvements.

To highlight just one data point, CPU usage has been cut by up to 50% over v1.1.0 ( 🙏 batched attestation processing). This makes it the first release we can officially recommend for validating on a Raspberry Pi 4.

N.B. this release contains a critical stability fix so please make sure you upgrade!

New features:

• Beta support for the official Beacon Node REST API:
  https://ethereum.github.io/eth2.0-APIs/. Enable it by launching the client with the --rest:on command-line flag

• Batched attestation verification and other reforms -> massive reduction in overall CPU usage.

• Improved attestation aggregation logic -> denser aggregations which in turn improve the overall health of the network and improve block production.

• More efficient LibP2P connection handling code -> reduction in overall memory usage.

We've fixed:

• A critical stability issue in attestation processing.

• scripts/run-*-node.sh no longer prompts for a web3 provider URL when the --web3-url command-line option has already been specified.

SHA512 checksums

# Linux AMD64
7e999b115667cf5da94c6b251bae82118af0c5b13ebd1ca800431bbb9f75188fb945bd7ae0cbdc7457cd74f695431075682a8ba52f442f48bca33d74a16e6f6c  nimbus_beacon_node
# Linux ARM64
1a79c60a9872c09501185add421dc2924035ade05822da7e7e94f31fb687ddba7ce6354bf8a00073384687be90b9cde9ff8b298d4d20d07608deca49ecd39ccc  nimbus_beacon_node
# Linux ARM
9eb8700fd105a3bc3cd269b51290084e836542b86a883a7b0fbe011d80a8288a4181119027810b469c470933297af0f832f877386fa2cef27e37496c7b51a098  nimbus_beacon_node
# Windows AMD64
4266cae744a63c8a51b7b5eda6c5ecb0adb7af7e72bcad96588d3e6c0532f0bfbeea4a7e9d2fc4e826021b5cb5b5aa744c6dc91881bd9bbc70551dceb76b608b  nimbus_beacon_node

v1.1.0

This release brings planned reforms to our database schema that provide substantial performance improvements and pave the way for an improved pause-free doppelganger detection (reserved for a future release).

Please be aware that, while we are committed to maintaining backwards compatibility between releases, this release does not support seamlessly downgrading back to any previous 1.0.x release. While you shouldn't need to downgrade, if for some reason you do, please get in touch with us before.

Even though we've tested this release extensively, as an extra safety precaution we advise you to **backup your Nimbus database (nbc.sqlite3) before upgrading -- the best way to do this is to simply copy it over (you'll find it either in build/data/shared_mainnet_0/db/, or the directory you supplied to the --data-dir argument when you launched Nimbus).

New features:

• More efficient state storage format ==> reduced I/O load and lower storage requirements.

• More efficient in-memory cache for non-finalized states ==> significant reduction in memory
  usage.

• More efficient slashing database schema ==> scales better to a larger number of validators.

• The metrics support is now compiled by default thanks to a new and more secure HTTP back-end.

• setGraffiti JSON-RPC call for modifying the graffiti bytes of the client at run-time.

• next_action_wait metric indicating the time until the next scheduled
  attestation or block proposal.

• More convenient command-line help messages providing information regarding the default
  values of all parameters.

• --direct-peer gives you the ability to specify gossip nodes to automatically connect to.

• Official docker images for ARM and ARM64.

• Support for fallback --web3-url providers.

We've fixed:

• Long processing delays induced by database pruning.

• File descriptor leaks (which manifested after failures of the selected web3 provider).

• The validator APIs now return precise actual balances instead of rounded effective balances.

• A connection tracking problem which produced failed outgoing connection attempts.

Breaking changes:

• Nimbus-specific JSON-RPCs intended for debug purposes now have the debug_ prefix:

  • getGossipSubPeers is now debug_getGossipSubPeers
  • getChronosFutures is now debug_getChronosFutures

SHA512 checksums:

# Linux AMD64
8d553ea5422645b5f06001e7f47051706ae5cffd8d88c45e4669939f3abb6caf41a2477431fce3e647265cdb4f8671fa360d392f423ac68ffb9459607eaab462  nimbus_beacon_node
# Linux ARM64
93ffd03a0ce67f7d035e3dc45e97de3c2c9a05a8dd0c6d5f45402ddb04404dc3cf15b80fee972f34152ef171ce97c40f794448bc779ca056081c945f71f19788  nimbus_beacon_node
# Linux ARM
f2e75f3fae2aea0a9f8d45861d52b0e2546c3990f453b509fab538692d18c64e65f58441c5492064fc371e0bc77de6bab970e05394cfd124417601b55cb4a825  nimbus_beacon_node
# Windows AMD64
fd68c8792ea60c2c72e9c2201745f9698bfd1dae4af4fa9e1683f082109045efebd1d80267f13cafeb1cd7414dc0f589a8a73f12161ac2758779369289d5a832  nimbus_beacon_node