github Consensys/teku 21.12.1
v21.12.1

latest releases: 24.10.3, 24.10.2, 24.10.1...
2 years ago

This is a critical security update. All users should update immediately.

Downloads

  • Available as 21.12.1 on Dockerhub
  • Download the binary distribution:
    • tar.gz (
      sha256: 7800e5989632d35806e98d7b141dc9d4b75ebc5b1718406834a343a8ef44487b)
    • zip (
      sha256: 977bba9f52ddf96bccdc4af7c1efef94fcbd166b19f9b8babbac5afecac4807a)

Bug Fixes

  • Updated log4j version and configuration to guarantee a zero-day remote code exploit published for log4j cannot be used against Teku nodes.

Upcoming Breaking Changes

  • Support for the Pyrmont testnet will be removed in an upcoming release. The Prater testnet should be used instead.
  • The /teku/v1/beacon/states/:state_id endpoint has been deprecated in favor of the standard API /eth/v1/debug/beacon/states/:state_id which now returns the state as SSZ when the Accept: application/octet-stream header is specified on the request.
  • The /eth/v1/debug/beacon/states/:state_id endpoint has been deprecated in favor of the v2 Altair endpoint /eth/v2/debug/beacon/states/:state_id
  • The /eth/v1/beacon/blocks/:block_id endpoint has been deprecated in favor of the v2 Altair endpoint /eth/v2/beacon/blocks/:block_id
  • The /eth/v1/validator/blocks/:slot endpoint has been deprecated in favor of the v2 Altair endpoint /eth/v2/validator/blocks/:slot
  • The commandline option --validators-performance-tracking-enabled has been deprecated in favour of --validators-performance-tracking-mode
  • The commandline option --network of the validator-client subcommand introduces a new option value auto, which automatically
    fetches network configuration information from the configured beacon node endpoint. Other --network option values for an external validator client
    are now deprecated in favour of this option value (usage: teku validator-client --network=auto)

Don't miss a new teku release

NewReleases is sending notifications on new releases.