github prysmaticlabs/prysm v2.1.0

latest releases: v5.0.3, v5.0.2, v5.0.1...
2 years ago

v2.1.0

This release is comprised of 285 commits and these notes reflect only the highlights in the changelist.

View the full changelist here: v2.0.6...v2.1.0

Known Issues

  • Erroneous warning message in validator client when bellatrix fee recipient is unset. This is a cosmetic message and does not affect run time behavior in Phase0/Altair. Fixed by #10543
  • In Bellatrix/Kiln: Fee recipient flags may not work as expected. See #10555 for a fix and more details.

Added

  • Web3Signer support. See the documentation for more details.
  • Bellatrix support. See kiln testnet instructions
  • Weak subjectivity sync / checkpoint sync. This is an experimental feature and may have unintended side effects for certain operators serving historical data. See the documentation for more details.
  • A faster build of blst for beacon chain on linux amd64. Use the environment variable USE_PRYSM_MODERN=true with prysm.sh, use the "modern" binary, or bazel build with --define=blst_modern=true. #10229
  • Vectorized sha256. This may have performance improvements with use of the new flag --enable-vectorized-htr. #10166
  • A new forkchoice structure that uses a doubly linked tree implementation. Try this feature with the flag --enable-forkchoice-doubly-linked-tree #10299
  • Fork choice proposer boost is implemented and enabled by default. See PR #10083 description for more details.

Changed

  • Flag Default Change The default value for --http-web3provider is now localhost:8545. Previously was empty string. #10498
  • Updated spectest compliance to v1.1.10. #10298
  • Updated to bazel 5.0.0 #10352
  • Gossip peer scorer is now part of the --dev flag. #10207

Removed

  • Removed released feature for next slot cache. --disable-next-slot-state-cache flag has been deprecated and removed. #10110

Fixed

Too many bug fixes and improvements to mention all of them. See the full changelist

Security

  • Go version updated to security release 1.17.9. The security fixes do not apply to Prysm.
  • Go-ethereum components updated to 1.10.17-535f25 #10417

Don't miss a new prysm release

NewReleases is sending notifications on new releases.