Repository navigation
v2.0.0-rc2
Pre-releaseWarning
This is a release candidate and a required update for Hoodi operators ahead of the Glamsterdam (Gloas) fork, activating on Hoodi at epoch 132352, October 26, 2026, 17:42:48 UTC. Mainnet operators should not update and should remain on v1.11.1.
This is CDVN's v2.0.0-rc2 release. It runs Charon v2.0.0-rc2, with Gloas support, and Gloas-ready clients: Lighthouse v8.3.1, Teku 26.10.1, Lodestar v1.50.0, Nimbus v26.10.1, Prysm v7.3.0, Grandine 3.0.0-rc.1, Nethermind 2.2.0, Reth v2.8.0 and Commit-Boost v0.12.0-rc1. Charon generates .charon/vc-config/proposer-config.json with your fee recipient, gas limit and builders, and every validator client reads its proposer settings from it. Another patch release may come if/when more clients push security fixes for the incidents this week. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.
Note
Expect more release candidates before the fork. Several clients are still releasing fixes for the eMudhra certificate authority compromise and the Node.js security release of the last 72 hours. We'll publish a new release candidate as they land, so please keep an eye on this repository.
Update
- Add the builder list to your
.env, copied exactly from.env.sample.hoodi. Every operator in your cluster must use the same list, in the same order, so agree on it with your cluster first:CHARON_BUILDER_URLS=https://builder-hoodi.nflaig.dev,https://hoodi.titanrelay.xyz - Update and restart:
# Stop the node docker compose down # Save your local .env / custom overrides git stash # Update your local copy of this repo git pull # Checkout this release git checkout v2.0.0-rc2 # Re-apply your stashed changes git stash apply # Restart the node docker compose up -d
The Lighthouse, Teku, Prysm and Nimbus validator clients run from images built locally on top of the official ones, so the first docker compose up -d after updating takes a little longer.
Once your node is running, check that Charon generated the proposer config with your builders: cat .charon/vc-config/proposer-config.json | jq. default_config.builder.builders must list every URL in your CHARON_BUILDER_URLS, and the builder section must be identical on every node in your cluster. If a node's list differs from its peers', Charon logs Mismatching peer builder configuration.
What's changed since v2.0.0-rc1
- Reth
v2.8.0: schedules the Amsterdam fork on Hoodi. Reth operators must run this release before the fork. It also changes some defaults, see the Reth release notes. - Lighthouse
v8.3.1(beacon node and validator client): a high-priority release that updates trusted certificates after the eMudhra CA compromise. - Monitoring: Prometheus
v3.15.1, Grafana13.2.4, Loki3.7.9, Tempo3.1.1and Alloyv1.21.1, with security fixes and the patched Go releases.
Charon and the other clients are unchanged from v2.0.0-rc1.
If you already ran v2.0.0-rc1
Most operators can skip this section. It only applies if you started v2.0.0-rc1 before setting CHARON_BUILDER_URLS, or with a different builder list from your cluster's. Charon writes .charon/vc-config/proposer-config.json the first time it starts and never changes it afterwards, so regenerate it. Replace vc-lodestar with the VC set in your .env (vc-lighthouse, vc-nimbus, vc-prysm or vc-teku):
- Stop Charon and your validator client:
docker compose stop charon vc-lodestar - Remove the outdated proposer config:
rm .charon/vc-config/proposer-config.json - Start Charon first. It generates a new proposer config from your
.env:docker compose up -d charon - Check the new file lists your builders:
cat .charon/vc-config/proposer-config.json | jq - Start your validator client. It reads the file on start:
docker compose up -d vc-lodestar
If the file and your .env don't match, Charon logs Builder flags differ from the proposer config file.
What's Changed
- images: bump Lighthouse v8.3.1, Reth v2.8.0 and monitoring for rc3 by @OisinKyne in #505
Full Changelog: v2.0.0-rc1...v2.0.0-rc2
