You will use the CLI to create the cluster definition file, which you will distribute it to the operators manually. @@ -341,7 +379,7 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the operators in your cluster to also finish these steps.
cluster-definition.json file created by
the leader/creator. You should save it in the .charon/{" "}
folder that was created initially. (Alternatively, you can use the{" "}
@@ -351,12 +389,9 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the
cluster-definition.json file and you place it in a .charon subdirectory, run: docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.1.2 dkg --publishand the DKG process should begin.
cluster_definition_hash), the key generation ceremony begins.
+ The node is now ready and will attempt to complete the DKG. You can monitor the DKG progress via the 'Logs' tab of the package. Once all clients in the cluster can establish a connection with one another and they each complete a handshake (confirm everyone has a matching cluster_definition_hash), the key generation ceremony begins.
Nethermind) and a consensus layer client (Lighthouse) using Docker Compose. You can also leverage alternative ways to run a node such as Ansible, Helm, or Kubernetes manifests.
+ The CDVN repository is configured to sync an execution layer client (Nethermind) and a consensus layer client (Lighthouse) using Docker Compose, further client combinations can be prepared using Sedge. You can also leverage alternative ways to run a node such as Ansible, Helm, or Kubernetes manifests.
-::: +# To prepare the node for the main Ethereum network +# Copy ".env.sample.mainnet", renaming it ".env" +cp .env.sample.mainnet .env -:::note -If you have a `nethermind` node already synced, you can simply copy over the directory. For example: `cp -r ~/.ethereum/goerli data/nethermind`. This makes everything faster since you start from a synced nethermind node. -::: + +In the same folder where you created your ENR in Step 1, and ran the DKG in Step 3, start your node in the DV cluster with docker compose. ```shell -# Delete lighthouse data if it exists -rm -r ./data/lighthouse +# To be run from the ./charon-distributed-validator-node folder # Spin up a Distributed Validator Node with a Validator Client docker compose up -d ``` +:::warning + +Do not start this node until the DKG is complete, as the charon container will interfere with the charon instance attempting to take part in the DKG ceremony. + +::: + If at any point you need to turn off your node, you can run: ```shell # Shut down the currently running Distributed Validator Node docker compose down ``` - You should use the Grafana dashboard that accompanies the quickstart repo to see whether your cluster is healthy. - ```shell # Open Grafana dashboard open http://localhost:3000/d/d6qujIJVk/ ``` - In particular you should check: - - That your Charon client can connect to the configured beacon client. - That your Charon client can connect to all peers directly. - That your validator client is connected to Charon, and has the private keys it needs loaded and accessible. - Most components in the dashboard have some help text there to assist you in understanding your cluster performance. - You might notice that there are logs indicating that a validator cannot be found and that APIs are returning 404. This is to be expected at this point, as the validator public keys listed in the lock file have not been deposited and acknowledged on the consensus layer yet (usually it takes ~16 hours after the deposit is made). +
+
-
+
- + The following command generates the artifacts required to deploy a distributed validator on the Holesky network, using Teku as the validator client, Prysm as the consensus client, and Geth as the execution client. For additional supported client combinations, refer to the documentation here. + ```shell + sedge generate full-node --validator=teku --consensus=prysm --execution=geth --network=holesky --distributed + ``` + You should be shown a long list of configuration outputs with the following endings: + ```shell + 2024-09-20 12:56:15 -- [INFO] Generation of files successfully, happy staking! You can use now 'sedge run' to start the setup. + ``` + +
- + Explore the config files. + + You should now see a `sedge-data` directory created in the folder where you ran the `sedge generate` command. + To view the directory contents, use the `ls` command. + ```shell + ls sedge-data + > docker-compose.yml jwtsecret + ``` + + +