This is a recommended update for mainnet operators running Nimbus. This release is optional for other operators. Please note the mandatory adjustment to .env vars required since v0.2.3 if updating to this release.
Operators must update to a Fusaka-ready release before the Mainnet Fusaka hard fork on December 3rd. Many clients have released updates since their first Fusaka-ready client, please take a final review of your versions ahead of the fork. (Lodestar are expected to release v1.37.0 on December 1st, which will be a recommended update for those running it as a validator client).
Important
To maximise compatibility of environment variable interpolation across operating systems, changes have been made between this version and v0.2.3.
Please set (uncomment) the following .env vars if you haven't already, or your charon, mev-boost, and charon-dv-exit-sidecar may not start properly.
CHARON_BEACON_NODE_ENDPOINTS=http://${CL}:5052
CHARON_EXECUTION_CLIENT_RPC_ENDPOINT=http://${EL}:8545
VE_BEACON_NODE_URL=http://${CL}:5052
VE_EXECUTION_NODE_URL=http://${EL}:8545
LIDO_DV_EXIT_BEACON_NODE_URL=http://${CL}:5052
Copying the .env.sample.mainnet file afresh and making any modifications you may have made, might be the least disruptive way to pick up these changes.
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 file variables, by setting EL=el-none, CL=cl-none, and MEV=mev-none for example. Read more about client swapping in our docs.
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.
To update to this version, please run the following commands:
# Stop the node
docker compose down
# Save any local changes
git stash
# Update your local copy of this repo
git pull
# Checkout this release
git checkout v0.2.6
# Re-apply the stashed local changes
git stash apply
# Restart the node
docker compose up -dNote
lido-charon-distributed-validator-node is a repo intended as a deployment guide and is not intended to be the canonical way to deploy a distributed validator.
Operators are encouraged to use this repository to build and maintain their own configurations that work for their individual use case. Please work with your squad to have your cluster exposed to no single point of failure on three or more nodes.
What's Changed
- Fix quoting for cluster name and peer replacements in config by @Lorenz29 in #208
- Bump to latest nimbus patch by @OisinKyne in #211
New Contributors
Full Changelog: v0.2.5...v0.2.6