Consensys-Incorporated/teku 23.6.0

on GitHub

This is a recommended update containing the rewards beacon-api endpoints, and an updated fix for the May non finality issue.

NOTE: Nethermind users on 1.19.X need to be at a minimum version of 1.19.2, due to compatibility issues with 1.19.0, 1.19.1.

Downloads

• Available as 23.6.0 on Dockerhub
• Download the binary distribution:
  • tar.gz (sha256: aacd4a4b8396d793163e2cf061146bd1d5436e95440b2f4a8653ef6bc37b4707)
  • zip (sha256: 948abc377dd33560ead4ce94b634372b59c1a6fd61d2f9f92117c26454a0615f)

Breaking Changes

• The command argument --Xengine-exchange-capabilities has been removed, update to use --exchange-capabilities-enabled if you are using this option.
• The command argument --Xdeposit-snapshot-enabled has been removed, just remove it from commandline/configuration if you use it, updated argument --deposit-snapshot-enabled defaults to true now.
• The /eth/v1/debug/beacon/heads endpoint has been removed in favor of the v2 Bellatrix endpoint /eth/v2/debug/beacon/heads.
• The /eth/v1/validator/blocks/:slot endpoint has been removed in favor of the v2 Altair endpoint /eth/v2/validator/blocks/:slot.
• The /eth/v1/beacon/blocks/:block_id endpoint has been removed in favor of the v2 Altair endpoint /eth/v2/beacon/blocks/:block_id.
• The /eth/v1/debug/beacon/states/:state_id endpoint has been removed in favor of the v2 Altair endpoint /eth/v2/debug/beacon/states/:state_id
• The /eth/v1/validator/liveness/:epoch endpoint was requiring the wrong body input and now conforms to the beacon-api spec.
• When --rest-api-enabled option is not specified and --rest-api-port is, --rest-api-enabled will now be set as true.
• Log messages previously printing WEI for builder bids and local payload values have been updated to print the ETH value.

Additions and Improvements

• Add support for Chiado (Gnosis testnet): --network=chiado
• Added beacon-apis rewards endpoints.
• Removed the experimental flag from /eth/v1/validator/liveness/:epoch rest-api endpoint.
• Following on from the non finality issue, improved state selection during attestation validation,
  where we failed to correctly identify that we could use the head state for validation of canonical attestation gossip.

Bug Fixes

• Fix a race condition on EL api result handling which may lead to beacon node remain syncing forever

Upcoming Breaking Changes

• Upgrading the minimum Java version to Java 17, which means users will need to upgrade their Java installation to at least Java 17. The docker versions relying on jdk16 will no longer be published, so docker users explicitly referencing the jdk16 build need to update their package to reference jdk17, as tags develop-jdk16, develop-jdk16-arm64, latest-jdk16 will no longer be updated.

Incident Statement - May 2023

As has been well documented by a post-mortem conducted by the Prysm team,
the Consensus layer suffered short periods of non-finality on the 11th and 12th of May, with the 12th of May being notable in that the network started an Inactivity leak.

To mitigate the problem, the Teku team released the 23.5.0 patch, which basically avoided processing some attestations due to
the observed behaviour of a number of clients suffering from memory contention if these attestations were fully validated by Teku.

This release contains a fix for the root cause of the issue, where the processing bug contributing to the original issue has been
rectified, greatly reducing the need for many states to be present while validating gossip.