> For the complete documentation index, see [llms.txt](https://docs.ava.do/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ava.do/staking-ethereum/setting-up-the-eth-clients.md).

# Setting up the ETH Clients

## Overview

To begin, you need to install both the **Execution Client** and the **Consensus Client** on your AVADO machine. These two pieces of software work together to perform your validator duties.

During the initial setup, they will download and process all existing information from the Ethereum blockchain to ensure they have an accurate and up-to-date local copy of the Ethereum state. This process is known as "**syncing**".

The Consensus Client will need to sync up first, and this is a relative fast process that can complete within an hour. Syncing the Execution Client will take more time, usually a day or two, as it involves downloading and processing a substantial amount of data.

{% hint style="info" %}
**Prefer a guided walkthrough?**

The Admin's **Staking setup** page walks through installing the execution client, consensus client, validator keys, fee recipient, MEV-Boost and monitoring in order, with a progress checklist. You can use it instead of, or alongside, the steps below.

<img src="https://2996176873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0YTdumceG05uJMtaEgaT%2Fuploads%2Fgit-blob-4600b51da2242e5e1cb5ab52928a7c4204f92e67%2Fadmin-staking-setup.png?alt=media" alt="Staking setup, in the AVADO Admin sidebar" data-size="original">
{% endhint %}

{% hint style="info" %}
**Keep your device cool!**

During the initial sync of a blockchain, your system will operate at full capacity for multiple hours. It is crucial to maintain an optimal temperature to prevent any potential heat damage. If you are using the AVADO i7 model, which features a fan-less design with cooling fins, we recommend using a USB fan to provide additional cooling support during this initial sync process. This will help ensure that your system stays cool and operates efficiently throughout the syncing period.
{% endhint %}

## Step 1: Install Execution Client

Choose ONE of the following. Open **DappStore** in the sidebar, search for it under the **ETH Staking** category, and click **Install**.

<figure><img src="https://2996176873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0YTdumceG05uJMtaEgaT%2Fuploads%2Fgit-blob-87c8a9ab7bfde8b6e4f99631994427f0ffbf5987%2Fadmin-dappstore.png?alt=media" alt=""><figcaption><p>DappStore. Scroll to the ETH Staking category to find Geth, Nethermind, Teku, Prysm and Nimbus.</p></figcaption></figure>

{% tabs %}
{% tab title="Nethermind" %}
Nethermind is a high-performance, highly configurable Ethereum execution client built on .NET

Search for **Nethermind Execution Client** in the DappStore and click **Install**.
{% endtab %}

{% tab title="Geth" %}
Geth is the Ethereum node software coded in Go language. It is widely used and well-maintained.

Search for **Geth Execution Client** in the DappStore and click **Install**.
{% endtab %}
{% endtabs %}

After installing the Execution Client, it will automatically start running, but it won't be able to sync until a Consensus Client is installed and synced. This will be our the next step.

Once installed, the client shows up on **My DApps** and on the **Home** page, where you can track its status alongside your other apps.

<figure><img src="https://2996176873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0YTdumceG05uJMtaEgaT%2Fuploads%2Fgit-blob-9afd46733655f26475537782acab8c85e6cc55f9%2Fadmin-my-dapps.png?alt=media" alt=""><figcaption><p>My DApps — installed apps, with status, Open/Manage links, restart and auto-update controls</p></figcaption></figure>

## Step 2: Install Consensus Client

Choose ONE of the following. Search for it in the **DappStore**, under the **ETH Staking** category, and click **Install**.

{% tabs %}
{% tab title="Teku" %}
Teku is an open source Ethereum consensus client written in Java.

Search for **Teku Consensus Client** in the DappStore and click **Install**.

Introducing **Zero Sync** mode for Teku! This feature enables validation from a backup Beacon Chain provided by AVADO, eliminating the initial sync wait time and reducing downtime during errors or maintenance. We highly recommend setting up Zero Sync now. Check out [**Teku Zero Sync**](/quick-help/teku-zero-sync.md) for more details.
{% endtab %}

{% tab title="Prysm" %}
Prysm is a popular Ethereum proof-of-stake client written in Go.

Search for **Prysm Consensus Client** in the DappStore and click **Install**. This will also automatically install the **Prysm Beacon Chain** package.

Unlike Teku and Nimbus, Prysm consists of two separate packages: one for the Beacon Chain and another for the Validator. On **My DApps**, you will notice two installed Prysm packages:

* **Prysm Consensus Client** - This is the Validator Client.
* **Prysm Beacon Chain** - This is the Beacon Chain Client and the new AVADO wizard.
  {% endtab %}

{% tab title="Nimbus" %}
Nimbus is an extremely efficient consensus layer client implementation.

Search for **Nimbus Consensus Client** in the DappStore and click **Install**.
{% endtab %}
{% endtabs %}

## Step 3: Configure the Consensus Client

At this stage, you'll need to configure the Consensus Client. The configuration options are the same across Teku, Prysm or Nimbus. Please proceed to our guide on [Configuring the Consensus Client](/staking-ethereum/setting-up-the-eth-clients/configuring-the-consensus-client.md).

* [**Configuring the Consensus Client**](/staking-ethereum/setting-up-the-eth-clients/configuring-the-consensus-client.md)

Once you've configured the options, you can continue below to complete the syncing process.

## Step 4: Syncing the Consensus Client

The Consensus Client will need to sync up first. Thanks to **Checkpoint Sync**, the Consensus Clients start with a recently finalized checkpoint state and only need to catch up to the current head of the blockchain. This process is relatively fast, usually taking **only a few minutes to no more than an hour**.

Please see our detailed guides on the syncing process. These guides will assist you in monitoring and ensuring a smooth progression of the process.

* [**Nimbus**](/staking-ethereum/setting-up-the-eth-clients/syncing-the-consensus-client/nimbus.md)
* [**Prysm**](/staking-ethereum/setting-up-the-eth-clients/syncing-the-consensus-client/prysm.md)
* [**Teku**](/staking-ethereum/setting-up-the-eth-clients/syncing-the-consensus-client/teku.md)

## Step 5: Syncing the Execution Client

Syncing the Execution Client is the process by which the it catches up to the latest Ethereum block and synchronizes its global state. It is a time-consuming process, typically taking **many hours to a few days** depending on your network speed. It's important to be patient during this period.

Please see our detailed guides on the syncing process. These guides will assist you in monitoring and ensuring a smooth progression of the process.

* [**Geth**](/staking-ethereum/setting-up-the-eth-clients/syncing-the-execution-client/geth.md)
* [**Nethermind**](/staking-ethereum/setting-up-the-eth-clients/syncing-the-execution-client/nethermind.md)

## Next Steps

Congratulations for setting up your Ethereum node!

Now that you have the basic infrastructure in place, you can proceed to the actual staking. Please follow our comprehensive guides for each option:

* [**Solo Staking**](/staking-ethereum/solo-staking-32-eth.md)
* [**Rocket Pool**](/staking-ethereum/rocket-pool.md) — about 4 ETH per validator.

{% hint style="danger" %}
Stader is deprecated and no longer offered as a staking option. See [Stader (4 ETH)](/staking-ethereum/stader-4-eth.md) only if you already have a Stader validator to exit.
{% endhint %}

Happy Staking!