github sigp/lighthouse v1.2.0
Tony

latest releases: v5.3.0, v5.2.1, v5.2.0...
3 years ago

Summary

This release marks the first minor version increase since the v1.1.x series. It contains several improvements to Lighthouse's stability and performance, particularly for users running multiple validators.

Removal of the pubkey cache file (which has historically been a source of obscure bugs) necessitates a change to the database schema, which will be applied automatically on start-up. A side effect of this schema change is that downgrading Lighthouse will not be possible after upgrading. We will be standing by to make a point release should any issues arrive, although increased testing for this release gives us hope that won't be necessary.

Due to the changes to the API, it is essential to update both the beacon node and validator client to the new version.

This release should improve the health of the entire network (in addition to boosting individual rewards), so we recommend that all users upgrade as soon as they're able.

Highlights

  • A mechanism was introduced to handle blocks that arrive early. This has the potential to improve validator rewards by ensuring that Lighthouse follows the chain as promptly as possible, and also solves an issue with peer reputation (#2155).
  • Update the HTTP API to align with the API spec on the validator status field. This is a breaking change which will require changes to downstream API consumers (#2149).
  • Prune the slashing protection database periodically, to prevent it from becoming oversized and slowing down signing. This is particularly relevant for users with large numbers of validators (100+), and has shown marked improvements for our Pyrmont validators (#2194).
  • Add the ability to set the graffiti from a file, for maximum flexibility when defacing the graffiti wall. Check out the docs for this new feature in the book: https://lighthouse-book.sigmaprime.io/graffiti.html (#2044).
  • Remove the pubkey cache file (pubkey_cache.ssz), storing its contents in the database instead (#2234).
  • Expedite block proposal by running slot processing before the proposal window. This aims to get blocks out earlier so that they have more time to propagate and are less likely to be orphaned (#2241).

All Changes

  • Release v1.2.0 (#2249)
  • Fix proposer cache priming upon state advance (#2252)
  • Release candidate v1.2.0-rc.0 (#2248)
  • Prevent adding and dialing bootnodes when discovery is disabled (#2247)
  • Update blst to 0.3.3 (#2246)
  • Use advanced state for block production (#2241)
  • Use the database to persist the pubkey cache (#2234)
  • Resolve RUSTSEC-2020-0146 (#2242)
  • Expose the startup timestamp to Prometheus (#2233)
  • Set graffiti per validator (#2044)
  • Update to the latest libp2p (#2239)
  • Bump spec tests to v1.0.1 (#2235)
  • Improve error when user doesn't have a wallet (#2231)
  • update tokio-stream to 0.1.3 and use BroadcastStream (#2212)
  • Lint for sum and product in consensus code (#2226)
  • Make lighthouse_version compatible with old Git (#2223)
  • Prune slashing protection DB (#2194)
  • Allow HTTP API to return SSZ blocks (#2209)
  • Update ValidatorStatus to match the v1 API (#2149)
  • Handle early blocks (#2155)
  • Fix lighthouse_version (#2221)

Binaries

See pre-built binaries documentation.

The binaries are signed with Sigma Prime's PGP key: 15E66D941F697E28F49381F426416DC3F30674B0

System Architecture Binary PGP Signature
x86_64 lighthouse-v1.2.0-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v1.2.0-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.2.0-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v1.2.0-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v1.2.0-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v1.2.0-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
System Option - Resource
Docker v1.2.0 sigp/lighthouse

Don't miss a new lighthouse release

NewReleases is sending notifications on new releases.