> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/dappnode-setup/ethereum-validator-clients/testnet-holesky.md).

# Testnet (Holesky)

{% hint style="warning" %}
While the Dappnode machines have a large enough SSD to hold both Mainnet and Testnet Ethereum chains, you will have lower performance if you try to run both chains simultaneously.

If you are already running a Mainnet chain, it is best to [pause those packages](/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/dappnode-setup/additional-configuration.md#remove-or-pause-packages) if you want to use a Testnet chain (e.g. Holesky). If you are running a Mainnet validator, pausing the Mainnet chain will stop that validator from performing its duties!
{% endhint %}

Once you have your Dappnode machine set up, the next step is to install the Holesky Testnet packages and begin syncing the chain.

### Install Testnet Validator Clients

Navigate to the `Stakers` menu and select the `Holesky` tab.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2Fr6cFFVpIqFp30Ui8GlXy%2FStaker_Holesky.png?alt=media&amp;token=b505159d-9f11-44fe-9c12-19f3cc07786f" alt=""><figcaption></figcaption></figure>

Select one Execution Client, one Consensus Client, and MEV Boost.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FKPypCYDXIVeMfceUNOsR%2Fimage.png?alt=media&amp;token=851f74bf-c197-4de7-8260-3307dfa25026" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/dappnode-setup/ethereum-validator-clients/testnet-holesky.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.