Skip to content

v2.0.0-rc1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@KaloyanTanev KaloyanTanev released this 21 Oct 18:33
· 4 commits to main since this release
v2.0.0-rc1
f87a7c3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Obol Logo

Warning

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-rc1 release. It bumps Charon to v2.0.0-rc2, with Gloas support, and the rest of the stack to Gloas-ready versions: Lighthouse v8.3.0, 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.7.0 and Commit-Boost v0.12.0-rc1. Charon now 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. Feedback is welcome and appreciated, please use github issues or discord if you have trouble with this release.

Breaking changes

Important

Copy CHARON_BUILDER_URLS from .env.sample.hoodi into your .env, and agree on it with your cluster: every operator must use the same builder list, in the same order. If lists differ, Charon logs Mismatching peer builder configuration.

Important

Set CHARON_BUILDER_URLS before starting the new version. Charon writes .charon/vc-config/proposer-config.json the first time it starts and never changes it afterwards. If you started v2.0.0-rc1 without the builder list, or you change the list later, regenerate the file and restart your validator client. Replace vc-lodestar below with the VC set in your .env (vc-lighthouse, vc-nimbus, vc-prysm or vc-teku):

  1. Stop Charon and your validator client:
    docker compose stop charon vc-lodestar
  2. Remove the outdated proposer config:
    rm .charon/vc-config/proposer-config.json
  3. Start Charon first. It generates a new proposer config from your .env:
    docker compose up -d charon
  4. Check that the new file lists your builders:
    cat .charon/vc-config/proposer-config.json | jq
  5. Start your validator client. It reads the new 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.

The Lighthouse, Teku, Prysm and Nimbus validator clients now run from images built locally on top of the official ones, so the first docker compose up -d takes a little longer.

What's Changed

Full Changelog: v1.11.1...v2.0.0-rc1

Contributors

KaloyanTanev
Assets 2
Loading