# Manage Stakings

After adding your GPUs to the platform, you need to stake your GPU before it can generate earnings for you. 

Two staking options are provided.

* **Quick Staking**: default staking configurations, setting all stakeholders as the Cloud Hosts.
* **Advanced Configurations**: allowing customisation of different roles.

You can find the tutorials to acquire ATH tokens [here](/aethir-tokenomics/how-to-acquire-ath.md).

{% hint style="warning" %}
**Make Sure GPUs Are Ready To Stake**

Please make sure the GPUs have the expected specifications and are ready for service before staking. **Any hardware modifications after this step will require re-onboarding.** Incorrect details or GPU downtime may result in [slashing](/staking-and-rewards-for-cloud-host-compute-providers/slashing-mechanism.md) penalties. 
{% endhint %}

### Stakeholders and Groups

Cloud Hosts can group GPUs into **Staking Groups**, each identified by a unique **Group ID (GID)**. Within each Group, several roles control the activities that can be performed on the GPUs. These roles are considered **Stakeholders**:

* **Staker**: Can perform staking and unstaking operations. 
* **Reward Receiver**: Can claim rewards generated by the GPUs.
* **Service Fee Receiver**: Can claim service fees.

Cloud Hosts cannot perform activities outside of their assigned roles, but can always initiate unstaking. Stakeholders can manage the Groups assigned in the [**Stakeholder Portal**](/aethir-cloud/aethir-cloud-host/cloud-host-portal-guide/stakeholder-portal.md).

### Quick Staking

Quick Staking offers an easy way to engage in staking, with Cloud Hosts as the default entity for staking, unstaking, and claiming earnings. Users can later reassign the Service Fee Receiver and Reward Receiver.

#### Quick Staking Steps

1. **Select GPUs to Stake**
2. **Confirm Staking Details**
   * Review the list of GPUs and the amount to be staked.
   * Additional GPUs can be added at this step.
3. **Sign with Wallet to Stake**
   * Complete the staking process by signing the transaction with your wallet.

#### Modifying Configurations

All GPUs performed Quick Staking will be shown on the Staking page under the ***Default-Group***. After staking, users can modify the details of the Group.

* **Set Receiver**: Modify **Reward Receiver** and **Service Fee Receiver**
* **Change Group Name**: Update the Group's name.
* **Connect GPUs**: Add more GPUs to the Default Group. To stake the added GPUs, please refer to [**Staking & Unstaking Within or Across Group**](#staking-and-unstaking-within-or-across-group). To remove non-staked or unstaked GPUs from the Default Group, please refer to [**Removing GPUs from Group**](#removing-gpus-from-group).

 

### Advanced Staking

Advanced Staking uses **Groups** to implement sophisticated role management. Cloud Hosts can create Groups and assign roles by selecting the **Advanced Staking** option. Cloud Hosts can modify configurations and, if assigned as the **Staker**, perform Staking and Unstaking operations individually or in bulk.

#### Start Advanced Staking

1. **Select the Staker**
   * Choose who will perform stakings for all GPUs in the Group.
   * This cannot be changed once any GPUs in the Group has been staked.
2. **Set Up Reward Receiver and Service Fee Receiver**
   * Define the wallet addresses for the **Reward Receiver** and **Service Fee Receiver**.
   * Alternatively, delegate this decision to the Staker if it is not the Cloud Host.
3. **(Optional) Name Your Staking Group**
   * Assign a custom name to the Staking Group. If unassigned, the default name will be the Group ID allocated to the Group followed by the date of creation.
4. **Add GPUs to the Group**
   * Include the GPUs to the Group for bulk management.
5. **Sign with Wallet.**
   * Confirm the transaction with the cryptowallet connected to the Cloud Host account.
6. **Check the Group Status on the Staking Page**
   * On the Stakings main page, a Group with your preferred configuration is created. You may notice the Group in two intermediate statuses before the configuration confirmation is successfully processed on chain.
     * **Pending**: The transaction is awaiting on-chain authorization.
     * **Failed**: The transaction timed out after 10 mins of non-authorisation. Or it has been rejected or failed. Retry or delete the Group if needed.

#### Staking & Unstaking Within or Across Group

GPUs must be staked before they can earn ATHs on the platform. Once staked, the status of each GPU will update to **Staked**. Staked GPUs cannot change Groups unless they are **unstaked**.

* **Individual Staking/Unstaking**: 
  1. Click the **Stake/Unstake** button in the GPU entry.
  2. Authorise the staking/unstaking in your cryptowallet.
* **Bulk Staking/Unstaking**:
  1. Select multiple GPUs by ticking the checkboxes.
  2. Click the **Stake/Unstake** button in the floating toolbar at the bottom of the page.
  3. Authorise the staking in your cryptowallet.

Note: Cloud Hosts can unstake all staked GPUs but can only stake GPUs for which they are the Staker.

#### Modifying Group Configurations

Cloud Hosts can modify Group configurations at any time, with the following options:

* **Set Stakeholder**: Modify stakeholders if no GPUs are staked in the Group.
* **Set Receiver**: Modify **Reward Receiver** and **Service Fee Receiver** when any GPUs are already staked.
* **Change Group Name**: Update the Group's name.
* **Connect GPUs**: Add more GPUs to the Group.

#### Removing GPUs from Group

Cloud Hosts can remove non-staked or unstaked **GPUs** from a Group. Once removed, the GPU can be reassigned with different stakeholders.


---

# Agent Instructions: 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:

```
GET https://docs.aethir.com/aethir-cloud/aethir-cloud-host/cloud-host-portal-guide/manage-stakings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.