Skip to content

Releases: sigp/lighthouse

Centipede Aliens

17 Aug 09:22
@github-actions github-actions
v1.5.0-rc.1
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
c737983
Compare
Choose a tag to compare
Centipede Aliens Pre-release
Pre-release

⚠️ Pre-Release: Not for Production Use ⚠️

This is a pre-release. It is not production-ready and not recommended for mainnet use.

Whilst we don't recommend this release for critical and/or mainnet use, we do recommend that users upgrade their Pyrmont and Prater nodes to this version. We assume that nothing critical is occurring on these testnets.

For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html

Summary

Compared to v1.5.0.-rc.0, this pre-release contains three fixes:

  1. A fix to the API to add quotes around a 64-bit integer. (#2515)
  2. Dependency upgrades to remove a "yanked" warning whilst compiling. (#2513)
  3. A change to our network peer scoring to reduce the impact of early sync committee messages. (#2510)

The most notable of these changes is (3), it addresses an issue on an Altair devnet where we saw a significant number of peer disconnections due to early sync committee messages. Although these messages shouldn't occur in theory, they are occurring in practice. As such, we recommend that all Pyrmont users should upgrade to this release before the Altair fork at 2021-08-19 12:00:07Z.

Users upgrading from v1.4.0 or earlier read the release notes in v1.5.0.-rc.0 to understand the breaking changes introduced there.

All Changes

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.0-rc.1-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.1-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.1-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.1-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v1.5.0-rc.1-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v1.5.0-rc.1-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
System Option - Resource
Docker v1.5.0-rc.1 sigp/lighthouse
Assets 14
Loading

Numbericons [PRE-RELEASE]

12 Aug 10:05
@github-actions github-actions
v1.5.0-rc.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
4c4ebfb
Compare
Choose a tag to compare
Numbericons [PRE-RELEASE] Pre-release
Pre-release

⚠️ Pre-Release: Not for Production Use ⚠️

This is a pre-release. It is not production-ready and not recommended for mainnet use.

Whilst we don't recommend this release for critical and/or mainnet use, we do recommend that users upgrade their Pyrmont and Prater nodes to this version. We assume that nothing critical is occurring on these testnets.

For more information on pre-releases, see: https://lighthouse-book.sigmaprime.io/advanced-pre-releases.html

Pyrmont Altair Upgrade

This update is mandatory for all nodes on the Pyrmont testnet. At 2021-08-19 12:00:07Z, Pyrmont will undergo an irregular state transition to upgrade to the Altair specification (i.e., there will be a hard fork).

Users running Lighthouse v1.4.0 or earlier will fail to undergo this state-transition and will be left on the wrong side of history.

The Eth2 developers (including the Lighthouse team) are upgrading Pyrmont in anticipation for the same upgrade on mainnet. Failing to upgrade your Pyrmont nodes will impede their efforts to deliver a smooth upgrade on mainnet. Please upgrade your Pyrmont nodes!

To be clear, mainnet users should not implement this release-candidate version. Prater users may upgrade, but are not required to.

Summary

This is a substantial update to Lighthouse with two important caveats:

  • This update involves a change to the Beacon Node database schema which is presently not backwards compatible. After upgrading the Beacon Node (BN), users will need to delete the existing BN database and re-sync in order to revert to a previous version. This does not affect the slasher or validator client. Re-syncing is only required on a downgrade, there is no need to re-sync if upgrading to this release from an earlier version --- the database migration will happen automatically.
  • Pyrmont users must upgrade their BN and Validator Client (VC) at the same time. Due to the upcoming Altair upgrade, pre-v1.5.0-rc.0 VCs and BNs are incompatible. This only applies to Pyrmont, other networks are not affected.

Failing to upgrade both the BN and VC on Pyrmont will result in the VC declaring the BN to be "incompatible". The solution is simple; update and restart both processes.

With the caveats clearly stated, the Lighthouse team is proud to present this release which contains:

  • Full support for the upcoming Altair fork on the Pyrmont testnet at 2021-08-19 12:00:07Z.
  • A refined and improved networking stack.
  • Doppelganger protection (disabled by default).
  • The reorg event has been added to the HTTP API.
  • Countless bug/annoyance fixes.
  • Caching of attestations for unknown blocks, to improve validator rewards (#2319)
  • Hardware-optimized hashing (#2426)
  • Faster and more reliable attesting for validators (#2478)
  • Support for compiling under the latest version of Rust (#2483)

Breaking Changes

  • The database schema used for v1.5.0-rc.0 nodes (including freshly-synced nodes and those upgraded from earlier versions) is not compatible with earlier versions of Lighthouse. This was mentioned earlier.
  • Exclusively for Pyrmont nodes, the VC and BN must both be running v1.5.0-rc.0. Earlier versions are not compatible with v1.5.0-rc.0.
  • Some Prometheus metrics and the /lighthouse/validator_inclusion endpoints have been modified to be Altair-compatible. See #2416 for detail.

All Changes

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.0-rc.0-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.0-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.0-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v1.5.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v1.5.0-rc.0-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 [lighthouse-v1.5.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz](https://...
Read more
Assets 14
Loading

Space Beth

10 Jun 05:20
@github-actions github-actions
v1.4.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
3b600ac
Compare
Choose a tag to compare
Space Beth

Summary

This is a low-priority update. It primarily contains optimizations which reduce the impact of the Beacon Node on RAM, CPU, disk I/O and Eth1 nodes.

Whilst we suggest all users update to this release at their convenience, there is no pressing reason to do so unless they are concerned that the resource requirements of Lighthouse are outpacing their hardware.

Notable features in this release are:

  • A reduction in memory footprint. On mainnet, this reduces memory usage from ~6 GB to ~1.5 GB. (#2299)
  • Improvements to avoid disk and memory intensive operations. (#2289, #2376)
  • An 80% reduction in Eth1 queries. (#2340)
  • Beta Windows support, not presently recommended for production. (#2333)

As mentioned in the "Memory Allocator Tuning" section, some users running Linux without glibc may need to apply the --disable-malloc-tuning CLI flag to lighthouse bn (the Beacon Node) in order to avoid a panic at startup. We expect this scenario to be very rare and have not encountered it during internal testing or during external release candidate testing. We only recommend using this flag if you experience a failure as it will substantially increase memory usage. We only expect to see this issue on obscure Linux installations; MacOS, Ubuntu, Amazon Linux and other common operating systems are unaffected.

Breaking Changes

  • #2272 changes the behaviour of the HTTP API when retrieving blocks/block-roots on a slot that was skipped. Previously, Lighthouse returned the value for the block at the previous slot. Now, to keep in-line with other clients, Lighthouse will return a 404.
  • #2299 automatically configures the GNU memory allocator (see "Memory Allocator Tuning" section for more detail).
  • #2251 adds additional fields to the lighthouse/health HTTP API endpoint.
  • #2392 ensures that using the --eth1-endpoints flag enables syncing the Eth1 chain. This fixes a regression in a previous release.

Update Priority

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

User Class Beacon Node Validator Client
Staking Users Low Priority Low Priority
Non-Staking Users Low 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).

Notes

Memory Allocator Tuning

With #2299, Lighthouse now automatically configures the GNU Memory Allocator at startup to provide a more optimal memory footprint.

This alone reduces the memory consumption of Lighthouse by at least 50%. However, some Linux systems may have an incompatible memory allocator. This will cause Lighthouse to panic and exit at startup (only at startup, never after it has begun operation).

If users experience a panic and instant exit during startup, do not fear. Simply provide the --disable-malloc-tuning flag to completely disable this new feature.

For example:

lighthouse --disable-malloc-tuning bn --staking

If you do experience this error, please raise an issue. We are eager to ensure Lighthouse runs on all platforms by default.

We have never seen this panic during our testing or on the release candidate, but we are aware it is possible on some obscure platforms.

Changes to Announced Features

Since Lighthouse Update #36 announced a list of features and a timeline for v1.4.0, the development team has decided to split the features into two, separate releases:

  • v1.4.0: to be released approximately one week earlier than scheduled, but only containing:
    • Beta Windows support, not presently recommended for production.
    • An 80% reduction in Eth1 queries. (Note: this does not reduce the time required to sync the Eth1 cache).
    • A reduction in memory footprint (on mainnet, this reduces memory usage from ~6 GB to ~1.5 GB).
  • v1.5.0: to be release late June, containing:
    • Altair testnet support.
    • Doppelganger protection.
    • Support for remote signing in the validator client.

All Changes

  • v1.4.0 (#2402)
  • Modify Malloc Tuning (#2398)
  • Only perform malloc tuning for beacon node (#2397)
  • Make less logs for attn with unknown head (#2395)
  • Fix options for --eth1-endpoints flag (#2392)
  • v1.4.0-rc.0 (#2379)
  • Revert "Network protocol upgrades (#2345)" (#2388)
  • Add early check for RPC block relevancy (#2289)
  • Return a specific error for frozen attn states (#2384)
  • Return more detail in Eth1 HTTP errors (#2383)
  • Use the forwards iterator more often (#2376)
  • Minimum Outbound-Only Peers Requirement (#2356)
  • Reduce outbound requests to eth1 endpoints (#2340)
  • Correct issue with dialing peers (#2375)
  • Network protocol upgrades (#2345)
  • Tune GNU malloc (#2299)
  • Monitoring service api (#2251)
  • More stringent dialing (#2363)
  • Add Windows to Bors config (#2358)
  • Enable Compatibility with Windows (#2333)
  • Write validator definitions atomically (#2338)
  • Add NETWORK_ID variable (#2330)
  • Updated to comply with new clippy formatting rules (#2336)
  • Add testing for beacon node and validator client CLI flags (#2311)
  • Add SensitiveUrl to redact user secrets from endpoints (#2326)
  • cargo audit fix (#2331)
  • Filter Disconnected Peers from Discv5 DHT (#2219)
  • Fix typos in redundancy docs (#2320)
  • 404's on API requests for slots that have been skipped or orphaned (#2272)
  • Allow specifying alternative url for deposit_contract (#2295)
  • Add a no-wait flag for voluntary exits (#2292)
  • Fix readme typo (#2312)

Binaries

See pre-built binaries documentation.

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

Windows for Lighthouse is still in beta and binaries are not yet provided.

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

Goomby [PRE-RELEASE]

03 Jun 04:40
@github-actions github-actions
v1.4.0-rc.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
f6280aa
Compare
Choose a tag to compare
Goomby [PRE-RELEASE] Pre-release
Pre-release

⚠️ Pre-Release: Not for Production Use ⚠️

This is a pre-release, which means it is not production-ready and not recommended for mainnet use. Since this is our first pre-release, these release notes will contain a short section describing pre-releases.

Find the latest stable release here: https://github.com/sigp/lighthouse/releases/latest/

Introduction to Pre-Releases

Note: this is a modified version of an announcment posted on Discord and via the mailing list.

We will publish pre-releases when we've developed a release that passes our own internal testing, but we'd still like to see some users running it before we announce it as a proper, stable release. We haven't done this in the past, but we'll start doing it when we make changes which might behave differently on various platforms and operating systems (e.g., tuning the system memory allocator). This allows us to get feedback on how the new version works on a broader range of hardware and operating systems.

Github will clearly show this release as a "Pre-release" and it won't show up as the "latest" release: https://github.com/sigp/lighthouse/releases/latest/. However, it will show up on the "Releases" page, so please pay attention to avoid the pre-releases when you're looking for stable Lighthouse.

Here's a quick guide:

  • If it has a version tag like v1.4.0 and does not have a pre-release tag, then we're announcing it as a stable release and you should run it on mainnet.
  • If it has a version tag like v1.4.0-rc.0 and does have a pre-release tag, then it's not necessarily stable and you should only run it on testnets.

If you have the time and you'd like to help out with testing, please try out the pre-release on Pyrmont or Prater when it is released. It'll give you a sneak-peak at our latest enhancements and help our development process.

Summary

Since Lighthouse Update #36 announced a list of features and a timeline for v1.4.0, the development team has decided to split the features into two, separate releases:

  • v1.4.0: to be released approximately two weeks earlier than scheduled, but only containing:
    • Beta Windows support, not presently recommended for production.
    • An 80% reduction in Eth1 queries. (Note: this does not reduce the time required to sync the Eth1 cache).
    • A reduction in memory footprint (on mainnet, this reduces memory usage from ~6 GB to ~1 GB).
  • v1.5.0: to be release mid-to-late June, containing:
    • Altair testnet support.
    • Doppelganger protection.
    • Support for remote signing in the validator client.

Memory Allocator Tuning

With #2299, Lighthouse now automatically configures the GNU Memory Allocator at startup to provide a more optimal memory footprint.

This alone reduces the memory consumption of Lighthouse by at least 50%. However, some Linux systems may have an incompatible memory allocator. This will cause Lighthouse to panic and exit at startup (only at startup, never after it has began operation).

If users experience a panic and instant exit during startup, do not fear. Simply provide the --disable-malloc-tuning flag to completely disable this new feature.

For example:

lighthouse --disable-malloc-tuning bn --staking

If you do experience this error, please raise an issue. We are eager to ensure Lighthouse runs on all platforms by default.

Breaking Changes

  • #2272 changes the behaviour of the HTTP API when retrieving blocks/block-roots on a slot that was skipped. Previously, Lighthouse returned the value for the block at the previous slot. Now, to keep in-line with other clients, Lighthouse will return a 404.
  • #2299 automatically configures the GNU memory allocator (see previous section for more detail).
  • #2251 adds additional fields to the lighthouse/health HTTP API endpoint.

All Changes

  • v1.4.0-rc.0 (#2379)
  • Revert "Network protocol upgrades (#2345)" (#2388)
  • Add early check for RPC block relevancy (#2289)
  • Return a specific error for frozen attn states (#2384)
  • Return more detail in Eth1 HTTP errors (#2383)
  • Use the forwards iterator more often (#2376)
  • Minimum Outbound-Only Peers Requirement (#2356)
  • Reduce outbound requests to eth1 endpoints (#2340)
  • Correct issue with dialing peers (#2375)
  • Network protocol upgrades (#2345)
  • Tune GNU malloc (#2299)
  • Monitoring service api (#2251)
  • More stringent dialing (#2363)
  • Add Windows to Bors config (#2358)
  • Enable Compatibility with Windows (#2333)
  • Write validator definitions atomically (#2338)
  • Add NETWORK_ID variable (#2330)
  • Updated to comply with new clippy formatting rules (#2336)
  • Add testing for beacon node and validator client CLI flags (#2311)
  • Add SensitiveUrl to redact user secrets from endpoints (#2326)
  • cargo audit fix (#2331)
  • Filter Disconnected Peers from Discv5 DHT (#2219)
  • Fix typos in redundancy docs (#2320)
  • 404's on API requests for slots that have been skipped or orphaned (#2272)
  • Allow specifying alternative url for deposit_contract (#2295)
  • Add a no-wait flag for voluntary exits (#2292)
  • Fix readme typo (#2312)

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.4.0-rc.0-x86_64-apple-darwin.tar.gz PGP Signature
x86_64 lighthouse-v1.4.0-rc.0-x86_64-apple-darwin-portable.tar.gz PGP Signature
x86_64 lighthouse-v1.4.0-rc.0-x86_64-unknown-linux-gnu.tar.gz PGP Signature
x86_64 lighthouse-v1.4.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz PGP Signature
aarch64 lighthouse-v1.4.0-rc.0-aarch64-unknown-linux-gnu.tar.gz PGP Signature
aarch64 lighthouse-v1.4.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz PGP Signature
System Option - Resource
Docker v1.4.0-rc.0 sigp/lighthouse
Assets 14
Loading

Pencilvester

14 Apr 00:36
@github-actions github-actions
v1.3.0
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
3a24ca5
Compare
Choose a tag to compare
Pencilvester

Summary

This release contains an important bug fix to the Beacon Node (lighthouse bn) and should be considered high priority for all stakers.

An additional validation condition is applied to aggregated attestations which prevents incorrect attestations from filling up the operations pool (#2306). Additionally, #2307 provides improvments to block-packing which will result in better block rewards for stakers.

Update now for safety and profit.

Outdated Lighthouse Intances

Analysis of the network shows a concerning portion of users are running Lighthouse with a version prior to v1.2.0. These users are exposed to a vulnerability in the core cryptography library of Lighthouse (and other Eth2 clients). See this blst security advisory for more information. It is critically important to keep Lighthouse updated when high priority updates are announced!

Breaking Changes

This release contains a very minor breaking change to the CLI interface. We do not expect any users to be affected by this change, but please read this section before updating.

The --disable-enr-auto-update value previously accepted a value that was ignored, only the presence of the flag had an effect. See the following examples:

  • Worked before this release, will continue to work.
    • lighthouse bn --disable-enr-auto-update
  • Worked before this release, will not work after this release.
    • lighthouse bn --disable-enr-auto-update yes
    • lighthouse bn --disable-enr-auto-update no
    • lighthouse bn --disable-enr-auto-update meow

For more detail, see #2303.

Update Priority

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

User Class Beacon Node Validator Client
Staking Users ⚠️ High Priority ⚠️ No Action Required
Non-Staking Users Low 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

  • v1.3.0 (#2310)
  • Pack attestations into blocks in parallel (#2307)
  • Add specific log and metric for delayed blocks (#2308)
  • Add check for aggregate target (#2306)
  • Clean up warnings (#2240)
  • Correcting disable-enr-auto-update flag definition (#2303)
  • Avoid BeaconState clone during metrics scrape (#2298)
  • Correcting command example validator exit (#2291)
  • Use generic BLS object instead of BLST (#2290)
  • Fix local testnet scripts (#2229)

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

Shleemypants

30 Mar 06:10
@github-actions github-actions
v1.2.2
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
9eb1945
Compare
Choose a tag to compare
Shleemypants

Summary

This release contains a fix for an issue (#2280) where a small clock disparity between the beacon node and validator client would cause errors stating "request epoch [n+1] is ahead of the current epoch [n]". See #2280 for more information.

We recommend the following users update at their earliest convenience:

  • Users who have experienced the error message described in #2280.
  • Users who are running their validator clients on different physical hosts to their beacon nodes.

This release also mitigates an incompatibility with Eth2 Infura (not Eth1 Infura) which was prematurely including Altair parameters in their API endpoints. See Consensys/teku#3749 for more information.

Note: please ensure you are using the latest Rust to build Lighthouse. We require 1.51 or later, most users can update Rust by running rustup update.

All Changes

  • v1.2.2 (#2287)
  • Allow for a clock disparity on the duties endpoints (#2283)
  • Expand observed attestations capacity (#2266)
    • Fixes a rare edge-case where late attestations could be rejected if they arrived within the 500ms gossip clock disparity tolerance period, whilst another attestation was received early. This is not a critical or common error.
  • correcting name of flag (#2285)
  • Add to docs that macOS binaries are available (#2281)
  • VC: accept unknown fields in chain spec (#2277)
    • Fixes incompatibility with Eth2 Infura.
  • Fix default implementation on FixedVector (#2264)
  • Update mailing list link (#2269)

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

Catogami

18 Mar 06:29
@github-actions github-actions
v1.2.1
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
b34a79d
Compare
Choose a tag to compare
Catogami

Summary

This release contains an optimization that significantly reduces the likelihood of locally-produced blocks being orphaned (#2243). It also contains a bug fix for the lighthouse account validator exit command (#2257).

We recommend all staking users update at their early convenience. Users who update will be benefiting themselves and the network as a whole.

Additional Changes

  • A new flag has been added to the validator import flow to assist with automated setups (#2228).
  • Support for the Prater testnet has been added (#2260). This testnet is intended for client developers and may be unstable; users should continue with Pyrmont.

All Changes

  • v1.2.1 (#2263)
  • Fix voluntary exit to work with latest beacon api (#2257)
  • Optimize validator duties (#2243)
  • Validator import password flag (#2228)
  • Add prater testnet config (#2260)
  • Version bump milagro_bls to v1.4.2 (#2261)

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

Tony

10 Mar 05:41
@github-actions github-actions
v1.2.0
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
3919737
Compare
Choose a tag to compare
Tony

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
Assets 14
Loading

Hamurai

22 Feb 08:31
@github-actions github-actions
v1.1.3
This tag was signed with the committer’s verified signature.
paulhauner Paul Hauner
GPG key ID: 5E2CFF9B75FA63DF
Learn about vigilant mode.
46920a8
Compare
Choose a tag to compare
Hamurai

Summary

This release contains a fix to a known issue which can cause excessive memory consumption as documented in #2215.

We recommend all users update at their earliest convenience. Users directly experiencing the issue described in #2215 should update immediately.

Additionally, a false-positive warning about resource consumption ("State advance too slow") was fixed. See #2214 for more details.

Excessive Resource Consumption

If your node is continually printing the follow log, then you are affected by the bug described in #2215 and should update as soon as possible:

Feb xx xx:xx:xx.xxx INFO Address updated                         udp_port: 9000, ip: ::ffff:xxx.xxx.xxx.xxx, service: libp2p

Note: the Lighthouse team is only aware of 3 or 4 cases at this point in time.

All Changes

  • v1.1.3 (#2217)
  • Fix false positive "State advance too slow" logs (#2218)
  • Address ENR update loop (#2216)

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

Jerry Smith

19 Feb 03:03
@github-actions github-actions
v1.1.2
8c6537e
Compare
Choose a tag to compare
Jerry Smith

Summary

Fixes a bug (#2211) which prevented the HTTP servers from starting when the CORS wildcard was supplied.

This update is only recommended for users who are experiencing issues with the CORS flag. There is no need to upgrade if your Lighthouse nodes are running on v1.1.1 without emitting any relevant CRIT, ERRO or WARN messages.

Users running versions prior to v1.1.1 should upgrade to v1.1.2 for the reasons described in the v1.1.1 release notes.

CORS Bug

The following flags would cause an issue if supplied to the v1.1.1 BN or VC:

  • --http-allow-origin "*"
  • --metrics-allow-origin "*"

All Changes

  • v1.1.2 (#2213)
  • Switch back to warp with cors wildcard support (#2211)
  • Add slot offset computing to be downloaded slot (#2198)
  • Fix short sha in github actions (#2210)
  • Update rustup in release action (#2206)

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