stakestack
UTC
GitHub

Prysm

Offchain Labs · Go · GPL-3.0

Go consensus client; beacon-chain and validator binaries.

consensusvalidatorEthereum MainnetHoodiSepoliaHolesky
OffchainLabs/prysmDocsWebsitegcr.io/offchainlabs/prysm/beacon-chain

Repository moved from prysmaticlabs/prysm to OffchainLabs/prysm; old URLs redirect.

Required by network upgrades

UpgradeNetworkMinimum
GlamsterdamSepolia≥ 7.2.1
FusakaEthereum Mainnet≥ 7.0.0

Releases

Rated by the prysm-notes rules · weight 1.5
Channel
Severity
Type
Network
Fork
32 releases
Prysmv7.3.1
Oct 22, 2026
Prysmv7.3.0
Why this rating
  • high (hoodi): Hoodi operators must update their beacon nodes and validator clients before then.
  • high (all networks): On networks that have forked into Gloas, beacon nodes and validator clients must be upgraded together.
  • medium (mainnet): We recommend that mainnet operators update their beacon nodes to this release as soon as possible.
  • consensus-safety wording: "Before, graffiti from proposer settings or the keymanager API that was not 32 bytes caused a 400 and a missed proposal."
  • deprecation wording: "- --dev, --holesky, the terminal total difficulty and block hash override flags, and several flag aliases are deprecated."
Oct 16, 2026
Prysmv7.2.1
Why this rating
  • fork readiness: "- Added support for Gloas Partial Columns."
  • deprecation wording: "To fall back to full column gossip, use --disable-partial-data-columns. --partial-data-columns is deprecated and has no effect."
  • performance wording: "- Use EL validation instead of forkchoice for optimistic status of incoming payload."
Oct 5, 2026
Prysmv7.2.0
Why this rating
  • high (sepolia): Sepolia operators are required to update to v7.2.0 before the fork, and must also run an execution client that supports the corresponding Amsterdam fork on Sepolia.
  • fork scheduled (sepolia): This release schedules the Gloas fork on the Sepolia testnet at epoch 353024 (October 6, 2026, 13:53:36 UTC).
  • fork scheduled (sepolia): - Gloas fork scheduled on Sepolia at epoch 353024 (October 6, 2026, 13:53:36 UTC).
  • medium (mainnet, hoodi): Gloas is not yet scheduled for Hoodi or mainnet; operators of those networks are encouraged to update per their regular update cadence.
  • consensus-safety wording: "- Fix the minimal slashing protection database decoding unset builder settings fields as explicit zero values; both validator DB backends now read the same stored settings identic…"
Sep 28, 2026
Prysmv7.1.8
Why this rating
  • medium (all networks): This is a highly recommended patch release containing multiple bug fixes improving the handling of early attestations for better inclusion.
Jul 29, 2026
Prysmv7.1.7
Why this rating
  • deprecation wording: "- REST Validator client now subscribes to the head_v2 beacon API event by default instead of the deprecated head event."
Jul 13, 2026
Prysmv7.1.6
Why this rating
  • high (all networks): Operators are encouraged to update to this release as soon as practical.
  • consensus-safety wording: "- Move peer-scoring of invalid block signatures to the gossip caller."
  • deprecation wording: "- v1 proposer settings files remain supported without modification: a deprecation warning is logged on gloas-scheduled networks and settings are upgraded automatically in the vali…"
  • performance wording: "This patch release contains targeted gossip-validation, sync, and operator-facing improvements, alongside continued Gloas (ePBS), PeerDAS/data-column, builder API, and performance…"
Jul 1, 2026
Prysmv7.1.5
Why this rating
  • performance wording: "This release is dominated by Gloas (ePBS) fork development, alongside broad performance and memory optimizations, additional Beacon API event and endpoint support, and a round of …"
Jun 17, 2026
Prysmv7.1.4
Why this rating
  • consensus-safety wording: "- Missed attestation fix: Newly-activated validators no longer miss their first attestation when using --enable-beacon-rest-api (#16723)."
  • performance wording: "This is a maintenance release with significant progress on the Gloas implementation alongside important production fixes and performance improvements."
May 22, 2026
Prysmv7.1.3
Why this rating
  • medium (all networks): Operators are encouraged to update at their convenience.
  • security wording: "A security update to go-ethereum v1.16.8 is also included."
  • Security: - Update go-ethereum to v1.16.8. [[PR]](
  • performance wording: "This release brings extensive Gloas (next fork) groundwork, a major logging infrastructure overhaul, and numerous performance optimizations across the beacon chain."
Mar 18, 2026
Prysmv7.1.2
Jan 7, 2026
Prysmv7.1.2-rc.0
Dec 22, 2025
Prysmv7.1.1
Why this rating
  • performance wording: "- Optimise migratetocold by not doing brute force for loop."
Dec 18, 2025
Prysmv7.1.0
Why this rating
  • deprecation wording: "If you are running v7.0.0 then you should update to v7.0.1 or later and remove the flag --disable-last-epoch-targets."
Dec 10, 2025
Prysmv7.0.1
Why this rating
  • high (all networks): Operators are encouraged to update to this release as soon as practical.
  • deprecation wording: "As of this release, the feature flag --disable-last-epoch-targets has been deprecated and can be safely removed from your node configuration."
Dec 8, 2025
Prysmv7.0.0
Why this rating
  • high (all networks): All operators MUST update to v7.0.0 or later release prior to the fulu fork epoch 411392.
  • fork scheduled (mainnet): - Fulu fork epoch for mainnet configurations set for December 3, 2025, 09:49:11pm UTC.
  • deprecation wording: "- Several deprecated flags have been deleted!"
Nov 10, 2025
Prysmv6.1.4
Oct 28, 2025
Prysmv6.1.3
Oct 21, 2025
Prysmv6.1.2
Why this rating
  • high (mainnet): All node operators are encouraged to update to this release as soon as practical for the best mainnet performance.
  • performance wording: "All node operators are encouraged to update to this release as soon as practical for the best mainnet performance."
Oct 10, 2025
Prysmv6.1.1
Why this rating
  • high (all networks): Testnet operators are required to update prior to the testnet fork date.
  • high (all networks): _Important note: All operators should upgrade as soon as possible to v6.0.5 OR v6.1.0 to receive a critical stability patch. v6.0.5 only includes the stability fix on top of v6.0.4, whereas v6.1.0 in…
  • medium (mainnet): Mainnet operators are encouraged to update per their regular update cadence.
  • security wording: "- Updated distroless/cc-debian11 to latest to resolve CVE-2024-2961."
  • Security: - Updated go to version 1.24.5. [[PR]]( - Updated distroless/cc-debian11 to latest to resolve CVE-2024-2961. [[PR]]( - Updated go to version 1.24.6. [[PR]]( - …
Sep 29, 2025
Prysmv6.1.0
Why this rating
  • high (all networks): Testnet operators are required to update prior to the testnet fork date.
  • high (all networks): _Important note: All operators should upgrade as soon as possible to v6.0.5 OR v6.1.0 to receive a critical stability patch. v6.0.5 only includes the stability fix on top of v6.0.4, whereas v6.1.0 in…
  • medium (mainnet): Mainnet operators are encouraged to update per their regular update cadence.
  • security wording: "- Updated distroless/cc-debian11 to latest to resolve CVE-2024-2961."
  • Security: - Updated go to version 1.24.5. [[PR]]( - Updated distroless/cc-debian11 to latest to resolve CVE-2024-2961. [[PR]]( - Updated go to version 1.24.6. [[PR]]( - …
Sep 26, 2025
Prysmv6.0.5
Why this rating
  • high (all networks): All operators should update as soon as possible to v6.0.5 or later.
  • Security: - Updated quic-go to latest version. [[PR]](
Sep 26, 2025
Prysmv6.0.4
Why this rating
  • consensus-safety wording: "- A fix for slashing protection history exports where the validator database was in a nested folder."
Jun 6, 2025
Prysmv6.0.3
Why this rating
  • medium (all networks): Operators are encouraged to update at their own convenience.
May 21, 2025
Prysmv6.0.2
Why this rating
  • fork readiness: "Most importantly, we have adjusted the index limit for field tries in the beacon state to better support Pectra states."
  • performance wording: "- Enable light client gossip for optimistic and finality updates."
May 12, 2025
Prysmv6.0.1
Why this rating
  • high (all networks): If you are using or planning to use this endpoint, upgrading to version 6.0.1 is mandatory.
  • security wording: "- Fix CVE-2025-22869."
  • Security: - Fix CVE-2025-22869. [[PR]]( - Fix CVE-2025-22870. [[PR]]( - Fix CVE-2025-22872. [[PR]]( - Fix CVE-2025-30204. [[PR]](
  • deprecation wording: "As you may have noticed, we put a deprecation notice on our gRPC code, in particular on gRPC-related flags."
May 2, 2025
Prysmv6.0.0
Why this rating
  • high (all networks): You MUST update Prysm Beacon Node, Prysm Validator Client, and your execution layer client to the Pectra ready release prior to the fork to stay on the correct chain.
  • high (all networks): This release is mandatory for all operators before May 7.
  • high (all networks): Please review the changelog below and update your client as soon as practical before May 7.
  • fork scheduled (mainnet): The fork is scheduled for mainnet epoch 364032 (May 7, 2025, 10:05:11 UTC).
  • deprecation wording: "- Deprecated everything related with the gRPC API."
Apr 21, 2025
Prysmv5.3.2
Why this rating
  • high (all networks): Testnet operators are required to update to this release.
  • medium (mainnet): Mainnet operators are recommended to update to this release at their regular cadence.
  • performance wording: "- cosmetic fix for calling /prysm/validators/performance when connecting to non prysm beacon nodes and removing the 404 error log."
Mar 25, 2025
Prysmv5.3.1
Why this rating
  • medium (all networks): Testnet operators are strongly encouraged to update to this release.
  • medium (all networks): Mainner operators are recommended to update to this release at their regular cadence.
  • breaking wording: "This should not be a breaking change."
  • deprecation wording: "- Fixed use of deprecated rand.Seed."
  • performance wording: "- Add SSZ support to light client finality and optimistic APIs."
Mar 13, 2025
Prysmv5.3.0
Why this rating
  • high (sepolia, holesky); medium (mainnet): Updating to this release is required for Holesky and Sepolia operators and it is recommended for mainnet users as there are a few bug fixes that apply to deneb logic.
  • security wording: "- go version upgrade to 1.22.10 for CVE CVE-2024-34156."
  • Security: - go version upgrade to 1.22.10 for CVE CVE-2024-34156. [[PR]]( - Update golang.org/x/crypto to v0.31.0 to address CVE-2024-45337. [[PR]]( - Update golang.org/…
  • fork readiness: "This release includes support for Pectra activation in the Holesky and Sepolia testnets!"
  • deprecation wording: "- WARN log message on node startup advising of the upcoming deprecation of the --enable-historical-state-representation feature flag."
Feb 12, 2025
Prysmv5.2.0
Why this rating
  • high (all networks): > [!IMPORTANT] > This release is mandatory for all validator clients using mev-boost with a gas limit increase.
  • medium (all networks): Without upgrading to this release, validator clients will default to using local execution blocks when the gas limit starts to increase. > > Updating to this release is highly recommended, especially…
  • breaking wording: "This may be a breaking change if you're using port 13000 already."
  • deprecation wording: "- /eth/v1alpha1/validator/activation/stream grpc wait for activation stream is deprecated. pr"
  • performance wording: "This improves the profile guided optimizations in the go compiler."
Dec 16, 2024
Prysmv5.1.2-mekong
Nov 7, 2024