stakestack
UTC
GitHub

Lighthouse

Sigma Prime · Rust · Apache-2.0

Rust consensus client with beacon node and validator client binaries.

consensusvalidatorEthereum MainnetHoodiSepoliaHoleskyEphemery
sigp/lighthouseDocsWebsitesigp/lighthouse

Required by network upgrades

UpgradeNetworkMinimum
GlamsterdamSepolia≥ 8.3.0-rc.0
FusakaEthereum Mainnet≥ 8.0.1

Releases

Rated by the lighthouse-table rules · weight 1.5
Channel
Severity
Type
Network
Fork
34 releases
Lighthousev8.3.2
Why this rating
  • high (hoodi): Staking Users (Hoodi) | High | High
  • high (mainnet): Staking Users (mainnet & other networks) | Not required | Not required
  • high (hoodi): All Hoodi users must upgrade to v8.3.2 before 26 October 2026 at 17:42:48 UTC, the previously scheduled activation time (epoch 132352).
  • high (all networks): Staking users must update their beacon node, validator client and execution client.
  • fork scheduled (hoodi): This release disables the scheduled Gloas fork on Hoodi.
Oct 23, 2026
Lighthousev8.4.0-rc.0
Why this rating
  • low (all networks): Staking Users | Low | Low
Oct 22, 2026
Lighthousev8.3.1
Why this rating
  • high (all networks): Staking Users | High | High
  • high (all networks): This high-priority release updates Lighthouse's trusted certificates to mitigate the compromised eMudhra certificate authority.
  • high (hoodi): As a reminder: all Hoodi users must upgrade to v8.3.x prior to Monday 26 Oct 2026.
  • high (all networks): All Lighthouse users on all networks should upgrade as soon as practical.
Oct 22, 2026
Lighthousev8.3.0
Why this rating
  • high (hoodi, sepolia): Staking Users (Hoodi & Sepolia) | High | High
  • high (mainnet): Staking Users (mainnet & other networks) | High | Medium
  • high (hoodi): Hoodi operators must upgrade before 26 October 2026 at 17:42:48 UTC.
  • fork scheduled (hoodi): This release includes the fork epoch for Hoodi's Gloas upgrade, the consensus-layer half of Glamsterdam, paired with Amsterdam on the execution layer.
  • fork scheduled (hoodi, sepolia): On Hoodi (as on Sepolia), the scheduled default becomes 200 million gas at Gloas.
Oct 19, 2026
Lighthousev8.3.0-rc.0
Why this rating
  • high (sepolia): Staking Users (Sepolia) | High | High
  • high (sepolia): Sepolia operators must upgrade before 6 October 2026 at 13:53:36 UTC.
  • fork scheduled (sepolia): On Sepolia, the scheduled default becomes 200 million gas at Gloas.
  • low (all networks): Staking Users (other networks) | Low | Low
  • performance wording: "This release completes the associated block-production and builder workflows, including external builder bid selection, payload timeliness committee duties, optimistic sync, and h…"
Oct 1, 2026
Lighthousev8.2.3
Why this rating
  • medium (all networks): Staking Users | Medium | Low
  • medium (all networks); medium (mainnet): This medium-priority release contains fixes for security vulnerabilities and is recommended for all mainnet users.
  • security wording: "This medium-priority release contains fixes for security vulnerabilities and is recommended for all mainnet users."
  • Security: We can now reveal the vulnerabilities that were patched: - quinn-udp: - quinn-proto: - quinn-proto:
Oct 1, 2026
Lighthousev8.2.2
Why this rating
  • high (all networks): Staking Users | High | Low
  • high (all networks): Lighthouse v8.2.2 is a high-priority release containing fixes for several security vulnerabilities.
  • high (mainnet): All mainnet beacon node users should upgrade as soon as practical to receive the security fixes in this release.
  • security wording: "Lighthouse v8.2.2 is a high-priority release containing fixes for several security vulnerabilities."
  • Security: This section will be updated with security advisories as they are made public. We are not disclosing the security content of this release in order to give user…
Aug 18, 2026
Lighthousev8.2.1
Why this rating
  • high (all networks): Staking Users | High | Low
  • high (all networks): Lighthouse v8.2.1 is a high-priority release containing fixes for several security vulnerabilities, as well as fixes and optimisations.
  • high (mainnet): All mainnet beacon node users should upgrade as soon as practical to receive the security fixes in this release.
  • medium (hoodi, sepolia): Users running Lighthouse on Hoodi or Sepolia are encouraged to upgrade to benefit from these fixes.
  • security wording: "Lighthouse v8.2.1 is a high-priority release containing fixes for several security vulnerabilities, as well as fixes and optimisations."
Jul 21, 2026
Lighthousev8.2.0
Why this rating
  • high (all networks): Staking Users | High | Low
  • high (all networks): Lighthouse v8.2.0 is a high-priority release containing fixes for several security vulnerabilities, as well as optimisations and new features.
  • high (all networks): - Mandatory fee recipient: Validator clients now refuse to startup when an enabled validator has no suggested_fee_recipient field in validator_definitions.yml and no global --suggested-fee-recipient …
  • high (all networks): All beacon node users should upgrade as soon as practical.
  • security wording: "Lighthouse v8.2.0 is a high-priority release containing fixes for several security vulnerabilities, as well as optimisations and new features."
Jun 22, 2026
Lighthousev8.1.3
Why this rating
  • high (all networks): Staking Users | High | High for Gnosis, Low otherwise
  • high (all networks): Lighthouse v8.1.3 is a high-priority patch release with further security-critical fixes atop v8.1.2.
  • high (all networks): This is a mandatory upgrade for all users running any prior version.
  • high (all networks): All Lighthouse beacon nodes should be upgraded as soon as possible.
  • high (all networks): All users running prior versions of Lighthouse BN should upgrade immediately.
Mar 26, 2026
Lighthousev8.1.2
Why this rating
  • high (all networks): Staking Users | High | Low
  • high (all networks): Lighthouse v8.1.2 is a high-priority patch release with further security-critical fixes atop v8.1.1.
  • high (all networks): This is a mandatory upgrade for all users running any prior version.
  • high (all networks): All Lighthouse beacon nodes should be upgraded as soon as possible.
  • high (all networks): All users running prior versions of Lighthouse BN should upgrade immediately.
Mar 9, 2026
Lighthousev8.1.1
Why this rating
  • high (all networks): Staking Users | High | High
  • high (all networks): This is a mandatory upgrade for all users running any prior versions.
  • high (all networks): Users should upgrade as soon as possible.
  • high (all networks): All users running prior versions of Lighthouse should upgrade immediately.
  • security wording: "Lighthouse v8.1.1 is a patch release that includes an important security fix, along with several networking and validator client bug fixes, sync observability metrics, and depende…"
Feb 27, 2026
Lighthousev8.1.0
Why this rating
  • medium (all networks): Staking Users | Medium | Medium
  • medium (all networks): This is a recommended upgrade for users experiencing performance issues, particularly those running large numbers of validators.
  • consensus-safety wording: "This fixes slashing protection database timeouts for users running large numbers of validators under heavy disk congestion."
  • performance wording: "Lighthouse v8.1.0 includes performance optimizations, validator client improvements, and bug fixes."
Feb 5, 2026
Lighthousev8.0.1
Why this rating
  • high (mainnet): As a reminder, all mainnet users must upgrade to either v8.0.0 or v8.0.1 prior to the Fulu fork at epoch 411,392 (2025-12-03, 21:49 UTC).
  • high (all networks): You must also update your execution client (e.g.
  • fork scheduled (mainnet): As a reminder, all mainnet users must upgrade to either v8.0.0 or v8.0.1 prior to the Fulu fork at epoch 411,392 (2025-12-03, 21:49 UTC).
  • medium (all networks): Staking Users | Medium | Low
  • hotfix wording: "This is a hotfix release addressing several bugs and performance issues discovered in v8.0.0."
Nov 20, 2025
Lighthousev8.0.0
Why this rating
  • high (all networks): Staking Users | High | High
  • high (mainnet): Upgrading to v8.0.0 is mandatory for all mainnet users prior to the Fulu fork at epoch 411,392 (2025-12-03, 21:49 UTC).
  • fork scheduled (mainnet): This release includes the mainnet fork epoch for the upcoming Fulu-Osaka (Fusaka) fork and subsequent blob-parameter-only (BPO) forks. 🎉
  • fork scheduled (mainnet): Upgrading to v8.0.0 is mandatory for all mainnet users prior to the Fulu fork at epoch 411,392 (2025-12-03, 21:49 UTC).
  • breaking wording: "- Add release helper script to list PRs and breaking changes (#7737)"
Nov 4, 2025
Lighthousev8.0.0-rc.2
Why this rating
  • high (all networks): Staking Users (testnet) | High | High
  • high (hoodi): Upgrading to v8.0.0-rc.2 or any earlier v8.0.0-rc.x version is mandatory prior to the Fulu forks on Hoodi:
  • fork scheduled (mainnet): We strongly recommend users already running earlier v8.0.0-rc.x versions on testnets to upgrade, as this release fixes a peer disconnection regression introduced in v8.0.0-rc.1 and it will help us te…
  • medium (mainnet): We strongly recommend users already running earlier v8.0.0-rc.x versions on testnets to upgrade, as this release fixes a peer disconnection regression introduced in v8.0.0-rc.1 and it will help us te…
  • medium (mainnet): This release is not recommended for mainnet, although mainnet users experiencing memory leaks are encouraged to upgrade to v8.0.0-rc.0 (not this rc.2).
Oct 23, 2025
Lighthousev8.0.0-rc.1
Why this rating
  • high (all networks): Staking Users (testnet) | High | High
  • high (hoodi, sepolia): Upgrading to v8.0.0-rc.1 or the previously released v8.0.0-rc.0 is mandatory prior to the Fulu forks on Sepolia and Hoodi:
  • high (all networks): If you build Lighthouse from source you need to upgrade your Rust compiler to v1.88.0 or later.
  • medium (mainnet): Users already running v8.0.0-rc.0 on testnets are encouraged to upgrade to help us test prior to the mainnet fork.
  • medium (mainnet): This release is not recommended for mainnet, although mainnet users experiencing memory leaks are encouraged to upgrade to v8.0.0-rc.0.
Oct 13, 2025
Lighthousev8.0.0-rc.0
Why this rating
  • high (all networks): Staking Users (testnet) | High | High
  • high (all networks): It is a required upgrade for the upcoming Fusaka hard forks on these testnets.
  • high (mainnet): However, the Fusaka upgrade has not yet been scheduled on mainnet, so mainnet users who choose to upgrade will still need to upgrade again to the official v8.0.0 mainnet release (scheduled for Novemb…
  • high (all networks): If you build Lighthouse from source you need to upgrade your Rust compiler to v1.88.0 or later.
  • breaking wording: "- Add release helper script to list PRs and breaking changes (#7737)"
Sep 29, 2025
Lighthousev7.1.0
Why this rating
  • Breaking changes: Upgrading to Lighthouse v7.1.0 should require no manual intervention for most users (aside from updating the binary/Docker image). However, some CLI flags have…
  • low (all networks): Staking Users | Low | Low
  • low (all networks): Lighthouse v7.1.0 is a low-priority maintenance release containing several optimisations and new features.
  • deprecation wording: "- Deprecated CLI flags"
  • performance wording: "Lighthouse v7.1.0 is a low-priority maintenance release containing several optimisations and new features."
Jul 10, 2025
Lighthousev7.0.1
Why this rating
  • high (mainnet): Mainnet Users | High | High
  • high (mainnet): As a reminder, all mainnet users must upgrade to either v7.0.1 or v7.0.0 by the time of the fork on 7 May 2025.
  • high (all networks): You must also update your execution client (e.g.
  • high (mainnet): Mainnet users must upgrade before the Electra fork.
  • fork scheduled (mainnet): This release includes the fork epoch for Electra on Mainnet
Apr 30, 2025
Lighthousev7.0.0
Why this rating
  • high (mainnet): All mainnet users must upgrade to v7.0.0 by the time of the fork on 7 May 2025.
  • high (all networks): You must also update your execution client (see compatible versions below).
  • high (mainnet): Mainnet users must upgrade before the Electra fork.
  • fork scheduled (mainnet): This releases includes the fork epoch for Electra on Mainnet
  • medium (mainnet): Mainnet Users | Medium | Medium
Apr 22, 2025
Lighthousev7.0.0-beta.7
Why this rating
  • high (all networks): Testnet Users | High | Low
  • fork scheduled (mainnet): - Mainnet Electra fork epoch (#7275)
  • medium (all networks): Users on these networks should update at their earliest convenience.
  • hotfix wording: "This release is a hotfix release for Electra-enabled test networks: Sepolia, Holesky, Hoodi and Chiado."
Apr 17, 2025
Lighthousev7.0.0-beta.5
Why this rating
  • high (all networks): Testnet Users | High | Low
  • high (hoodi, sepolia, holesky): This is a high-priority bugfix release for all Electra testnets: Sepolia, Holesky, Hoodi and Chiado.
  • high (all networks): You should update to this release as soon as possible, especially if you are running a large number of validators on one of these networks.
  • Breaking changes: There are no breaking changes in this release.
Mar 27, 2025
Lighthousev7.0.0-beta.4
Why this rating
  • medium (all networks): This release contains a bug and we strongly recommend upgrading to v7.0.0-beta.5.
  • medium (hoodi, sepolia, holesky): It is recommended for all testnets: Sepolia, Holesky, Hoodi and Chiado (Gnosis testnet).
  • medium (all networks): This release contains a bug and we recommend upgrading to v7.0.0-beta.5.
  • Breaking changes: There are no breaking changes introduced by this release.
  • low (all networks): Testnet Users | Low | Low
Mar 20, 2025
Lighthousev7.0.0-beta.3
Why this rating
  • hotfix wording: "This is another hotfix for Holesky fixing a bug introduced in v7.0.0-beta.2."
Mar 13, 2025
Lighthousev7.0.0-beta.2
Why this rating
  • high (all networks): Staking Users (testnet) | High | High
  • Breaking changes: You should only upgrade to v7.0.0-beta.2 from v7.0.0-beta.{0,1} on Holesky. This release contains no breaking changes compared to v7.0.0-beta.1. Please see the…
  • hotfix wording: "This is a second hot-fix release for the unsuccessful Electra upgrade on Holesky in February 2025."
  • performance wording: "It contains patches to help reduce memory usage during non-finality, and to help nodes sync."
Mar 4, 2025
Lighthousev7.0.0-beta.1
Why this rating
  • high (all networks): Staking Users | High (Holesky only) | High (Holesky only)
  • consensus-safety wording: "- Blacklist invalid block root in block verification and blacklist invalid finalized epochs in sync."
  • hotfix wording: "This is a hot-fix release for the unsuccessful Electra upgrade on Holesky in February 2025."
Feb 26, 2025
Lighthousev7.0.0-beta.0
Why this rating
  • high (all networks): Staking Users (testnet) | High | High
  • high (sepolia, holesky): This beta release is high-priority for users on Holesky and Sepolia.
  • high (all networks): It is a required upgrade for the upcoming Electra hard forks on these testnets.
  • high (all networks): If you are running Lighthouse on a testnet, you must also upgrade your execution layer client to a Prague-Electra (_Pectra_) compatible release.
  • high (sepolia, holesky): Holesky and Sepolia users must upgrade before the Electra fork.
Feb 13, 2025
Lighthousev6.0.1
Why this rating
  • Breaking changes: Upgrading to Lighthouse v6.0.x should be automatic for most users, but you must: - Remove any unsupported CLI flags (see below), and - Be aware of the one-way …
  • low (all networks): Staking Users | Low | Low
  • low (all networks): This low-priority patch release fixes a few minor issues in the recent major release v6.0.0.
  • deprecation wording: "- Removal and deprecation of several old CLI flags."
  • performance wording: "Lighthouse v6.0.x includes new features and optimisations which are backwards-incompatible with Lighthouse v5.x.y."
Dec 16, 2024
Lighthousev6.0.0
Why this rating
  • Breaking changes: Upgrading to Lighthouse v6.0.0 should be automatic for most users, but you must: - Remove any unsupported CLI flags (see below), and - Be aware of the one-way …
  • low (all networks): Staking Users | Low | Low
  • low (all networks): This low-priority major release introduces new features and optimisations which are backwards-incompatible with Lighthouse v5.x.y.
  • deprecation wording: "- Removal and deprecation of several old CLI flags."
  • performance wording: "This low-priority major release introduces new features and optimisations which are backwards-incompatible with Lighthouse v5.x.y."
Dec 2, 2024
Lighthousev5.3.0
Why this rating
  • medium (all networks): Staking Users | Medium | Medium
  • medium (all networks): This medium-priority release contains performance optimisations, bugfixes and new features.
  • breaking wording: "There are several breaking changes detailed below."
  • deprecation wording: "- --builder-profit-threshold: This flag was already deprecated and has been incompatible since v5.2.0 ("
  • performance wording: "This medium-priority release contains performance optimisations, bugfixes and new features."
Aug 8, 2024
Lighthousev5.2.1
Why this rating
  • medium (all networks): Staking Users | Medium | Low
  • medium (all networks): This medium-priority release contains bugfixes for issues identified in v5.2.0.
  • medium (all networks): Users who have experienced sync issues with v5.2.0 are recommended to upgrade.
  • medium (all networks): We recommend upgrading Nethermind to v1.27.0.
  • 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.
Jun 28, 2024
Lighthousev5.2.0
Why this rating
  • medium (all networks): Staking Users | Medium | Medium
  • medium (all networks): This medium-priority release contains a major improvement to how states are managed in memory (tree-states) and an optimised epoch and block processing implementation.
  • Breaking changes: Several breaking changes have been made to CLI flags as part of a cleanup and modernisation effort. Please make sure to remove or update these flags as part of…
  • deprecation wording: "The validator client --latency-measurement-service flag is now deprecated in favour of --disable-latency-measurement-service."
  • performance wording: "This medium-priority release contains a major improvement to how states are managed in memory (tree-states) and an optimised epoch and block processing implementation."
Jun 11, 2024
Lighthousev5.1.3
Why this rating
  • medium (all networks): Staking Users | Medium | Medium
  • medium (all networks): This is a medium priority release.
  • medium (all networks): We recommend that all users upgrade at their convenience.
  • medium (all networks): We particularly recommend upgrading if you are seeing either of these logs:
  • hotfix wording: "This hotfix release includes several bug fixes related to the handling of blobs."
Mar 28, 2024