Consensys/teku 24.6.0

on GitHub

This is a recommended update with with performance improvements and bug fixes.

Downloads

• Available as 24.6.0 on Dockerhub
• Download the binary distribution:
  • tar.gz (sha256: 3be854b094302d0d4aba3492248f76f13d9245a2d1778989239440ef8ccf06d8)
  • zip (sha256: 91d7937c9f6d23fcba8294fcfd8dd3e0a492e2a84bc8b925143eb28dc4262a3d)

Current Releases

For information on changes in released versions of Teku, see
the releases page.

Breaking Changes

• Renamed --Xp2p-dumps-to-file-enabled hidden CLI option to --Xdebug-data-dumping-enabled

Additions and Improvements

• Added metadata fields to /eth/v1/beacon/blob_sidecars/{block_id} Beacon API response as per ethereum/beacon-APIs#441
• Added rest api endpoint /teku/v1/beacon/state/finalized/slot/before/{slot} to return the slot of the most recently stored state at or before the specified slot.
• The validator client will start using the v2 variant of the beacon node block publishing
  endpoints. In the cases where the block has been produced in the same beacon node, only equivocation validation will be done instead of the entire gossip validation.
• Docker images are now based on ubuntu 24.04 LTS (noble)
• The teku vc subcommand fails when no validator key source is provided. In order to run a validator client, one of the following options must be set:
  --validator-keys, --validators-external-signer-url or --validator-api-enabled
• Updated dependencies.

Bug Fixes

• Fixed performance degradation introduced in 24.4.0 regarding archive state retrieval time.
• Fixed file writer when storing database mode settings to file (related to #8357).

Upcoming Breaking Changes

• Next release will introduce a breaking change to Teku's metrics. This is due to some metrics changing names after a library upgrade.
  We recommend all users of the Teku - Detailed dashboard to upgrade to version Revision 12
  as soon as possible. Documentation with all metrics that have been renamed will be provided.
• Next release will require Java 21. The current release is compatible, please consider upgrading before the next release.
• From the next release, you will need to explicitly set --data-storage-mode=(prune|archive) unless you're using minimal data-storage-mode (which is the default behaviour).