> 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/the-nimbus-app.md). # The Nimbus and Teku app Nimbus and Teku have a new, simpler app: see your validators, add keys, set your fee recipient, and fix problems with one click. From **Nimbus 0.0.51** and **Teku 0.0.77**, Nimbus and Teku have a new app. It is the same app for both, and it updates by itself. You don't need to do anything: your validator keys, slashing protection and settings stay as they are. {% hint style="info" %} Only Nimbus and Teku have the new app for now. Prysm and Lighthouse still look like the other guides on this site. The pictures below are from Nimbus; Teku looks the same. {% endhint %} ## Open the app Open **My DApps**, then click **Nimbus** or **Teku**. You can also click **Open in new tab** to use it full screen.
The Nimbus page in the AVADO Admin, showing the Nimbus app in the Setup tab

The Nimbus app inside its page in the AVADO Admin.

The Teku app: the Validators page with two validators and the status line at the top

The same app on Teku.

## Your validators The app opens on **Validators**. You see every validator on your AVADO, its status, its balance and where its rewards go.
The Validators page with two validators, the status line at the top and a No execution client installed message

The Validators page.

* **The line at the top** tells you how Nimbus or Teku is doing: **Synced** (all good), **Syncing** with a percentage, or a warning. * **A coloured message** shows when something needs your attention, with a button that fixes it. For example **No execution client installed** has an **Install an execution client** button. * Click the arrow next to a validator to see it on **beaconcha.in**. ## Add validators **1. Click Add validators** **2. Add your keystore files** Drop them on the box, or click **choose files**. The files are called `keystore-m_12381_3600_…json`. You can add many at once.
The Add validators page with one keystore file added

Each file shows the validator it belongs to.

**3. Type your keystore password** This is the password you chose when you created the keys. **4. Only if these validators ran somewhere else before:** add the **slashing-protection file** from that machine. **5. Click Import key** That's it. The validators show up on the **Validators** page. ## Set your fee recipient The fee recipient is the address that gets your block rewards (tips and MEV). Go to **Settings** and enter your address under **Default fee recipient**. Then click **Save changes**. The client restarts, which takes a minute or two.
The Settings page with Default fee recipient and Graffiti

Settings: default fee recipient, graffiti, execution client and MEV-Boost.

To use a different address for one validator, click **Fee recipient** next to it on the **Validators** page.
The Fee recipient window for one validator

Leave it empty to use the default.

{% hint style="warning" %} Always copy your address from your wallet. If you type it and make a mistake, the app tells you: **This address has a typo**. {% endhint %}
The Fee recipient window showing: This address has a typo: its capital letters don't match

The app catches typos in mixed-case addresses.

## Settings In **Settings** you can also: * Change your **Graffiti** (the short text shown with blocks you propose). * Choose your **Execution client** (Geth or Nethermind). The app shows which ones are installed. * Turn on **MEV-Boost**. Install the MEV-Boost app first. Click **Save changes** when you are done. ## Move a validator to another machine **1. Click Remove next to the validator**
The Remove window: the key is deleted from this node, it does not exit the validator

Removing a key does not exit your validator.

**2. Click Remove validator** Your browser downloads a **slashing-protection file**. Keep it: you need it on the new machine.
Key removed: wait at least 5 epochs, about 32 minutes, before you start this validator anywhere else

The app tells you how long to wait.

**3. Wait at least 32 minutes** Wait at least **5 epochs (about 32 minutes)** before you start the validator anywhere else. An hour is safer. {% hint style="danger" %} Never run the same validator on two machines at once. It gets slashed: you lose part of your stake and the validator is forced out. {% endhint %} **4. Import the keystore file and the slashing-protection file on the new machine** ## Exit a validator An exit is permanent. Read [Exit from a Solo Validator](/staking-ethereum/solo-staking-32-eth/exit-from-a-solo-validator.md) first. Click **Exit** next to the validator, type its number to confirm, then click **Exit validator**. The **Exit** button only shows for active validators.
The Exit validator window: an exit is permanent, type the validator index to confirm

Type the validator number to confirm.

## Rocket Pool If Rocket Pool is installed, the app reminds you: manage your Rocket Pool validators in the **Rocket Pool** app, not here. Rocket Pool adds its validators back by itself, and a different fee recipient can cost you a penalty. ## Advanced Switch to **Advanced** (bottom left) to see the **Advanced** page: start, stop or restart the client, check its processes and read its logs.
The Advanced page with Start, Restart and Stop buttons and the process status

The Advanced page. The logs are further down.

## Light or dark At the bottom left, choose **Light**, **Dark** or **Match computer**.