This release contains a fix to a known issue with the database which caused excessive database usage (>20gb when it should be ~8gb) and missing beacon state errors whilst syncing.
This release is compatible with existing databases, but you must re-sync if you wish to benefit from these fixes.
To reiterate, to repair a broken Lighthouse database please re-sync (lighthouse bn --purge-db) using this release.
Changes
- Alternative (to BeaconChainHarness) BeaconChain testing API (#1380)
- Check Cargo.lock freshness on CI (#1565)
- Prevents releases from indicating the the git tree is dirty in the release tag.
- Fix bug in database pruning (#1564)
- Resolves issue regarding excessive database usage and issues during sync. Requires a full resync.
- Fix order of testnet config load (#1558)
- Fixes issues when using non-mainnet specifications (only relevant to developers).
Binaries
Binaries are supplied for two platforms:
x86_64-unknown-linux-gnu: AMD/Intel 64-bit processors (most desktops, laptops, servers)aarch64-unknown-linux-gnu: 64bit ARM processors (Raspberry Pi 4)
Additionally there is also a -portable suffix which indicates if the portable feature is used:
- Without
portable: uses modern CPU instructions to provide the fastest signature verification times (may causeIllegal instructionerror on older CPUs) - With
portable: approx. 20% slower, but should work on all modern 64-bit processors.