> 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/ssv-explained/holesky-dappnode-setup.md).

# Holesky Dappnode Setup

Now that you created your SSV Operator you need to run it alongside a Holesky node.

This guide explains how to set up an SSV Node on Dappnode OS.

## 1. Sync your Holesky Node

The first step is to sync a Holesky Node and activate MEV Boost. Go to your Staker Tab, go to Holesky the Holesky tab on the top. Select an Execution Client - all but Reth work with SSV at the time of writing, a consensus client and Mev Boost Holesky.

Select all Relays on MEV Boost.

<figure><img src="/files/8cLMBqzv3x6oNl5rh6br" alt=""><figcaption></figcaption></figure>

Click on "Apply Changes" to save your Staker setup. Go back to the Dashboard, you should now see your Holesky clients in the overview starting to sync.

You can wait for your node to sync or continue with the next step right away.

## 2. Run the Holesky SSV Node

Your next step is to install the SSV Holesky package on your Dappnode.

### Option 1: DAppStore

Go to the DAppStore and click on the "SSV Holesky" package. It should be one of the first in the Dnp section.

<figure><img src="/files/GOAns4Vkoosrjzb33F3N" alt=""><figcaption></figcaption></figure>

### Option 2: IPFS Search

If you cannot see the SSV Holesky Package here, go to the official [Dappnode SSV package on Github](https://github.com/dappnode/DAppNodePackage-ssv-generic/releases) and check the releases. Check which release has the tag "latest" and click on "Release details". This image is just an example, use the "latest" release.

<figure><img src="/files/37ReaInXJAmJDNUZAZAP" alt=""><figcaption></figcaption></figure>

Go back to your Dappnode UI and go to the DAppStore.

Copy the ipfs hash from "SSV Holesky" and insert it in the DAppStore Search bar and press Enter. The search itself is not very reliable and you will usually not find a result. The DAppStore should load the hash now directly.

If the Package doesn't load, try again. The ipfs search is sometimes a bit unreliable and sometimes you have to try several times. Also consider asking for help in the Dappnode Discord if the problem persists, sometimes you need to fix your ipfs package.

<figure><img src="/files/PFRhixHqPnQfCDJywe5R" alt=""><figcaption></figcaption></figure>

## Install SSV Holesky

When you have found the SSV Holesky package, click on Install.

<figure><img src="/files/8RCdJNvqQ8V66I3IsWYK" alt=""><figcaption></figcaption></figure>

1. For Setup mode select "Import Operator".
2. Set Builder Proposals to true.
3. Upload the encrypted private key file you created in the previous guide.
4. Enter the password that you created for the private key in the previous guide.

<figure><img src="/files/Jete1whoADQ9R0rPBs5v" alt=""><figcaption></figcaption></figure>

Click on "Submit". SSV Holesky should be installed now.

<figure><img src="/files/GdaZyR7R8I9G5RRfFl3N" alt=""><figcaption></figcaption></figure>

That's it - wait for a couple of minutes and check if SSV Holesky is running. Let the Etherfi team know that your operator is ready.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/ssv-explained/holesky-dappnode-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.