Skip to content

Releases: prysmaticlabs/prysm

v2.0.1

06 Oct 13:53
@prestonvanloon prestonvanloon
v2.0.1
843ed50
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.1

v2.0.1

This patch release fixes a few bugs in v2.0.0. Be sure to read the v2.0.0 release notes before updating from v1 to v2.

Fixed

  • Updated libp2p transport library to stop metrics logging errors on windows. #9733
  • Prysm's web UI assets serve properly #9732
  • Eth2 api returns full validator balance rather than effective balance #9722
  • Slashing protection service registered properly in validator. #9735

Security

We've updated the Prysm base docker images to a more recent build. #9727 #9674

Full Changelog: v2.0.0...v2.0.1

Assets 38
Loading

v2.0.0

04 Oct 17:49
@prestonvanloon prestonvanloon
v2.0.0
f7845af
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.0

v2.0.0

This release is the largest release of Prysm to date. v2.0.0 includes support for the upcoming Altair hard fork on the mainnet Ethereum Beacon Chain.
This release consists of 380 changes to support Altair, improve performance of phase0 beacon nodes, and various bug fixes from v1.4.4.

Upgrading From v1

Please update your beacon node to v2.0.0 prior to updating your validator. The beacon node can serve requests to a v1.4.4 validator, however a v2.0.0 validator will not start against a v1.4.4 beacon node. If you're operating a highly available beacon chain service, ensure that all of your beacon nodes are updated to v2.0.0 before starting the upgrade on your validators.

Added

  • Full Altair support. Learn more about Altair.
  • Added bootnodes from the Nimbus team. #9656
  • Revamped slasher implementation. The slasher functionality is no longer a standalone binary. Slasher functionality is available from the beacon node with the --slasher flag. Note: Running the slasher has considerably increased resource requirements. Be sure to review the latest documentation before enabling this feature. This feature is experimental. #8331
  • Support for standard JSON API in the beacon node. Prysm validators continue to use Prysm's API. #7510
  • Configurable subnet peer requirements. Increased minimum desired peers per subnet from 4 to 6. This can be modified with --minimum-peers-per-subnet in the beacon node. #9657.
  • Support for go build on darwin_arm64 devices (Mac M1 chips). Cross compiling for darwin_arm64 is not yet supported. #9600.
  • Batch verification of pubsub objects. This should improve pubsub processing performance on multithreaded machines. #9344
  • Improved attestation pruning. This feature should improve block proposer performance and overall network attestation inclusion rates. Opt-out with --disable-correctly-prune-canonical-atts in the beacon node. #9444
  • Active balance cache to improve epoch processing. Opt-out with --disable-active-balance-cache #9567
  • Experimental database improvements to reduce history state entry space usage in the beaconchain.db. This functionality can be permanently enabled with the flag --enable-historical-state-representation. Enabling this feature can realize a 25% improvement in space utilization for the average user , while 70 -80% for power users(archival node operators). Note: once this feature is toggled on, it modifies the structure of the database with a migration and cannot be rolled back. This feature is experimental and should only be used in non-serving beacon nodes in case of database corruption or other critical issue. #8954

New Metrics

Beacon chain node

Metric Description References
p2p_message_ignored_validation_total Count of messages that were ignored in validation #9538
beacon_current_active_validators Current total active validators #9623
beacon_processed_deposits_total Total number of deposits processed #9623
sync_head_state_miss The number of sync head state requests that are not present in the cache #9422
sync_head_state_hit The number of sync head state requests that are present in the cache #9422
total_effective_balance_cache_miss The number of get requests that are not present in the cache #9456
total_effective_balance_cache_hit The number of get requests that are present in the cache #9456
sync_committee_index_cache_miss_total The number of committee requests that aren't present in the sync committee index cache #9317
sync_committee_index_cache_hit_total The number of committee requests that are present in the sync committee index cache #9317
next_slot_cache_hit The number of cache hits on the next slot state cache #8357
next_slot_cache_miss The number of cache misses on the next slot state cache #8357
validator_entry_cache_hit_total The number of cache hits on the validator entry cache #9155 #9310
validator_entry_cache_miss_total The number of cache misses on the validator entry cache #9155 #9310
validator_entry_cache_delete_total The number of cache deletes on the validator entry cache #9310
saved_sync_committee_message_total The number of saved sync committee message total #9203
saved_sync_committee_contribution_total The number of saved sync committee contribution total #9203
libp2p_peers Tracks the total number of libp2p peers #9623
p2p_status_message_missing The number of attempts the connection handler rejects a peer for a missing status message #9505
p2p_sync_committee_subnet_recovered_broadcasts The number of sync committee messages that were attempted to be broadcast with no peers on the subnet #9390
p2p_sync_committee_subnet_attempted_broadcasts The number of sync committees that were attempted to be broadcast #9390
p2p_subscribed_topic_peer_total The number of peers subscribed to topics that a host node is also subscribed to #9538
saved_orphaned_att_total Count the number of times an orphaned attestation is saved #9442

Changed

  • Much refactoring of "util" packages into more canonical packages. Please review Prysm package structure and godocs.
  • Altair object keys in beacon-chain/db/kv are prefixed with "altair". BeaconBlocks and BeaconStates are the only objects affected by database key changes for Altair. This affects any third party tooling directly querying Prysm's beaconchain.db.
  • Updated Teku bootnodes. #9656
  • Updated Lighthouse bootnodes. #9656
  • End to end testing now collects jaeger spans #9341
  • Improvements to experimental peer quality scoring. This feature is only enabled with --enable-peer-scorer. #8794
  • Validator performance logging behavior has changed in Altair. Post-Altair hardfork has the following changes: Inclusion distance and inclusion slots will no longer be displayed. Correctly voted target will only be true if also included within 32 slots. Correctly voted head will only be true if the attestation was included in the next slot. Correctly voted source will only be true if attestation is included within 5 slots. Inactivity score will be displayed. #9589
  • Increased pubsub message queue size from 256 to 600 to support larger networks and higher message volume. #9702
  • The default attestation aggregation changed to the improved optimized max cover algorithm. #9684 #8365
  • Prysm is passing spectests at v1.1.0 (latest available release). #9680
  • --subscribe-all-subnets will subscribe to all attestation subnets and sync subnets in post-altair hard fork #9631.
  • "eth2" is now an illegal term. If you say it or type it then something bad might happen. #9425
  • Improved cache hit ratio for validator entry cache. #9310
  • Reduced memory overhead during database migrations. #9298
  • Improvements to beacon state writes to database. #9291

Changed Metrics

Beacon chain node

Metric Old Name Description References
beacon_reorgs_total beacon_reorg_total Count the number of times a beacon chain has a reorg #9623

Deprecated

These flags are hidden from the help text and no longer modify the behavior of Prysm. These flags should be removed from user runtime configuration as the flags will eventually be removed entirely and Prysm will fail to start if a deleted or unknown flag is provided.

  • --enable-active-balance-cache #9567
  • --correctly-prune-canonical-atts #9576
  • --correctly-insert-orphaned-atts #9575
  • --enable-next-slot-state-cache #9602

Removed

Note: Removed flags will block starting up with an error "flag provided but not defined:".
Please check that you are not using any of the removed flags in this section!

  • Prysm's standalone slasher application (cmd/slasher) has been fully removed. Use the --slasher f...
Read more
Assets 38
Loading

v2.0.0-rc.2

21 Sep 17:10
@prestonvanloon prestonvanloon
v2.0.0-rc.2
161a13a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.0-rc.2 Pre-release
Pre-release

Pre-release v2.0.0-rc.2

Changes

  • Many bug fixes and improvements (full detailed v2 changelog coming soon!)
  • Major refactoring and reorganizing of Prysm codebase.
  • Further alignment with standard API and standard prometheus metrics
  • Implemented Altair spec from: https://github.com/ethereum/eth2.0-specs/tree/dev/specs/altair
  • Significant changes relative to the latest production release. Compare this diff for full list of changes.

To learn more about Altair: https://github.com/ethereum/annotated-spec/blob/master/altair/beacon-chain.md

Using this pre-release

  • Docker images are available for beacon node and validator with the tag v2.0.0-rc.2.
  • Prysm.sh script will only use v2.0.0-rc.2 if you set the version override environment variable USE_PRYSM_VERSION=v2.0.0-rc.2
  • Build from source at commit 161a13a or tag v2.0.0-rc.2.

Prater Genesis Bootstrapping

If you have not run a Prater Prysm node yet, you will need to download the pre-generated genesis state for prater and provide the beacon node flag --genesis-state=/path/to/prater/genesis.ssz.
The genesis.ssz state file can be found in the eth2-clients/eth2-networks repo.

Thank you all for the support!

Assets 38
Loading

v1.4.4

01 Sep 20:01
@prestonvanloon prestonvanloon
v1.4.4
29d48df
Compare
Choose a tag to compare
v1.4.4

(2021-09-01)

This release has a few features enabled and a few new features for testing. Updating to this release is encouraged, but not required for mainnet validators.

Notable changes

Enabled features

  • Update head timely feature is now on by default. This beacon node feature updates the "head" of the chain in a more timely manner and may result in performance or profitability improvements. If any issues are observed, you may opt out with --disable-update-head-timely. See #8412 and #9224.
  • Optimized balance updates feature is now on by default. This beacon node feature is an improved process of calculating validator balances. This feature improves performance of epoch processing, but may result in higher memory usage. If any issues are observed, you may opt out with --disable-optimized-balance-update. See #8743 and #9225.

New features (not enabled)

These new beacon node features are introduced behind "feature flags" as part of our normal feature testing. These flags are low risk to enable and can improve the overall health of the network. We encourage users to opt in to these features early, however, these features will be enabled by default in an upcoming release.

  • --correctly-insert-orphaned-atts beacon node flag supports block construction with orphaned attestations. This feature may increase block profitability and general network attestation inclusion efficiency. See #9441 and #9442.
  • --correctly-prune-canonical-atts beacon node flag reduces attestation pool removal when non-canonical blocks are received. This feature may increase block profitability and general network attestation inclusion efficiency. See #9443.

Other fixes / changes

  • Increased cache size for seen attestations #9476
  • Limit deposit proof construction to genesis construction only #9289
  • Fix initial sync stall when chain experiences extremely long period of non-finalized epochs #9452

Full list of changes below.

1.4.4 (2021-08-31)

Assets 47
Loading

v2.0.0-rc.1

31 Aug 16:34
@prestonvanloon prestonvanloon
v2.0.0-rc.1
49dce52
Compare
Choose a tag to compare
v2.0.0-rc.1 Pre-release
Pre-release

Pre-release v2.0.0-rc.1

This is a required upgrade for all nodes on the Prater Testnet.

As you may have heard, Prater is upgrading to Altair at 2021-09-02 12:24:00 UTC. We are recommending a pre-release for Prater hard fork to ensure bugs and breakages do not leak into mainnet. Please DO NOT upgrade for your mainnet nodes with this release. We will have a proper release for that after stability has been ensured in the testnet.

Thank you all for the support!

Changes

To learn more about Altair: https://github.com/ethereum/annotated-spec/blob/master/altair/beacon-chain.md

Using this pre-release

  • Docker images are available for beacon node and validator with the tag v2.0.0-rc.1.
  • Prysm.sh script will only use v2.0.0-rc.1 if you set the version override environment variable USE_PRYSM_VERSION=v2.0.0-rc.1
  • Build from source at commit 49dce52 or tag v2.0.0-rc.

Prater Genesis Bootstrapping

If you have not run a Prater Prysm node yet, you will need to download the pre-generated genesis state for prater and provide the beacon node flag --genesis-state=/path/to/prater/genesis.ssz.
The genesis.ssz state file can be found in the eth2-clients/eth2-networks repo.

Assets 50
Loading

v2.0.0-rc.0

16 Aug 23:54
@prestonvanloon prestonvanloon
v2.0.0-rc.0
4db77ce
Compare
Choose a tag to compare
v2.0.0-rc.0 Pre-release
Pre-release

Pre-release v2.0.0-rc.0

This is a required upgrade for all nodes on the Pyrmont Testnet.

As you may have heard, Pyrmont is upgrading to Altair at 2021-08-19 12:00:07 UTC. We are recommending a pre-release for Pyrmont hard fork to ensure bugs and breakages do not leak into mainnet. Please DO NOT upgrade for nodes other than Pyrmont testnet. We will have a proper release for that after stability has been ensured in the testnet.

Thank you all for the support!

Changes

To learn more about Altair: https://github.com/ethereum/annotated-spec/blob/master/altair/beacon-chain.md

Using this pre-release

  • Docker images are available for beacon node and validator with the tag v2.0.0-rc.0.
  • Prysm.sh script will only use v2.0.0-rc.0 if you set the version override environment variable USE_PRYSM_VERSION=v2.0.0-rc.0
  • Build from source at commit 4db77ce or tag v2.0.0-rc.
Assets 50
Loading

v1.4.3

03 Aug 18:36
@prestonvanloon prestonvanloon
v1.4.3
8bca66a
Compare
Choose a tag to compare
v1.4.3

(2021-08-03)

Small fix on top of v1.4.2. Please review the v1.4.1 release notes if upgrading from v1.3.x or older.

Notable changes

  • Fix recursive stack overflow from grpc-gateway handler #9264 fixes #9246

1.4.3 (2021-07-30)

Assets 50
Loading

v1.4.2

22 Jul 14:16
@prestonvanloon prestonvanloon
v1.4.2
b365090
Compare
Choose a tag to compare
v1.4.2

(2021-07-22)

Small fix on top of v1.4.1. Please review the v1.4.1 release notes if upgrading from v1.3.x or older.

Notable changes

  • Fix subcommands such as validator accounts list #9236

1.4.2 (2021-07-21)

Assets 50
Loading

v1.4.1

20 Jul 19:03
@prestonvanloon prestonvanloon
v1.4.1
a9ee3ee
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.1

(2021-07-20)

Welcome to another Prysm release! This release has many changes, fixes, and features!

This is a required release for supporting the upcoming London hardfork on Ethereum mainnet. Prysm releases prior to this version may experience warnings or errors when fetching block data from an eth1 endpoint after London is activated. These errors can lead to missed block proposals if your block requires deposits that Prysm was unable to fetch due to new changes in the London hardfork.

⚠️ Important: Update to this release before the London hardfork on Ethereum mainnet! ⚠️

Where is v1.4.0?

In the last release, we accidentally pushed the git tag for v1.4.0 when creating v1.3.11. The tag was quickly removed from github and the release was successfully tagged as v1.3.11. Unfortunately, go.mod / godocs has cached the v1.4.0 tag already to point to the same commit as v1.3.11. There really isn't much of an issue here, except that pushing another v1.4.0 may cause some confusion or issues with using go.mod and go get. So, we are simply skipping 1.4.0 and jumping to 1.4.1.

Notable changes in v1.4

  • Ethereum APIs endpoints, except validator endpoints, are ready to use! See #7510 for more details of the implementation statuses.
  • Go-ethereum dependency update to support London hardfork. #9157
  • Validator Doppelganger verification --enable-doppelganger #9120
  • Tooling for boltdb bucket analysis #9116
  • Strict argument validation when starting Prysm processes #9129
  • Improvements to prysm.sh #9072
  • Improvements to client-stats #9039 (Docs link)
  • Database backup permissions fix #8888

Experimental/new features to test

These features have passed our own internal testing but we'd still like to see some users feedback before we roll them out as default in a stable release.

Validator features

  • --attest-timely validator can attest timely after current block processes. See #8185 for more details
  • --enable-doppelganger Enables the validator to perform a doppelganger check on startup

Beacon node features

  • --update-head-timely Improves update head time by updating head right after state transition. Note: This feature is going to flip to "opt-out" in next release.

Prysm slasher binary deprecation

We have been communicating that the slasher is going to be deprecated in the v1.4 release. This effort has been pushed back while we work on various storage optimizations in parallel to Altair development. Expect the Prysm slasher binary will be deprecated and removed in the upcoming Prysm v2 release with Altair support. Follow the v2 tracking issue for more info #9166.

Full list of changes below.

1.4.1 (2021-07-09)

Read more
Assets 50
Loading

v1.3.11

16 Jun 17:20
@prestonvanloon prestonvanloon
v1.3.11
9fd5575
Compare
Choose a tag to compare
v1.3.11

(2021-06-16)

This release contains a fix for the validator UI as well as many other improvements/fixes.

⚠️ Prysm slasher binary will be deprecated and no longer provided in the next release. The slasher functionality will be available in the beacon node binary in the 1.4.0 release. ⚠️

Notable changes:

  • Update web-ui to beta.4, fixes logs displayed in UI #9047
  • Fix json field names to be snake_case instead of camelCase. Fixes UI display issues. #8988
  • Support for Graffiti hex strings prefixed with hex: #8894
  • Client stats graceful failure handling #8976
  • Cache eviction policy for committees changed to LRU. #8996 Possibly fixes some resource spikes #8483.
  • SSZ variable length bounds enforced in SSZ layer. #8936
  • Small improvement to epoch processing by refactoring sqrt() call. #8945

Full list of changes below.

1.3.11 (2021-06-16)

Assets 50
Loading