> 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/avado-setup/ethereum-validator-clients/mainnet.md).

# Mainnet

{% hint style="warning" %}
While the Avado 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 Testnet chain (e.g., Goerli), it is best to [remove or pause those packages](/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/avado-setup/additional-configuration.md#remove-or-pause-packages).
{% endhint %}

Once you have your Avado machine set up, the next step is to install the Teku and Nethermind packages and begin syncing the chain.

{% hint style="info" %}
For the hardware specs used by the Avado machines in this first trial, the best clients to use are Teku and Nethermind. Luckily they are also [minority clients](https://clientdiversity.org/), so +1 for client diversity 🥳
{% endhint %}

### Install Nethermind and Teku Clients

Navigate to the `DappStore` menu and look for `Ethereum execution client (Nethermind)` and `Ethereum Validator + Beacon Chain (Teku)`.

{% hint style="info" %}
The search feature didn't work for me, so you can just use the browsers search function, or look down the list manually 👀
{% endhint %}

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2Fa8wIy6BimdSYntJCWKun%2Fimage.png?alt=media&amp;token=d49b94ef-3dff-4c90-969d-9a7232503179" alt=""><figcaption><p>Avado Dappstore</p></figcaption></figure>

### Configure Teku

By default on Avado machines, Teku is configured to use Geth. Since we are using Nethermind as our Execution Client, this needs to be changed.

Navigate to the `My DApps` menu and click the `Open` button for `Teku`.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FykI6Aawi5bSp6yODngcx%2Fimage.png?alt=media&amp;token=f9861a34-9c2c-4465-9d47-e5309fab6bd5" alt=""><figcaption></figcaption></figure>

The Teku configuration will open on a new page. Click the `Settings` menu.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FBJ6pma4nXNqyeEbn5iBW%2Fimage.png?alt=media&amp;token=e4730c81-62ff-41d9-b47d-d5d5cb601012" alt="" width="563"><figcaption></figcaption></figure>

Change the `Execution Engine` to `Nethermind` and then `Apply changes`.

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2Fhsjd7E3Dkqx3Ji6SqWdb%2Fimage.png?alt=media&amp;token=363d0d72-53f7-4adc-a106-f529a90b50dd" 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 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/obol-dvt-explained/avado-setup/ethereum-validator-clients/mainnet.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.