Releases · sigp/lighthouse

25 May 09:44

github-actions

v2.3.0-rc.0

f4aa17e

Robobros Pre-release

Pre-release

🧑‍🔧 Release Candidate: Not for Production Use 🧑‍🔧

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

Whilst we do not recommend this release for critical and/or mainnet use, we would appreciate help testing this release on testnets.

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

Summary

This release candidate introduces support for the Ropsten Beacon Chain, among other changes.

The Ropsten Beacon Chain will launch on Monday, May 30th, 2022 3:00:00 PM +UTC. The long-standing Ropsten testnet is expected to undergo "the merge" in early June 2022. Any user that wishes to participate in the Ropsten merge must use this release candidate (or any following release).

Ropsten

Use the --network ropsten flag to join the Ropsten testnet.

Breaking Changes

❗ Database Schema Upgrade ❗

This release contains a backwards-incompatible database schema migration for any network that has undergone "the merge" (see #3157). At the time of writing, this includes Kiln and Kintsugi but excludes Prater and Mainnet. For clarity:

Prater, Mainnet: users who upgrade to v2.3.0-rc.0 are able to downgrade to v2.2.x and v2.1.x releases.
Kiln, Kinstugi: users who upgrade to v2.3.0-rc.0 are not able to downgrade to any prior release

All Changes

v2.3.0-rc.0 (#3218)
Avoid parallel fork choice runs during sync (#3217)
Document database migrations (#3203)
Decrease proposer boost to 40% (#3201)
Call per_slot_task from a blocking thread (v2) (#3199)
Remove build status badge from README (#3195)
Fix Rust 1.61 clippy lints (#3192)
Add Ropsten configuration (#3184)
Run fork choice before block proposal (#3168)
Log out response status when we hit PayloadIdUnavailable (#3190)
Tiny improvement: PeerManager and maximum discovery query (#3182)
Add client authentication to Web3Signer validators (#3170)
Avoid unnecessary slashing protection when publishing blocks (#3188)
Fix http header accept parsing problem (#3185)
Remove DB migrations for legacy database schemas (#3181)
Prevent attestation to future blocks from early attester cache (#3183)
Allow TaskExecutor to be used in async tests (#3178)
[refactor] Refactor Option/Result combinators (#3180)
Remove lcli block packing analysis (#3179)
Separate execution payloads in the DB (#3157)
Exclude EE build dirs from Docker context (#3174)
Add remotekey API support (#3162)
Fix: no version info in homebrew package (#3167)
Don't panic in forkchoiceUpdated handler (#3165)
Fix Execution Engine integration tests (#3163)
Change the url of the blog post (#3161)
Poll shutdown timeout in rpc handler (#3153)
log upgrades + prevent dialing of disconnecting peers (#3148)
Disallow attesting to optimistic head (#3140)
keep failed finalized chains to avoid retries (#3142)

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-v2.3.0-rc.0-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.3.0-rc.0-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.3.0-rc.0-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.3.0-rc.0-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.3.0-rc.0-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.3.0-rc.0-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.3.0-rc.0-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.3.0-rc.0-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.3.0-rc.0	sigp/lighthouse

Assets 18

12 Apr 06:32

github-actions

v2.2.1

aa72088

Talking Cat

Summary

This release fixes a bug in Lighthouse v2.2.0 that prevented some nodes from completing sync.

The majority of nodes running v2.2.0 will not have been affected by the bug, but nodes attempting to sync from genesis would get stuck at slot 0 forever, and nodes performing checkpoint sync would fail to download blocks from before the Altair hard fork (Oct 2021). The bug occurred as a result of changes made to RPC limits in preparation for the Merge, and has been fixed in PR #3146. Please see that pull request for more detail.

Users upgrading from v2.1 should also read the release notes for v2.2.0 to understand a new protocol feature called proposer boost which has been enabled in v2.2: https://github.com/sigp/lighthouse/releases/tag/v2.2.0

Backwards Compatibility

This release is fully backwards-compatible with the previous releases v2.2.0 and v2.1.x.

Downgrading from v2.2.1 to v2.1.x is also supported without any manual intervention.

Update Priority

This update is a Medium Priority update for users of Lighthouse v2.2.0, and a Low Priority update for v2.1.x.

User Class	Beacon Node	Validator Client
Staking Users	Low Priority*	Low Priority*
Non-Staking Users	Low Priority*	---

See Update Priorities for more information about this table.

All Changes

v2.2.1 (#3149)
Don't log crits for missing EE before Bellatrix (#3150)
Fix rpc limits version 2 (#3146)
Transition Block Proposer Preparation (#3088)
Fix SPRP default value in cli (#3145)
Ensure VALID response from fcU updates protoarray (#3126)
Add tests for importing blocks on invalid parents (#3123)

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-v2.2.1-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.1-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.1-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.1-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.2.1-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.2.1-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.1-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.1-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.2.1	sigp/lighthouse

Assets 18

05 Apr 07:10

github-actions

v2.2.0

bac7c3f

Balthromaw

Summary

This release includes a minor protocol upgrade named proposer boost, which is designed to mitigate several attacks against fork choice.

It is recommended that all users upgrade over the course of the next few weeks.

Proposer Boost

Background

Proposer boost mitigates attacks involving the delayed publishing of blocks and attestations. By creating disagreement amongst honest nodes, an attacker could frustrate consensus and cause re-orgs. For more detail on the attacks mitigated, please see Three Attacks on Proof-of-Stake Ethereum by researchers from the Ethereum Foundation and Stanford University.

Mitigation

Proposer boost mitigates the attacks by granting additional power to the proposer of each block, equal to 70% of the weight of the attesters in a single slot. This 70% "boost" is only granted to timely blocks, which prevents the delayed-publishing attack while also incentivizing on-time block publication in general. For more information please see the accompanying pull request to the beacon chain specification: ethereum/consensus-specs#2730.

Upgrade Strategy

By virtue of being a protocol change, proposer boost needs to be rolled out by a large fraction of the nodes on the network in order to be effective. This Lighthouse release is coordinated with forthcoming releases from the other consensus clients.

Although it's best for all nodes on the network to adopt proposer boost within a short time frame, we estimate that the impact of upgrades spaced over the course of a few weeks will be minimal. For more detailed analysis please see #3131.

In addition to theoretical analysis and unit testing, proposer boost has also undergone extensive testing on the Prater testnet, where it has been enabled for several months.

Other New Features

The beacon node and validator client HTTP APIs can now be hosted on IPv6 addresses (#3104).
The concurrency of request handling during sync was improved (#3036).
A command for manually inspecting the beacon node's database was added (#3129).
Lots of progress was made towards The Merge, including:
- Groundwork for MEV (#3062)
- Bugfixes (#3133, #3132, #3125, #3071).

Backwards Compatibility

This release is fully backwards-compatible with the previous release.

Downgrading from v2.2.0 to v2.1.x is also supported without any manual intervention.

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	---

See Update Priorities for more information about this table.

All Changes

v2.2.0 (#3139)
Update mdbook runner to Ubuntu 20.04 (#3138)
Update and consolidate dependencies (#3136)
Fix merge rpc length limits (#3133)
Conserve disk space by raising default SPRP (#3137)
Enable proposer boost on mainnet and GBC (#3131)
Strip newline from jwt secrets (#3132)
Add lighthouse db command (#3129)
Kiln mev boost (#3062)
json rpc id to value (#3110)
Increase timeouts for EEs (#3125)
Update engine state in broadcast (#3071)
Improve slashing import log (#3122)
Fix typos in docs (#3121)
Target geth master in integration testing (#3120)
Optionally skip RANDAO verification during block production (#3116)
Add merge objects to lcli parse-ssz subcommand (#3119)
feat: Update ASCII art (#3113)
Support IPv6 in BN and VC HTTP APIs (#3104)
Add Nethermind integration tests (#3100)
Remove sync await points (#3036)
Add Proposer Cache Pruning & POS Activated Banner (#3109)
Fix ganache windows CI attempt 2 (#3107)
Fix ganache in windows CI (#3105)
Correct typos book (#3099)
Updates to tests and local testnet for Ganache 7 (#3056)

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-v2.2.0-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.0-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.0-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.0-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.2.0-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.2.0-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.0-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.2.0-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.2.0	sigp/lighthouse

Assets 18

18 Mar 04:34

github-actions

v2.1.5

9bc9527

Hydrogen-F

Summary

This is a security-focussed release to address a denial-of-service vulnerability in OpenSSL (CVE-2022-0778).

Lighthouse does not rely on OpenSSL for any of its P2P functionality, but does make use of OpenSSL TLS when making HTTPS connections. We recommend that users upgrade to this release from v2.1.4 if they are using HTTPS URLs in their configuration and are concerned about the denial-of-service risk, see below for details.

OpenSSL Vulnerability Detail

If configured, Lighthouse will use HTTPS to connect to URLs passed to --eth1-endpoints, --checkpoint-sync-url or --beacon-nodes (from the validator client). These URLs typically correspond to servers trusted by the user, but still pose a denial-of-service risk if the connection is intercepted by an intermediary (e.g. an ISP or public hotspot router). We believe that attacks are unlikely to occur in practice, and that their impact would be relatively minor — lighthouse would hang, but there would be no slashing risk nor risk of signing keys being compromised.

For more information please see:

OpenSSL security advisory: https://www.openssl.org/news/secadv/20220315.txt
Lighthouse fix: #3095

Backwards Compatibility

Other than the OpenSSL fix, this release is functionally equivalent to the previous release, and is 100% backward compatible.

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	---

See Update Priorities for more information about this table.

All Changes

v2.1.5 (#3096)
Update openssl for CVE-2022-0778 (#3095)
Clarify proposers message is about current epoch (#3084)
Add minimum supported Rust version (#3082)

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-v2.1.5-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.5-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.5-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.5-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.5-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.5-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.5-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.5-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.1.5	sigp/lighthouse

Assets 18

15 Mar 06:20

github-actions

v2.1.4

98f7404

Magnesium-J

Summary

This release contains optimisations to P2P networking to improve validator performance. It also contains new functionality for The Merge and out-of-the-box support for the Kiln testnet via the --network kiln flag.

This release will increase the default peer count from 50 to 80. Users who don't specify a custom --target-peers value should see an increased peer count after updating. This is normal and expected.

Other notable features include:

Ignore non-routable IPs in discovery (#3023)
- See the "Breaking Changes" section for more details.
Removal of unnecessary error/warning logs related to sync committees (#2999, #3086)
Support for requesting proposer duties for the next epoch via the HTTP API (#2963)
Addition of an API to compute block packing efficiency (#2879)
Improved performance when a VC encounters timeout errors for a BN (#3022)
Addition of --validator-dir alias, to aid usability (#3034)
Fixes to missing quotes on integer values on the API (#3074, #3080)

Increased Peer Count

Ensuring peak performance on the P2P network frequently involves trade-offs between bandwidth usage and ensuring there is a diverse and useful set of peers. The trade-off space varies over time as the network increases in size and as different implementations evolve.

As described in this comment, increasing the default peer count from 50 to 80 has shown to provide significant benefits in peer management whilst making a less significant impact on network bandwidth.

The upside of this change is that we expect less "InsufficientPeers" errors, therefore reducing penalties caused by missed/late attestations or sync messages. The downside is that we expect users to notice a ~50% increase in bytes transmitted on the network and a ~15% increase in bytes recieved (mileage may vary).

Users who prefer minimal bandwidth are free to use --target-peers 50 and maintain the status-quo. That being said, we expect most users will be happy with the new default value of 80.

Breaking Changes

Discovery and Non-Routable IPs

In #3032, Lighthouse now ignores non-globally-routable IP addresses during discovery. This prevents some cloud providers (e.g., Hetzner) from banning Lighthouse under the (false) premise that it is maliciously scanning the private network.

We only expect this to impact developers running local testnets and enterprise users with sophisticated internal P2P routing. This change can be reverted by adding the --enable-private-discovery flag to the BN.

Kintsugi

The Kintsugi testnet is not supported by this release. Users should prefer Kiln.

VC and BN Update Procedure

The VC and BN between this release and the previous are compatible. You may update them independently.

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	---

See Update Priorities for more information about this table.

All Changes

v2.1.4 (#3076)
Ignore attestations to finalized blocks (don't reject) (#3052)
Lower debug! logs to trace! (#3053)
Rename random to prev_randao (#3040)
Custom RPC request management for sync (#3029)
Update libp2p (#3039)
Filter non global ips from discovery (#3023)
Rename Eth1/Eth2 in documents (#3021)
Increase default target-peer count to 80 (#3005)
Enforce Optimistic Sync Conditions & CLI Tests (v2) (#3050)
Cleanup small issues (#3027)
Retrospective invalidation of exec. payloads for opt. sync (#2837)
Update to Rust 1.59 and 2021 edition (#3038)
Ensure logfile respects the validators-dir CLI flag (#3003)
Add aliases for validator-dir flags (#3034)
Avoid hogging the fallback status lock in the VC (#3022)
Increase Bors timeout, refine target-branch-check (#3035)
Add API to compute block packing efficiency data (#2879)
Allow proposer duties request for the next epoch (#2963)
Fix sync committee polling for 0 validators (#2999)
Improved peer management (#2993)
Use SmallVec in Bitfield (#3025)
Engine API v1.0.0.alpha.6 + interop tests (#3024)
Update to consensus-specs v1.1.9 (#3016)
Update block reward API docs (#3013)

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-v2.1.4-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.4-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.4-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.4-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.4-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.4-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.4-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.4-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.1.4	sigp/lighthouse

Assets 18

11 Feb 05:43

github-actions

v2.1.3

c3a793f

Garbage Goober

Summary

This release addresses a bug in rust-libp2p which has been causing the Lighthouse networking stack to perform poorly since the v2.1.0 release.

This bug-fix significantly improves peer stability and is recommended for any user who is seeing an erratic peer-count and/or missing attestations due to InsufficientPeers.

Fix to `rust-libp2p`

Since the v2.1.0 release, users have been reporting issues with peer stability manifesting as missed attestations.

After months of developer hours investigating this issue and making peer stability improvements via other methods, we are relieved to have identified an obscure but impactful bug in rust-libp2p.

Whilst user feedback will be the ultimate indicator of success, we are confident that this release will represent a major improvement in peer stability.

Lighthouse relies on a regular "heartbeat" from rust-libp2p in order to perform many critical tasks. An unfortunate regression in rust-libp2p caused the heartbeat to become irregular and stretch from a 700ms interval to several minutes. We have raised this issue with the rust-libp2p developers who have been receptive and are working on a fix. To provide relief to our users, Lighthouse is using a Sigma Prime fork of rust-libp2p with a hot-fix applied.

Breaking Changes

The Pyrmont network is no longer natively supported by Lighthouse (#2543). This means that the --network pyrmont flag will no longer work.

Since the Pyrmont testnet is abandoned and in a state of disarray, we do not expect this to be of concern to our users. The Prater testnet has superseded the Pyrmont testnet.

Users can still opt to use the --testnet-dir flag to manually sync the Prymont network, if desired.

VC and BN Update Procedure

The VC and BN between this release and the previous are compatible. You may update them independently.

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	Low Priority
Non-Staking Users	Medium Priority	---

See Update Priorities for more information about this table.

All Changes

v2.1.3 (#3017)
Remove Pyrmont testnet (#2543)
libp2p upgrade + gossipsub interval fix (#3012)
Add "update priority" (#2988)
Allow per validator fee recipient via flag or file in validator client (similar to graffiti / graffiti-file) (#2924)
Bump crossbeam-utils to fix cargo-audit CI failure (#3004)
Fix Docker run -p for both TCP and UDP (#2998)
Gossip cache timeout adjustments (#2997)
Correct a dial race condition (#2992)
upgrade libp2p (#2933)
Retry gossipsub messages when insufficient peers (#2964)

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-v2.1.3-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.3-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.3-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.3-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.3-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.3-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.3-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.3-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.1.3	sigp/lighthouse

Assets 18

02 Feb 04:05

github-actions

v2.1.2

0177b92

Heistotron

Summary

This release significantly improves peer stability and is recommended for any user who is seeing an erratic peer-count and/or missing attestations due to InsufficientPeers.

In addition to peer stability improvements, this release also contains:

Eth2 Key Manager API support for the validator client (#2736)
Docker Hub images with CPU-optimized "modern" BLST (#2966)
Support for --network gnosis (#2931)

Peer Scoring Stability

There appears to be a significant portion of peers which are transmitting late messages on the p2p gossip network. The cause is yet to be determined and it's clear that more time will be required to investigate. The late messages are not likely to consume a significant amount of system or network resources, so it seems beneficial to network stability to temporarily tolerate peers who exhibit this behaviour (see (#2976). Once the cause(s) of the late messages is/are determined, we will revisit the peer-scoring parameters.

Optimized Docker Images

If you are running Lighthouse under Docker on a modern CPU then you can probably upgrade to the latest-modern tag for a 20-30% speed-up on signature verification.

If you are running the Lighthouse image manually, use latest-modern or v2.1.2-modern in your docker commands, e.g.

docker run sigp/lighthouse:latest-modern

If you are using lighthouse-docker then you can upgrade by setting LIGHTHOUSE_VERSION=latest-modern in your .env file.

To check whether your CPU is compatible with the optimized image, see Portability in the book. For more information on all the available images, see Available Docker Images.

VC and BN Update Procedure

The VC and BN between this release and the previous are compatible. You may update them independently.

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	Low Priority
Non-Staking Users	Low Priority	---

User 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

v2.1.2 (#2980)
Add checks to prevent fwding old messages (#2978)
Add strict penalties const bool (#2976)
Fix small typo in error log (#2975)
local testnet: Fix an error on startup (#2973)
Run setup.sh foreground in order to avoid timing issues (#2970)
Optimized Docker images (#2966)
Reduce gossip history (#2969)
Parse uint256 as decimal string (#2957)
Implement standard keystore API (#2736)
Native support for Gnosis Beacon Chain network (#2931)
Avoid looking up pre-finalization blocks (#2909)
Add API to compute discrete validator attestation performance (#2874)
Outaded flag in lighthouse book (#2965)
Implement API for block rewards (#2628)
Add flag to disable confirmation when performing voluntary exits (#2955)
Set mmap threshold to 128KB in malloc utils (#2937)
Code quality improvents to the network service (#2932)
Document why we hash downloaded blocks for both sync algs (#2927)
Fix errors from local testnet scripts on MacOS (#2919)

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-v2.1.2-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.2-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.2-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.2-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.2-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.2-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.2-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.2-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.1.2	sigp/lighthouse

Assets 18

25 Jan 03:57

github-actions

v2.1.1

5f628a7

Poñeta

Summary

This update addresses a bug that can cause missed attestations accompanied by a Could not publish message error: InsufficientPeers log. We recommend all users update to this release, at their convenience. Even users who are not affected by the bug immediately will likely experience it to some degree, eventually.

The bug fix is relevant to the BN and users are not strictly required to update the VC as well. However, we still recommend updating the VC to this version.

Notable changes include:

Fix for increased frequency of missed attestations accompanied by a Could not publish message error: InsufficientPeers log (#2948).
Compatibility between Lighthouse VCs and Nimbus beacon nodes (#2940, #2943, #2952).
Fix to HTTP query string parsing (#2908).

Known Issues

The validator client compatibility changes inadvertently introduced a bug that results in a panic when a Lighthouse v2.1.1 validator client (VC) connects to a Lighthouse beacon node (BN) of version v2.0.1 or earlier. If you update your beacon node(s) and validator client(s) to v2.1.1 then your setup will be unaffected, the panic will only occur if a beacon node is kept back on v2.0.1 or earlier. We have confirmed that Infura beacon nodes are also unaffected. For more information please see #2957.

Breaking Changes

There are no breaking changes between v2.1.0 and v2.1.1.

Users upgrading from a version prior to v2.1.0 should be sure to read the v2.1.0 release notes and understand the breaking changes involved.

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	Low Priority
Non-Staking Users	Low Priority	---

User Classes and Priorities

All Changes

5f628a7 v2.1.1 (#2951)
69288f6 VC: don't warn if BN config doesn't match exactly (#2952)
b9b3ea7 Fix metric name for monitoring (#2950)
ca29b58 Increase target subnet peers (#2948)
f35a337 Quote validator indices when posting duties (#2943)
799aedd Add default config options for transition constants (#2940)
f0f327a Removed all disable_forks (#2925)
fc7a1a7 Allow disconnected states to introduce new peers without warning (#2922)
a8ae9c8 Add linkcheck workflow (#2918)
0116c8d Change type of extra fields in ConfigAndPreset (#2913)
d06f874 Support duplicate keys in HTTP API query strings (#2908)

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-v2.1.1-x86_64-apple-darwin.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.1-x86_64-apple-darwin-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.1-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.1-x86_64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.1-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	lighthouse-v2.1.1-aarch64-unknown-linux-gnu-portable.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.1-x86_64-windows.tar.gz	PGP Signature
	x86_64	lighthouse-v2.1.1-x86_64-windows-portable.tar.gz	PGP Signature

System	Option	-	Resource
	Docker	v2.1.1	sigp/lighthouse

Assets 18

20 Jan 08:08

github-actions

v2.1.0

79db2d4

Diane Sanchez

Summary

This update provides significant optimisations and bug-fixes for mainnet users.
We recommend all users update to this release, at their convenience. Users
need to update both their Beacon Node (BN) and Validator Client (VC) when
updating.

Notable changes include:

Adds a mechanism to improve attestation performance during heavy disk I/O (#2872).
Improves cache performance during skip slots and late-blocks (#2849, #2832).
Fixes cases where peers are excessively penalized and disconnected, resulting in
sharp drops in peer counts (#2903, #2894).
Switches the slasher database to MDBX, resulting in a smaller disk footprint (#2776).
Changes default behaviour when using a relative --datadir (#2682, #2846).
Introduces support for running merge testnets (e.g. Kintsugi) (#2768).

Users should expect this release candidate to provide more stability, reduced resource consumption
and better validator performance.

Known Issues

Increased Memory Footprint

During testing, some nodes exhibited a temporarily increased beacon node memory
footprint of about 150% (~3GB) after upgrading from v2.0.1 to v2.1.0. The memory usage returns to normal after the first restart.

This increased footprint occurs during a recent database migration. The
migration causes memory fragmentation which increases the overall memory
footprint.

Users who observe an increased memory footprint can choose to restart their
beacon node to get the "normal" footprint again. Users who don't mind the
increased footprint can leave their node running with no harm.

Since the migration only happens once (i.e. the first time running v2.1.0 or
later) and the memory usage is within reasonable bounds, the developers have
opted to leave the migration as-is.

Teku/Infura Compatibility

Connecting a Lighthouse validator client to a Teku (or Infura) beacon node produces a warning:

WARN Beacon node config does not match exactly, advice: check that the BN is updated and configured for any upcoming forks

This is due to some minor differences in how the two clients serve data on the /config/spec endpoint when new hard forks are defined. The warning is cosmetic (if annoying), and the two clients will continue to function in its presence.

Breaking Changes

The VC from this release (v2.1.0) is not compatible with Lighthouse BNs from prior versions.
Users MUST update both Lighthouse BNs and VCs to v2.1.0.

New dependencies

Lighthouse now requires libclang when building from source. For details on the packages to install for different platforms please see the updated Building from Source section of the book.

❗ Database Schema Upgrade ❗

Some changes have been made to Lighthouse's database schema to support "the merge", proposer
boosting, and other optimisations. The database schema upgrade will be applied automatically upon
upgrading. Once a beacon node's database has been upgraded by Lighthouse v2.1.0 it will no longer be
compatible with any v2.0.x release, meaning that if you want to revert to a previous version of
Lighthouse you will have to re-sync. We anticipate that this will not be necessary, but Checkpoint
Sync is a good way to re-sync quickly if required.

Slasher Database Changed from LMDB to MDBX

The following section is relevant only to users running a slasher.

The slasher's underlying database has been upgraded to MDBX in
order to address disk usage issues with LMDB (#2538).
Combined with more efficient attestation storage, this should result in around 5-10x less disk space
being used over a long period.

The upgrade to MDBX will happen automatically and destructively upon running v2.1.0. Any previous
LMDB database will be deleted and replaced with a fresh MDBX database. We made the decision to
delete the database rather than copy it, in order to reduce complexity and to avoid running out of
space while copying hundreds of gigabytes of data. Although some LMDB slasher databases had
ballooned to 800GB+ they still only contained data from the last 18 days (4096 epochs) and will be
rebuilt to an equivalent smaller database after running the new release for 18 days.

If you are concerned about everyone upgrading at the same time you could choose to wait a random
number of days between 1 and 18 before upgrading. However we suspect that this is not necessary due
to the presence of Prysm slashers on the network, and the natural staggering of upgrades amongst
users.

Relative Paths in Data Directory

In this release, a bug with parsing the --datadir flag resulted in relative paths being relative
to the users home directory, rather than to the present working directory. This has been fixed in
#2682 and #2846.

Backwards compatibility is maintained by opening the path relative to the home directory, if it
exists. If that path does not exist, the path is assumed to be relative to the present working
directory.

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

All Changes

v2.1.0 (#2928)
Make /config/spec backwards compat for VC (#2934)
Update to spec v1.1.8 (#2893)
Use "release candidate" in book (#2920)
v2.1.0-rc.1
v2.1.0-rc.0
Remove grandparents from snapshot cache (#2917)
Lazy hashing for SignedBeaconBlock in sync (#2916)
PeerDB Status unknown bug fix (#2907)
Network performance tuning (#2608)
Remove gitter from readme (#2914)
Fix broken links in book (#2912)
Rust 1.58 lints (#2906)
Remove penalty for attesting to unknown head (#2903)
Antithesis docker workflow (#2877)
Add peer score adjustment msgs (#2901)
Avoid penalizing peers for delays during processing (#2894)
Skip serializing proposer boost if null (#2899)
Avoid peer penalties on internal errors for batch block import (#2898)
Update dependencies including sha2 (#2896)
Add early attester cache (#2872)
Document Homebrew package (#2885)
Adjusting ARCHIVE_URL (#2892)
Add tests for flags enable-enr-auto-update and disable-packet-filter (#2887)
Fix off-by-one in block packing lcli (#2878)
Allow value for beacon_node fee-recipient argument (#2884)
Use ? debug formatting for block roots in beacon_chain.rs (#2890)
Update to superstruct v0.4.1 (#2886)
Fix assert in slashing protection import (#2881)
Update rust version in lcli Dockerfile (#2876)
Only import blocks with valid execution payloads (#2869)
Additional networking metrics (#2549)
Allow to set validator password via reimport (#2868)
Optimise slasher DB layout and switch to MDBX (#2776)
Add configurable block replayer (#2863)
Unban peers at the swarm level when purged (#2855)
Minor Edit on Port Forward Reference (#2867)
Downgrade AttestationStateIsFinalized error to debug (#2866)
Enable mallinfo2 behind feature flag (#2864)
Update docker images to Ubuntu latest (#2862)
do not count dialing peers in the connection limit (#2856)
Update OpenSSL (#2865)
Optimise balances cache in case of skipped slots (#2849)
v1.1.6 Fork Choice changes (#2822)
Merge devnet 3 (#2859)
Update rusqlite from yanked version (#2861)
Remove wrong duplicated comment (#2751)
Optimise snapshot cache for late blocks (#2832)
fix cache miss justified balances calculation (#2852)
1.57.0 lints (#2850)
Restrict network limits based on merge fork epoch (#2839)
Remove duplicate slot_clock method (#2842)
Support legacy data directories (#2846)
Kintsugi Diva comments (#2836)
Cleanup Comments & Fix get_pow_block_hash_at_ttd() (#2835)
Kintsugi review comments (#2831)
Bump crate versions (#2829)
Removed PowBlock struct that never got used (#2813)
Kintsugi on_merge_block tests (#2811)
Increase network limits (#2796)
Ensure difficulty/hash/epoch overrides change the ChainSpec (#2798)
Implement engine API v1.0.0-alpha.4 (#2810)
Skip memory intensive engine test (#2809)
Fixes after rebasing Kintsugi onto unstable (#2799)
Remove old uses of testnet
Fix Uint256 deserialization (#2786)
1.1.5 merge spec tests (#2781)
Fix arbitrary check kintsugi (#2777)
Move merge-f2f docker to kintsugi (#2774)
Kintsugi rebase patches (#2769)
Accept TTD override as decimal (#2676)
v1.1.1 spec updates (#2684)
[Merge] Optimistic Sync: Stage 1 (#2686)
Fix db paths when datadir is relative (#2682)
[Merge] Optimistic EL verification (#2683)
[Merge] Block validator duties when EL is not ready (#2672)
Disable notifier logging from dummy eth1 backend (#2680)
Update lcli pubkey replace command (#2677)
Fixed bugs for m3 readiness (#2669)
Misc changes for merge testnets (#2667)
Add BeaconChainHarness tests for The Merge (#2661)
Disable autotests for beacon_chain (#2658)
Add merge fork_epoch and fork_version to Config (#2663)
add automated docker build for merge-f2f branch (#2654)
[Merge] Add execution API test vector...

Assets 18

17 Jan 06:09

github-actions

v2.1.0-rc.1

a836e18

Japheth Pre-release

Pre-release

🧑‍🔧 Release Candidate: Not for Production Use 🧑‍🔧

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

Whilst we do not recommend this release for critical and/or mainnet use, we would appreciate help testing this release on testnets.

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

Summary

Users need to update both their Beacon Node (BN) and Validator Client (VC) when updating.

Notable changes include:

Adds a mechanism to improve attestation performance during heavy disk I/O (#2872).
Improves cache performance during skip slots and late-blocks (#2849, #2832).
Fixes cases where peers are excessively penalized and disconnected, resulting in
sharp drops in peer counts (#2903, #2894).
Switches the slasher database to MDBX, resulting in a smaller disk footprint (#2776).
Changes default behaviour when using a relative --datadir (#2682, #2846).
Introduces support for running merge testnets (e.g. Kintsugi) (#2768).

Users should expect this release candidate to provide more stability, reduced resource consumption
and better validator performance.

Note: the v2.1.0-rc.0 version was not released due to CI failures. Use v2.1.0-rc.1 instead.

Breaking Changes

The VC from this release (v2.1.0-rc.1) is not compatible with Lighthouse BNs from prior versions.
Users MUST update both Lighthouse BNs and VCs to v2.1.0.

❗ Database Schema Upgrade ❗

Beacon Node API Changes

The GET eth/v1/config/spec endpoint has been modified to support new constants introduced in
Bellatrix (a.k.a. "the merge"). Since v2.1.0-rc.1, VCs will expect some Bellatrix constants to be
present in the spec endpoint. Using a v2.1.0-rc.1 VC with an earlier version BN will produce
errors logs similar to "missing field `TERMINAL_TOTAL_DIFFICULTY`".

Slasher Database Changed from LMDB to MDBX

The following section is relevant only to users running a slasher.

Relative Paths in Data Directory

All Changes

v2.1.0-rc.1
v2.1.0-rc.0
Remove grandparents from snapshot cache (#2917)
Lazy hashing for SignedBeaconBlock in sync (#2916)
PeerDB Status unknown bug fix (#2907)
Network performance tuning (#2608)
Remove gitter from readme (#2914)
Fix broken links in book (#2912)
Rust 1.58 lints (#2906)
Remove penalty for attesting to unknown head (#2903)
Antithesis docker workflow (#2877)
Add peer score adjustment msgs (#2901)
Avoid penalizing peers for delays during processing (#2894)
Skip serializing proposer boost if null (#2899)
Avoid peer penalties on internal errors for batch block import (#2898)
Update dependencies including sha2 (#2896)
Add early attester cache (#2872)
Document Homebrew package (#2885)
Adjusting ARCHIVE_URL (#2892)
Add tests for flags enable-enr-auto-update and disable-packet-filter (#2887)
Fix off-by-one in block packing lcli (#2878)
Allow value for beacon_node fee-recipient argument (#2884)
Use ? debug formatting for block roots in beacon_chain.rs (#2890)
Update to superstruct v0.4.1 (#2886)
Fix assert in slashing protection import (#2881)
Update rust version in lcli Dockerfile (#2876)
Only import blocks with valid execution payloads (#2869)
Additional networking metrics (#2549)
Allow to set validator password via reimport (#2868)
Optimise slasher DB layout and switch to MDBX (#2776)
Add configurable block replayer (#2863)
Unban peers at the swarm level when purged (#2855)
Minor Edit on Port Forward Reference (#2867)
Downgrade AttestationStateIsFinalized error to debug (#2866)
Enable mallinfo2 behind feature flag (#2864)
Update docker images to Ubuntu latest (#2862)
do not count dialing peers in the connection limit (#2856)
Update OpenSSL (#2865)
Optimise balances cache in case of skipped slots (#2849)
v1.1.6 Fork Choice changes (#2822)
Merge devnet 3 (#2859)
Update rusqlite from yanked version (#2861)
Remove wrong duplicated comment (#2751)
Optimise snapshot cache for late blocks (#2832)
fix cache miss justified balances calculation (#2852)
1.57.0 lints (#2850)
Restrict network limits based on merge fork epoch (#2839)
Remove duplicate slot_clock method (#2842)
Support legacy data directories (#2846)
Kintsugi Diva comments (#2836)
Cleanup Comments & Fix get_pow_block_hash_at_ttd() (#2835)
Kintsugi review comments (#2831)
Bump crate versions (#2829)
Removed PowBlock struct that never got used (#2813)
Kintsugi on_merge_block tests (#2811)
Increase network limits (#2796)
Ensure difficulty/hash/epoch overrides change the ChainSpec (#2798)
Implement engine API v1.0.0-alpha.4 (#2810)
Skip memory intensive engine test (#2809)
Fixes after rebasing Kintsugi onto unstable (#2799)
Remove old uses of testnet
Fix Uint256 deserialization (#2786)
1.1.5 merge spec tests (#2781)
Fix arbitrary check kintsugi (#2777)
Move merge-f2f docker to kintsugi (#2774)
Kintsugi rebase patches (#2769)
Accept TTD override as decimal (#2676)
v1.1.1 spec updates (#2684)
[Merge] Optimistic Sync: Stage 1 (#2686)
Fix db paths when datadir is relative (#2682)
[Merge] Optimistic EL verification (#2683)
[Merge] Block validator duties when EL is not ready (#2672)
Disable notifier logging from dummy eth1 backend (#2680)
Update lcli pubkey replace command (#2677)
Fixed bugs for m3 readiness (#2669)
Misc changes for merge testnets (#2667)
Add BeaconChainHarness tests for The Merge (#2661)
Disable autotests for beacon_chain (#2658)
Add merge fork_epoch and fork_version to Config (#2663)
add automated docker build for merge-f2f branch (#2654)
[Merge] Add execution API test vectors from Geth (#2651)
[Merge] Add serde impls for Transactions type (#2649)
[Merge] Implement execution_layer (#2635)
Finished Gossip Block Validation Conditions (#2640)
Fork boundary fix (#2646)
Store execution block hash in fork choice (#2643)
Update test vectors to v1.1.0 (#2642)
Handle merge fork in web3signer (#2631)
Update merge consensus to v1.1.0-beta.5 (#2630)
Fix clippy lints on merge-f2f (#2626)
Fix consensus, SSZ, tree hash & run merge EF tests (#2622)
Initial merge changes
Add background file logging (#2762)
Status'd Peer Not Found (#2761)
Correctly update range status when outdated chains are removed (#2827)
Allow additional subnet peers (#2823)
Revert peer DB changes from #2724 (#2828)
Use published ssz/tree_hash (#2825)
Ensure consistent log formatting (#2819)
Inform dialing via the behaviour (#2814)
Move peer db writes to eth2 libp2p (#2724)
Sync wrong dbg assertion (#2821)
Update Lighthouse Dependencies (#2818)
Fix decoding max length (#2816)
Investigate and correct RPC Response Timeouts (#2804)
Fix simulator issues (#2802)
Add a section on using infura as the checkpoint sync provider (#2797)
Add fork choice EF tests (#2737)
Add regression tests for boot_node (#2749)
Move the peer manager to be a behaviour (#2773)
De-duplicate attestations in the slasher (#2767)
Add minimum supported version for checkpoint sync in book (#2779)
Add cargo vendor test (#2076)
Peer manager cfg (#2766)
Do not compute metrics in the network service if the cli flag is not set (#2765)
Ensure dependent root consistency in head events (#2753)
Fix linting error on Windows (#2759)
Check proposer index during block production (#2740)
Add op pool metrics for attestations (#2758)
Update prometheus ...

Assets 18

Releases: sigp/lighthouse

Robobros

🧑‍🔧 Release Candidate: Not for Production Use 🧑‍🔧

Summary

Ropsten

Breaking Changes

❗ Database Schema Upgrade ❗

All Changes

Binaries

Talking Cat

Summary

Backwards Compatibility

Update Priority

All Changes

Binaries

Balthromaw

Summary

Proposer Boost

Background

Mitigation

Upgrade Strategy

Other New Features

Backwards Compatibility

Update Priority

All Changes

Binaries

Hydrogen-F

Summary

OpenSSL Vulnerability Detail

Backwards Compatibility

Update Priority

All Changes

Binaries

Magnesium-J

Summary

Increased Peer Count

Breaking Changes

Discovery and Non-Routable IPs

Kintsugi

VC and BN Update Procedure

Update Priority

All Changes

Binaries

Garbage Goober

Summary

Fix to rust-libp2p

Breaking Changes

VC and BN Update Procedure

Update Priority

All Changes

Binaries

Heistotron

Summary

Peer Scoring Stability

Optimized Docker Images

VC and BN Update Procedure

Update Priority

User Classes and Priorities

All Changes

Binaries

Poñeta

Summary

Known Issues

Breaking Changes

Update Priority

User Classes and Priorities

All Changes

Binaries

Diane Sanchez

Summary

Known Issues

Increased Memory Footprint

Teku/Infura Compatibility

Breaking Changes

New dependencies

❗ Database Schema Upgrade ❗

Slasher Database Changed from LMDB to MDBX

Relative Paths in Data Directory

Update Priority

Users Classes and Priorities

Fix to `rust-libp2p`