search

SlingNode / slingnode-ansible-ethereum

Deploy Ethereum nodes using Ansible.
https://slingnode.com
MIT License
18 stars 1 forks source link

New client release #104

Closed pgjavier closed 1 year ago

pgjavier commented 1 year ago

23.6.1 updated

This is a required update for *Gnosis* network operators. It contains Gnosis Capella fork configuration.

Downloads
---------

* Available as 23.6.1 on Dockerhub ( <https://hub.docker.com/r/consensys/teku> )
* Download the binary distribution:

* tar.gz ( <https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/23.6.1/teku-23.6.1.tar.gz> ) (sha256: 4a33cf38265ba1b5eb5142eaad230d4b3aaf5130bfaf54d7d37cca9eac10d64c )
* zip ( <https://artifacts.consensys.net/public/teku/raw/names/teku.zip/versions/23.6.1/teku-23.6.1.zip> ) (sha256: 81106eaf1ac11710a47459ee2a5e763478cbbe0e618fdfeb72995062c65e30fa )

Breaking Changes
----------------

* The Development options --Xprogressive-balances-mode and --Xee-version have been removed and will no longer be recognised as command line options.
* Network configs were updated following concensus-specs changes ( <https://github.com/ethereum/consensus-specs/pull/3375> ). If you run custom network, you will need to add lines with network parameters ( <https://github.com/Consensys/teku/blob/0b5ef8a/ethereum/spec/src/main/resources/tech/pegasys/teku/spec/config/configs/mainnet.yaml#L102-L139> ) to your custom config (including the Deneb constants if required). If you are using a remote validator auto network feature, you will need to update both Beacon Node and Validator Client.

Additions and Improvements
--------------------------

* Added Gnosis configuration for the 🦉 Capella 🦉 network fork due at epoch 648704, UTC Tue 01/08/2023, 11:34:20
* Updated Sigmaprime's bootnodes
* Increased the pending pool size for attestations

-------------------------
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.

<https://newreleases.io/github/Consensys/teku?version=23.6.1|release note...>