> 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/obol-dvt-package/testnet-holesky.md).

# Testnet (Holesky)

### Install the Obol Holesky package

Find the latest release of the Obol Holesky Dappnode package on [Github](https://github.com/dappnode/DAppNodePackage-holesky-obol/releases)

Click on "release details" and copy the IPFS hash.

Navigate to the `DAppStore` page and enter the IPFS hash, then click `Search`.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FW8kVTpyFyxLgGoz3g7hz%2Fimage.png?alt=media&amp;token=5cae3105-9ca2-4dcc-b6b8-f7b17e954fc5" alt=""><figcaption></figcaption></figure>

Under `ADVANCED OPTIONS` make sure the toggle for `Bypass only signed safe restriction` is on so that the package can be installed.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F426hAj4N9sbxeP83Vmhg%2Fimage.png?alt=media&amp;token=fb5de8ff-5c70-4c26-ae5c-ea0facd15bf3" alt="" width="563"><figcaption></figcaption></figure>

Skip all the questions during installation without filling out any fields.

After installation is finished, navigate to the Obol Package and click on the tab BACKUP.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F8pEPJx9rji0pUUHIkdTn%2FObol_Holesky.png?alt=media&amp;token=47eac7b3-25ee-4075-bda1-e600e2bd7272" alt=""><figcaption></figcaption></figure>

Click "Backup Now", which will download a file with a `.tar.xz` ending. Expand the file and you should see the following contents.

<div data-full-width="false"><figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FY8XAzKukbZH7RVn1LYE7%2FScreenshot%202024-07-15%20at%2019.09.48.png?alt=media&amp;token=c8080abe-7471-4ba4-b86c-6868b13d7c75" alt=""><figcaption></figcaption></figure></div>

Delete all files from the `charon1` directory. Now expand the keyshare file you received from ether.fi and put all the contents into the `charon1` directory.

Open the `cluster-lock.json` file and find the `operators` array and find your operator entry. The file you received will have the number of your node in the cluster. Keep in mind that the first node is node0, so node3 would be the fourth operator in the array for example.

Next, create a file called `enr` (just `enr` without a file ending).

Open the `enr` file in a text editor and paste your enr text from the operator array in the `cluster-lock.json`. Save the file and exit.

Your contents should now look like the following:

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F5drvW6s631AdMIoSwH4i%2FScreenshot%202024-07-15%20at%2019.12.41.png?alt=media&amp;token=e9033e6a-1d06-4701-93b7-1f2c19412f37" alt=""><figcaption></figcaption></figure>

Only `charon1` has changed. The other folders have to stay unchanged.

Now you have to pack all the charon folders back to a `.tar.xz` file. This is different on all OSs but on Linux and macOS, you can do the following in the Terminal:

```
cd directory-with-charon-folders
tar -cvf obol-backup.tar ./
xz obol-backup.tar
```

On macOS you might need to install the xz package with Homebrew: <https://formulae.brew.sh/formula/xz>

After those commands, you should see an `obol-backup.tar.xz`. You will need it in the next step.

Open the Dappnode interface again and go to packages. Make sure to start the package "Holesky Obol", as the containers should be stopped right now. You need to be fast with the next step, as otherwise the Obol package will exit again and you need to start it again before continuing.

Next, navigate to the Obol packages Backup tab.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F8pEPJx9rji0pUUHIkdTn%2FObol_Holesky.png?alt=media&amp;token=47eac7b3-25ee-4075-bda1-e600e2bd7272" alt=""><figcaption></figcaption></figure>

Click "Restore" and select your `obol-backup.tar.xz` you created just before. Restore from this file.

This should be it. If you notice any errors during Restore, start the obol package again and click restore again. It takes a few tries sometimes to get it right.

You can now check your Logs now and tell ether.fi that you finished the process.

And that should be it! The keyshare has been imported into your Holesky Obol Charon client and once your Testnet Holesky chains are synced, the validator will start to perform its duties 🥳


---

# 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/obol-dvt-package/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.