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:
-
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.
-
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:oncommand-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.shno longer prompts for a web3 provider URL when the--web3-urlcommand-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