Skip to content

Kyle
Compare
Choose a tag to compare
@github-actions github-actions released this 28 Jun 04:02
· 249 commits to stable since this release
v5.2.1
This tag was signed with the committer’s verified signature.
michaelsproul Michael Sproul
GPG key ID: 77B1309D2E54E914
Learn about vigilant mode.
9e12c21
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Summary

This medium-priority release contains bugfixes for issues identified in v5.2.0. Users who have experienced sync issues with v5.2.0 are recommended to upgrade.

The list of bugfixes includes:

  • Prevention of forwards sync stalls after restarting, through more robust handling of peer disconnects and errors (#5969, #5945, #5993).
  • Prevention of backfill sync stalls (#5969).
  • Removal of unnecessary warnings for stale blobs propagated on gossip by other clients (#5935). The log message WARN Could not verify blob sidecar for gossip. Ignoring the blob sidecar should no longer be seen.
  • Correct sizing of the slasher database for the growing validator sets on mainnet and Holesky (#5934).

Breaking Changes

There are no breaking changes between v5.2.0 and v5.2.1. Please see the release notes for v5.2.0 if you are upgrading from a prior 5.x.x release.

Known Issues

Teku 24.10 BN Incompatibility

Beacon nodes running Teku 24.10.x and newer are not compatible out of the box with the validator client from this release. If you want to run Lighthouse VC v5.2.x with Teku BN 24.10.x you must use the --produce-block-v3 flag with Lighthouse. Upgrading to Lighthouse v5.3.0 is preferable as it fixes the incompatibility without requiring any flags.

Nethermind v1.26.0 and Reth v1.0.0 engine_getClientVersionV1 bug

Nethermind v1.26.0 and Reth v1.0.0 include an implementation of engine_getClientVersionV1 which is not compliant with the API specification and does not work with Lighthouse. We recommend upgrading Nethermind to v1.27.0. At time of writing there is no compatible Reth release available.

The warning generated by a non-compliant implementation is:

WARN Execution engine call failed error: InvalidClientVersion("Input must be exactly 8 characters long (excluding any '0x' prefix)"), service: exec

This warning can be safely ignored, although it may cause a slight degradation to node performance as Lighthouse flip-flops the EL's state between healthy and unhealthy.

See NethermindEth/nethermind#7013 and paradigmxyz/reth#9137 for details.

Source builds without jemalloc will OOM on Linux

We've become aware of OOM issues for Lighthouse builds from source that disable the jemalloc feature on Linux. This is due to GNU malloc not handling the allocation of many tree nodes as well as other allocators (jemalloc, the Windows allocator). If you are building from source for Linux ensure that you include jemalloc in FEATURES (enabled by default). If you build the Dockerfile use --build-arg FEATURES=jemalloc (not enabled by default).

This will be addressed in v5.3.0 by an already-merged PR: #5995

Update Priority

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

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

See Update Priorities for more information about this table.

Lighthouse BNs and VCs from v5.0.0, v5.1.x and v5.2.x are compatible. However, we recommend that users update both the VC and BN to v5.2.1 if upgrading.

All changes

  • Release v5.2.1 (testing branch) (#5989)
  • Attempt to continue lookups after adding peers (#5993)
  • Remove all batches related to a peer on disconnect (#5969)
  • Update slasher DB size and Lighthouse book (#5934)
  • Ensure all handler events are covered (#5945)
  • report failed requests from RPC after being clear from rate limiter but not yet sent. (#5942)
  • Lower tolerance of stale blobs on gossip (#5935)
  • chore: simplify method to generate a random valid blob (#5946)
  • chore: change impl Into<T> for U to impl From<U> for T (#5948)
  • Update CI nethermind and LLVM versions (#5933)
  • Fix cargo audit: update curve25519-dalek (#5959)
  • Update local testnet documentation (#5896)
  • Fix SelfRateLimiter breaks the sequence of delayed_requests. (#5903)
  • Verify inclusion proof should not be fallible (#5787)
  • Remove extern crate (#5922)
  • Add FUNDING.json for DRIPS (#5932)
  • Fix CommandLineTest port conflicts on CI (#5908)
  • Remove some easy Electra TODOs (#5928)
  • Rust 1.79 lints (#5927)
  • Fix panic on startup in debug build (#5917)
  • Fix skip-ci on stable (#5909)
  • Beta compiler fixes (#5916)

See full changelog here.

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