charon-distributed-validator-node
charon-distributed-validator-node copied to clipboard
Run one node as part of Distributed Validator Cluster using docker-compose
Lodestar does not natively support importing keystores with different password in an efficient way right now (see https://github.com/ChainSafe/lodestar/issues/5249) that's why each keystore is imported individually right now via `validator import`...
this PR adds a FEE_RECIPIENT .env variable and passes it through to the Lodestar and Lighthouse validator clients
This PR fixes a couple of errors encountered when trying to use the geth_teku_lighthouse example. 1 - lighthouse validator was failing to start with error: "lighthouse_vc-1 | error: unexpected value...
Add support for partners - easier overriding of env variables and docker compose files. Implement Lido as first partner. Up until now Lido has been using lido-charon-distributed-validator-node repository, however, this...
# 🎯 Problem to be solved An approach that was taken to ease the setup for a partner organisation (Lido) was to create a fork of this repository and configure...
This release includes improvements related to fetching duties if node was previously syncing.
It would be nice to be able to configure `-min-bid` on mev-boost via env variable
Automatically generated PR to update version to v1.4.1
For charon v1.4.x: - Removed jaeger setup. - Added tempo setup with OTLP settings. Same settings were tested with kurtosis-charon.
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/ObolNetwork/charon-distributed-validator-node). This repository currently has no open or...