This release is an update for mainnet users, and builds upon releases v0.1.22, v0.1.23, and v0.1.24. This release is not fully Fusaka hardfork ready, so please expect at least one more update before the scheduled hardfork expected on December 3rd.
Mainnet Users Action Required
If this is your first update to LCDVN since v0.1.21, it is important to note that certain environment variables have changed since that release. This is to allow the graceful swap between different client types.
Please consult with your cluster, and see if enough node operators can swap to diverse EL/CLs and VCs before the Fusaka hardfork. The client swap guide is here.
At a minimum, mainnet users should add the following values to their .env file before calling docker compose up -d to finish their update. Consider opening .env.sample.mainnet and copying that fresh to .env, and re-applying any changes you had made, to minimise divergences/missing values.
# Easy track contract addresses.
VE_EASY_TRACK_ADDRESS=0xF0211b7660680B49De1A7E9f25C65660F0a13Fea
# Easy track motion creator addresses, set to the Simple DVT Module Committee multisig.
VE_EASY_TRACK_MOTION_CREATOR_ADDRESSES_ALLOWLIST=["0x08637515E85A4633E23dfc7861e2A9f53af640f7"]
Important
Users should no longer run docker compose -f docker-compose.yml -f logging.yml -f docker-compose.override.yml to run their cluster, they should instead only run docker compose up -d. Overrides to turn off certain containers (e.g. in the case where you use an external EL/CL rather than the one in this repo) should be done with .env vars, setting EL=el-none, CL=cl-none, and MEV=mev-none for example.
Logging can be enabled by uncommenting the line #MONITORING=${MONITORING:-monitoring},monitoring-log-collector in their .env file, and setting CHARON_LOKI_ADDRESSES to a URI given to you by the Obol team.
Note
This version of Charon is Fusaka ready, but the default lighthouse CL and MEV-boost clients in this repo are not. This means Charon will periodically output warn logs highlighting this fact. Lighthouse and mev-boost must be updated to a newer version before the Fusaka hardfork on mainnet. Expected on December 3rd.
To update to this version, please run the following commands:
# Stop the node
docker compose down
# Save any local changes
git stash
git pull
# Check out this release
git checkout v0.1.25
# Re-apply the local changes
git stash apply
# Restart the node
docker compose up -dWhat's Changed
- Lido bitnami by @apham0001 in #173
- chore(deps): update actions/github-script action to v8 by @renovate[bot] in #166
- Bump to v1.7.0 by @KaloyanTanev in #175
- feat(env): add Easy Track contract addresses to mainnet sample config by @cnupy in #176
- feat: update Hoodi sample environment config for validator ejector by @cnupy in #181
- Update mev relays and dv exit sidecar uris by @OisinKyne in #183
- Fix nimbus run.sh by @TobiWo in #179
- Separate monitoring compose by @KaloyanTanev in #185
- Update to latest stable releases by @OisinKyne in #187
New Contributors
Full Changelog: v0.1.23...v0.1.25