Skip to content

Releases: eth-educators/eth-docker

Version 2.6.0.0

25 Jan 08:43
2310403
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

Breaking changes

  • Requires Lighthouse 4.6.0 or later

New features

  • Supports ./ethd prune-lighthouse to prune Lighthouse state
  • Lighthouse VC will broadcast duties to all configured CLs, and uses v3 API for producing blocks
  • Besu on machines with 64 GiB of RAM or more will use the high spec flag
  • Added Bloxroute relay to default Holesky MEV config
  • Prysm uses 70 max peers by default
  • ./ethd config offers a VC-only setup on Gnosis Chain. Thanks @haurog!
  • Remove Nethermind memory hints
  • Add network aliases to CLs, ${NETWORK}-consensus. This can be useful in setups with multiple Eth Docker
    installations on one host, all connected to the same Docker overlay network
  • Changed Prometheus yq dependency to version 4
  • Update Lodestar beacon max-old-space-size to 8192. Thanks @nflaig!
  • Changed Teku default heap size to 5G
  • ./ethd keys does some input vaidation on public keys and other user-supplied values

Bug fixes

  • Nethermind prune no longer outputs an error message on Nethermind 1.25.0 and later
  • Added parameter to support Erigon 2.55 and later

Version 2.5.0.1

31 Dec 08:26
9b6cd95
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Breaking for Besu: Requires Besu 23.10.3
  • Besu will limit its trie logs, and on fresh sync heal its flat DB for better RPC performance
  • Besu source build uses Java 21 runtime (but continues to build with Java 17)
  • Additional pre-previsioned Grafana alerts: memory, CPU, out of memory (OOM) kill
  • Geth can keep its ancient directory on a separate path, see ANCIENT_DIR in .env
  • Logs dashboard works if the directory is not called eth-docker
  • Nethermind auto-prune uses 350 GiB threshold on Gnosis Chain again (fixes issue introduced in v2.4.1.0)

Version 2.4.1.0

29 Dec 15:29
65ae1bb
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Fix ./ethd keys import with unique passwords. Thanks @shamoya!
  • Fix Teku archive sync on Holesky
  • Nethermind auto-prune is network aware: Kicks off at 350 GiB mainnet, 50 GiB otherwise
  • Web3signer PostgreSQL migration to PG16 during ./ethd update
  • Teku source build uses Java 21
  • Slightly less naive offline detection for create-withdrawal-change.sh

Version 2.4.0.0

13 Dec 09:53
0e6b218
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes for most users
It is mandatory for users of Teku 23.12.0 who do not wish to use checkpoint sync

  • Breaking change: Teku without checkpoint sync (e.g. archive node) uses parameters that require Teku 23.12.0
  • Fixed checkpoint sync url query during ./ethd config
  • ./ethd keys can set individual Graffiti, as long as the client supports it
  • Prometheus instance hard-coded for easier use with dashboards that use instance
  • Added a pre-provisioned Grafana alert for disk space
  • Renamed Teku and Nimbus -legacy.yml files to -allin1.yml

Version 2.3.12.0

04 Dec 15:51
4242c38
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Fix Nimbus Web3signer wait loop
  • Add ./ethd space
  • Add Eden relays to Holesky during ./ethd config
  • mev-boost can be source-built
  • ./ethd update can be --non-interactive
  • Support ETHD_FRONTEND=noninteractive as an alternative to --non-interactive

Version 2.3.11.0

01 Dec 16:23
d23f416
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • New Nimbus and Teku deployments use a dedicated validator client service. Legacy deployments use the
    nimbus-legacy.yml and teku-legacy.yml files.
    NB If you made manual changes to nimbus.yml or teku.yml, these will not automatically carry over to the -legacy.yml files. Please recreate your changes. Also consider whether CL_EXTRAS and VC_EXTRAS could do what you need, without manual changes.
  • Introduced a wait loop to Nimbus when using Web3signer, to work around a bug in Nimbus
  • Better handling of legacy master branch of Eth Docker

Version 2.3.10.0

25 Nov 12:15
3c2712b
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Prometheus metrics collection improved. Scrape targets in ./prometheus/conf.d, uses yq to merge custom-prom.yml. Default scrape interval 15s instead of 1m now possible because of this, which solves a whole bevvy of "No Data" in preloaded dashboards. Thanks to @aliask!
  • Preserve empty RAPID_SYNC_URL in .env
  • Extraneous web3signer messages during keyimport, when web3signer was not in use, resolved
  • ./ethd up <service-name> supported
  • Version numbering will be semver-ish from here: World-shaking changes (think Ethereum merge) first digit, breaking changes second digit, enhancements third digit, bug fixes fourth digit.

Version 2.3.9

15 Nov 13:08
e7c5f31
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Eth Docker's version can be pinned in .env
  • Use new Teku v23.11.0 syntax. Breaking for any prior version.
  • Fix the ./ethd prune-geth command
  • Additional IPv6 support for Lodestar, Geth and Erigon
  • Use .NET 8 for Nethermind source build
  • default.env defaults to Holesky testnet

Version 2.3.8

08 Nov 13:57
49ddf28
Compare
Choose a tag to compare

This is an optional release with new features and bug fixes

  • Fixed a breaking bug in cl-traefik.yml that impacted 2.3.7
  • Fix ./ethd keys delete all when using Web3signer
  • ./ethd config can now configure SSV for Holesky
  • Switched Prometheus to scrape by Docker labels
  • Added Web3signer dashboard
  • Fixed Nimbus dashboard provisioning
  • Running multiple RPC nodes connected to one central traefik is now easier. If that is your use case, set
    EL_NODE=http://${NETWORK}-execution:8551 in .env. See the ELCLIENT.yml files for the alias this references.

Version 2.3.7

02 Nov 21:29
16a36e7
Compare
Choose a tag to compare

This is an optional release with security relevant changes for traefik users

  • BREAKING change for users who use traefik to access the execution client RPC API, consensus client REST
    API or execution client engine RPC API: The el-traefik.yml, cl-traefik.yml and ee-traefik.yml files are
    now required for this. This was done to avoid host header attacks against users who just want to expose Grafana
    and may not have firewall rules in place to trusted source IPs.
  • Ditto for Prometheus access, where it is prometheus-traefik.yml