github sigp/lighthouse v1.5.2
Two Crows

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

Summary

This release contains useful optimizations for mainnet and testnet users. It also contains improvements to logging, tightened file permissions and usability improvements.

Mainnet users will benefit from #2547, which reduces the time it takes to set a block as the canonical head. This reduces the likelihood of late-to-arrive blocks causing missed head votes for attesters. This should see a marginal increase in validator rewards.

Prater and Prymont users will benefit from #2560 which greatly reduces the load during block processing. This will help overloaded nodes run more smoothly. Any Prater or Pyrmont user running v1.5.1 or earlier should update at their next convenience. This optimization was included in v1.5.2-rc.0, so there is no pressing need to update testnet nodes running that release-candidate.

Cross-compatibility between Lighthouse and Teku has been improved by #2587. This will benefit Infura users across mainnet and testnets.

Breaking Changes

The breaking changes listed here are introduced between v1.5.1 and this this release. No breaking changes have been introduced since v1.5.2-rc.0.

Tighter File Permissions

The log file generated with the --logfile flag will now have tighter file permissions (600). Previously, all users had read permissions. Now, read permissions are only granted to the user running the lighthouse binary. Since the log file is created anew on each restart, these permissions will take affect immediately after updating.

The API token files generated by the lighthouse vc will also be created with the same restricted file permissions (600). If the API token files already exist, no changes will be made to their permissions.

Restricting access to log files and API tokens is a security best-practice.

Remote Signer

The lighthouse remote_signer command has been removed. This feature was incomplete and has been archived. At present, there are no plans to reinstate it. Once #2522 is complete, Lighthouse will support remote signing via Web3Signer.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Beacon Node Validator Client
Staking Users Medium Priority Medium Priority
Non-Staking Users Medium Priority ---

Users Classes and Priorities

Staking users are those who use lighthouse bn and lighthouse vc to stake on the Beacon Chain. Non-staking users are those who run a lighthouse bn for non-staking purposes (e.g., data analysis or applications).

High priority updates should be completed as soon as possible (e.g., hours or days). Medium priority updates should be completed at the next convenience (e.g., days or a week). Low priority updates should be completed in the next routine update cycle (e.g., two weeks).

All Changes

Changes are since the v1.5.1 release.

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.5.2-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v1.5.2-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.5.2-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v1.5.2-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v1.5.2-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v1.5.2-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.5.2-x86_64-windows.tar.gz PGP Signature
x86_64 lighthouse-v1.5.2-x86_64-windows-portable.tar.gz PGP Signature
System Option - Resource
Docker v1.5.2 sigp/lighthouse

Don't miss a new lighthouse release

NewReleases is sending notifications on new releases.