v0.1.13

This release updates the optional logging stack to correctly set node metadata for better parsing. Please follow the below instructions if you opt to submit logging data to Obol.

1. Uncomment #CHARON_LOKI_ADDRESSES= in your .env file and set the URL provided to you by the Obol or Lido core team.
2. Uncomment #CLUSTER_NAME=, and #CLUSTER_PEER= in your .env file, and set them to your cluster's name and your node's name. Save the file.
3. Instead of using docker compose up -d to run the cluster. Use docker compose -f docker-compose.yml -f logging.yml up -d going forward.

This is a recommended release for running this repo on mainnet. Please anticipate more upgrades ahead of the Pectra hardfork expected in early April.

Note

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: use env vars to create promtail conf file by @apham0001 in #105
• fix: add condition in case vars are undefined by @apham0001 in #106

Full Changelog: v0.1.12...v0.1.13