Obol DVT
Connect existing EC & BN clients
If you are already running an Execution Client (EC) e.g. Geth and a Beacon Node (BN) e.g. Lighthouse you can connect your Obol DVT node to them. This allows you to reuse existing hardware and continue to run your solo staking validator alongside Obol DVT validators.
Update HTTP flags on existing Beacon Node
On your existing Beacon Node, ensure these flags are added so the Charon client can communicate directly.
Clone the ObolNetwork/charon-distributed-validator-node repo
There are three steps needed to change the configuration:
Copy and edit the .env
Copy the sample .env
file.
Uncomment (remove the #
) the line CHARON_BEACON_NODE_ENDPOINTS
. Add your existing Beacon Node IP address, for example "http://192.168.1.8:5052"
. As the Charon Client is running inside a Docker container you can't use localhost
, even though might be running on the same physical machine, it requires the IP address of the host machine.
Copy and edit the example override file
Any uncommented section will automatically override the same section in docker-compose.yml
when run with docker-compose up
. This allows you to edit the variables used by Docker without changing the docker-compose.yml
which could be modified in future updates.
Edit the newly copied file docker-compose.override.yml
and uncomment (remove the #
) the following lines:
services:
geth:
profiles: [disable]
lighthouse:
profiles: [disable]
You are now ready to start the Obol tutorial for creating an ENR and getting your new DVT validator set up!
Last updated