# Techne Bronze Speedrun (CLI) ## Requirements Obol Techne Bronze Credentials require node operators to run 50 testnet validator keys as a distributed validator cluster for 3 weeks, where Obol will fund the testnet ETH required to activate the validator keys. {% hint style="warning" %} Obol encourages DVT operators to contribute 1% of their staking rewards to their [retroactive funding program](https://obol.org/contributions) (RAF) which supports the decentralisation of Ethereum. This CLI flow bypasses the RAF mechanism so only use this method if really needed. {% endhint %} ### Hardware (Holesky) * CPU: 4 cores * RAM: 16GB * SSD: 350GB * OS: Ubuntu 24.04 ## Set up Splitter contract Choose your cluster members and form your cluster members by creating a Splitter contract that splits the execution layer rewards among all operators. {% embed url="" %} ## Install dependencies Install Docker. ```sh curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh sudo groupadd docker sudo usermod -aG docker $USER ``` Exit and re-login. ```sh exit ``` ## Generate your Obol ENR ```sh cd # Use docker to create an ENR. Backup the file `.charon/charon-enr-private-key`. docker run --rm -v "$(pwd):/opt/charon" -u $(id -u):$(id -g) obolnetwork/charon:v1.1.0 create enr ``` You should expect to see a console output like this: ``` Created ENR private key: .charon/charon-enr-private-key enr:-JG4QGQpV4qYe32QFUAbY1UyGNtNcrVMip83cvJRhw1brMslPeyELIz3q6dsZ7GblVaCjL_8FKQhF6Syg-O_kIWztimGAYHY5EvPgmlkgnY0gmlwhH8AAAGJc2VjcDI1NmsxoQKzMe_GFPpSqtnYl-mJr8uZAUtmkqccsAx7ojGmFy-FY4N0Y3CCDhqDdWRwgg4u ``` Save the `ENR public key` in a text file on your laptop. You will need to use this in the next section. The `ENR public key` is denoted as `enr:-JG4QGQpV4qYe32QFUAbY1UyGNtNcrVMip83cvJRhw1brMslPeyELIz3q6dsZ7GblVaCjL_8FKQhF6Syg-O_kIWztimGAYHY5EvPgmlkgnY0gmlwhH8AAAGJc2VjcDI1NmsxoQKzMe_GFPpSqtnYl-mJr8uZAUtmkqccsAx7ojGmFy-FY4N0Y3CCDhqDdWRwgg4u` in the example output above. ### Restarting from scratch If you want to redo the whole process, remove the existing `charon-distributed-validator-node` folder before re-running the set of commands above. ```sh cd sudo rm -r .charon ``` ## Create the Cluster Definition file Appoint a cluster leader among your cluster. The cluster leader will collect everyone's `ENR public key` and run the following command. **Replace:** * `--name` flag with your choice of name for your cluster * `--fee-recipient-addresses` flag with your cluster's actual `Splitter contract address` * `--operator-enrs` flag with the actual `ENR public key` of your cluster members 
cd
docker run --rm -v "$(pwd):/opt/charon" -u $(id -u):$(id -g) obolnetwork/charon:v1.1.0 create dkg \
--name="<Cluster_name>" --num-validators=50 \
--fee-recipient-addresses="<Splitter_contract_address>" \
--withdrawal-addresses="0x17E6F6270A101dc7687Cc9899889819EeAF8253f" \
--network="holesky" \
--operator-enrs=\
"enr:-HW4QO5ci0ykiIxKD9CPoK0DzqrtV85jaXRgHeUKJyX8KmAhOxe5lD5MBGTNf9vJClUIeLzqj9awJtXsxWGciTI8BgSAgmlkgnY0iXNlY3AyNTZrMaEDivyOXAZbkL8sqbSuCQ0NBa3qiGxgrU_3pda02C1A0HQ",\
"enr:-HW4QFOFj99TaauvirkSRmEphR1UkevkegYJYkBzzLK3b2kwLmEHxE_E8q_BTJY0pN1vIBPq4rZ2Kih-K11MOAC6VimAgmlkgnY0iXNlY3AyNTZrMaECV0SXHBiWDjucuAdRPbJA19ExP73EvDlYJGEwyr4fYZY",\
"enr:-HW4QFRRhXE1aBufxYYqXLp5_QTCpAmct6UsKt-MMqbaNNCcNpVMC-icRYwAwXalh0Y2cIIhVocLVRPcZSQrev8osJyAgmlkgnY0iXNlY3AyNTZrMaECerwvVkvu8ZM_vALT10Rtp0YiFth7R5JrqP-iTmXwzAk",\
"enr:-HW4QIq63_axsvYq3D24gcZSFTKjrSl0nWwXVeYc29mJV-avEzVMKUcaxjM9wYnz4GWIT4JQqASJfu6M-HK5RH-zE8aAgmlkgnY0iXNlY3AyNTZrMaEDafXZh594s4ft5El40JmGt1qVsOdW5gv2qzaVtC2LTLc"
{% hint style="info" %} Keep the `--withdrawal-addresses flag` as is because we want Obol to fund our testnet validators. {% endhint %} A `cluster-definition.json` file will be generated and saved in the `~/.charon` directory. Distribute this `cluster-definition.json` file to each cluster member to place within their own `~/.charon` directories. {% hint style="info" %} You can use any messaging app for this because only the public part of the ENR key is exposed in this file. {% endhint %} ## Run the DKG ceremony ```sh cd docker run --rm -v "$(pwd):/opt/charon" -u $(id -u):$(id -g) obolnetwork/charon:v1.1.0 dkg --publish ``` {% hint style="info" %} All cluster members need to run the DKG service within 30 minutes of one another and keep it running until the ceremony is complete. {% endhint %} Once the DKG ceremony is completed, **back up the `.charon` folder containing the following important files:** * charon-enr-private-key * cluster-lock.json * cluster-definition.yml * validator\_keys/ * deposit-data.json **Back up using one of the 2 methods below.** {% tabs %} {% tab title="secure copy" %} This is the most secure method but requires having SSH access to your server from your laptop's terminal (i.e., after manually adding SSH public keys to your server). ```sh scp -i PATH_TO_SSH_PRIVATE_KEY -r USER@EXTERNAL_IP_ADDRESS:~/.charon $HOME/Documents ``` Your .charon folder will now be found on your laptop's `Documents` folder. Note that `.charon` is a hidden folder so you will not see it being displayed in your file system. {% endtab %} {% tab title="base64" %} This is an alternative method if you have not set up SSH access to your server from your laptop's terminal. It is less secure as you will expose your files temporarily on your terminal. * Zip up the .charon folder and convert the zipped file into a base64 string. Then print out the resulting contents. ```sh sudo tar -czvf - $HOME/.charon | base64 > dot_charon.tar.gz.b64 cat dot_charon.tar.gz.b64 ``` * Copy the entire output carefully and save it in a text editor on your laptop. * Clear your terminal and remove the bash history of your server to minimise exposure of these important files ```sh clear history -c ``` #### Restoring the files To restore base64 encoded files, we basically need to reverse the process above. Convert the base64 string back into a zipped file and then unzip the resulting archive. ```sh base64 -d dot_charon.tar.gz.b64 > dot_charon.tar.gz tar xvf dot_charon.tar.gz ``` The `.charon` folder will be found in the folder you ran the above command in. Run `ls -la` to see it. {% endtab %} {% endtabs %} Then, set the following permissions. ```sh sudo chmod +x ~/.charon sudo chmod 755 ~/.charon sudo chmod 600 ~/.charon/charon-enr-private-key ``` ## Set up ETH Docker Each cluster member needs to spin up a "vanilla" validator node. {% content-ref url="/pages/c8hStsV6JG56qLSk8fhB" %} [ETH Docker](/automation-tools/eth-docker.md) {% endcontent-ref %} **Changes to note:** * Set the `Reward Address` to your cluster's Splitter contract. ### Edit the configuration file Edit the `.env` file in the `eth-docker` folder. ```sh cd nano ~/eth-docker/.env ``` * Append `:lido-obol.yml` in the `COMPOSE_FILE` line. **Example:**
* Change the `CL_NODE` line to **** (from ) **Example:**
`CTRL+O`, `ENTER`, `CTRL+X` to save and exit. ## Start your Obol-enabled validator node Migrate .charon contents into ETHDocker. ```sh cd sudo cp -r .charon/* eth-docker/.eth ``` Start ETH Docker. ```sh ethd up ``` After all your services running via Docker "warmed up" for \~5 minutes, import your validator key shards. ``` ethd keys import ``` ## Monitoring Charon Print Obol's Charon logs. ```sh ethd logs charon -f --tail 20 ``` Other monitoring commands under "View Logs" section of the overall ETH Docker page. {% content-ref url="/pages/c8hStsV6JG56qLSk8fhB" %} [ETH Docker](/automation-tools/eth-docker.md) {% endcontent-ref %} ### Grafana Dashboards Open up a browser webpage and enter the following URL. ``` http://:3000 ``` * Enter **"admin"** for both the username and password. * Navigate to `Dashboards`. The 2 most common dashboards when running Obol DVTs are `Charon Log Dashboard` and `Charon Overview` ## Register your cluster for funding Cluster leader to fill up the Obol Techne Credentials registration form [here](https://airtable.com/apphbfJ552v5mHpo4/pag7JX1gSNIMzvELA/form). Copy and paste the `cluster-lock.json` and `deposit-data.json` files from your node to a text editor your laptop so that you can upload them easily onto the form. ```sh sudo cat ~/.charon/cluster-lock.json ``` ```sh sudo cat ~/.charon/deposit-data.json ``` ## Add Obol monitoring credentials You will receive your monitoring credentials after registrering your cluster with Obol Techne Credentials Progamme and you will need to add it into your ETH Docker configuration. Open up the `obol-prom.yml` file for editing. ```sh nano ~/eth-docker/prometheus/obol-prom.yml ``` Replace the `credentials` field with your actual monitoring credentials.

e.g., Replace OBOL_PROM_REMOTE_WRITE_TOKEN

`CTRL+O`, `ENTER`, `CTRL+X` to save and exit. Copy the contents over into the `custom-prom.yml` file that is empty by default but already incorporated in the default ETH Docker configurations. ```sh cp ~/eth-docker/prometheus/obol-prom.yml ~/eth-docker/prometheus/custom-prom.yml ``` Then, restart your ETH Docker services. ```sh ethd down ethd up ``` ## Securing your device ### Firewall Rules ```sh sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow 22/tcp # for SSH sudo ufw allow 30303 # for the EL sudo ufw allow 9000 # for the CL sudo ufw allow 3000 # for the native Grafana sudo ufw allow 3610 # for Obol P2P sudo ufw enable ``` Make sure to also configure port forwarding on the ports allowed above. {% content-ref url="/pages/tbZ1z2fKwHTUGm4dNmFj" %} [Advanced networking](/tips/advanced-networking.md) {% endcontent-ref %} ### Other Security SOPs {% content-ref url="/pages/0cy4sNAS3WVzQgOT6Iaj" %} [Networking & network security](/linux-os-networking-and-security/networking-and-network-security.md) {% endcontent-ref %} {% content-ref url="/pages/7JHbPUcfxcSFhooQGjlF" %} [Device level security setup](/linux-os-networking-and-security/device-level-security-setup.md) {% endcontent-ref %} ## Support {% embed url="" %} ## Donations #### If you found this helpful, consider supporting Stakesaurus in one of few ways [here](https://dvt-homestaker.stakesaurus.com/#if-you-found-this-helpful-consider-supporting-stakesaurus-in-one-of-two-ways-below)! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dvt-homestaker.stakesaurus.com/dvt-setup/obol/techne-bronze-speedrun-cli.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.