> 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/rocket-pool/validator-keys.md).

# Validator keys and your consensus client

How the Rocket Pool app keeps your validator keys loaded in Nimbus, Teku, Lighthouse or Prysm, and why it sometimes asks for your approval first.

Your Rocket Pool validators sign their work with **validator keys**. The keys are made on your AVADO when you create validators, and they run inside your **consensus client**: Nimbus, Teku, Lighthouse or Prysm, the same app that runs solo validators.

The Rocket Pool app takes care of this for you. **Every 5 minutes** it checks that:

* every key that belongs to one of your validators is loaded in your consensus client, and
* each key's **fee recipient** (where its block rewards go) is correct: the smoothing pool if you joined it, otherwise your megapool or your fee distributor.

Home shows the result under **Node health**, for example **Validator keys: 3/3 running in Nimbus**.

## Which consensus client

The app uses the client chosen in the package's settings (**CONSENSUSCLIENT** on the Rocket Pool page in the AVADO Admin). If that client isn't installed, Home says so and offers the DappStore. If the setting is empty and exactly one client is installed, that one is used.

Only one client runs your keys. If you want to switch to another client, install it, change the setting, and wait: the app never moves keys by itself (see below), so it will ask you to approve them in the new client once they are gone from the old one.

{% hint style="info" %}
The Nimbus and Teku apps show a reminder when Rocket Pool is installed: manage Rocket Pool validators in the Rocket Pool app, not there. Rocket Pool adds its keys back by itself, and a different fee recipient can cost you a penalty.
{% endhint %}

## When the app asks for your approval

Keys that the app made for a deposit it just sent are loaded straight away. Any other key that is **missing from every client** waits for your OK first, because loading a key that still runs somewhere else gets it slashed. That happens after:

* restoring a wallet with existing validators,
* removing a key from your client by hand,
* switching to another consensus client.

Home then shows **… validator key needs your approval** and a **Validator keys** card:

<figure><img src="https://2996176873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0YTdumceG05uJMtaEgaT%2Fuploads%2Fgit-blob-397c83d5f5f56d8ccc36d6fd903cd274793e8f27%2Frp-home-key-approval.jpg?alt=media" alt="Home: a banner saying 1 validator key needs your approval, and the Validator keys card with the key, a slashing warning and a Type LOAD to confirm field"><figcaption><p>Approving a key: read the warning, type LOAD, press the button.</p></figcaption></figure>

1. Make sure these validators are **not running anywhere else**: not on another machine, not with a staking service. If you moved them to another AVADO, don't load them here.
2. Type **LOAD** and click **Load … into …**.

A key the app has never seen in a client first gets a **20-minute safety wait**, and Home says when it will load. After that the key is loaded and starts validating. If it can't be loaded yet, the card says why, for example because another client on the AVADO couldn't be checked.

{% hint style="danger" %}
Never run the same validator key in two places. Slashing takes part of your ETH and forces the validator out for good.
{% endhint %}

## Messages you may see

<figure><img src="https://2996176873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0YTdumceG05uJMtaEgaT%2Fuploads%2Fgit-blob-7445d587d13c17e2fc91a72ddd4e93576652778a%2Frp-home-keys-attention.jpg?alt=media" alt="Home with four banners: a key loaded in two clients, keys needing approval, a key not running because Teku is too old, and a key that will start soon"><figcaption><p>Everything the key check can report, on one demo node.</p></figcaption></figure>

| Message                                                                | What it means and what to do                                                                                                                                                                                                              |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A validator key is loaded in two clients — this can get it slashed** | The key is in two consensus clients on this AVADO at once (for example Nimbus and Teku). The app never removes keys itself. Open one of the two clients in the AVADO Admin and remove the key there, now.                                 |
| **… validator key needs your approval**                                | See above.                                                                                                                                                                                                                                |
| **… validator key will start soon**                                    | Approved; waiting out the safety delay. Nothing to do.                                                                                                                                                                                    |
| **… validator key not running in …**                                   | Loading failed, or the key runs in another installed client. The app tries again every few minutes. If it says **Update …**, update that client package in the AVADO Admin first: an older version can't have keys loaded into it safely. |
| **Your validators have no consensus client**                           | The client in the package setting isn't installed, or no client is. Install one from the DappStore.                                                                                                                                       |
| **Block rewards may go to the wrong address**                          | The app couldn't set a key's fee recipient. It retries by itself; if it lasts more than an hour, contact <support@ava.do>.                                                                                                                |
| **Rocket Pool couldn't check your validators**                         | The last check failed, usually because the client or the Rocket Pool daemon didn't answer. It retries by itself.                                                                                                                          |

## The key check, in Advanced mode

Switch to **Advanced** (bottom left) and open **Advanced**. The **Validator key check** card shows the client, how many keys are loaded, how many fee recipients are correct, when it last ran and when it runs next. **Check now** runs it right away, for example after you fixed something.

## Moving a validator away from this AVADO

To run a Rocket Pool validator somewhere else, exit it or move the whole node: take a [backup](https://docs.ava.do/staking-ethereum/rocket-pool/wallet-and-backups.md), restore it on the new AVADO, then remove the keys from the old AVADO's consensus client, and only then approve them on the new one. Wait at least an hour between removing and approving.
