> For the complete documentation index, see [llms.txt](https://docs.aavegotchi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aavegotchi.com/own/earning-in-aavegotchi/staking.md).

# Staking

### What is Staking? <a href="#what-is-staking" id="what-is-staking"></a>

Staking in Aavegotchi involves locking up your cryptocurrency, specifically the native token GHST, in various staking contracts to earn rewards.

The primary rewards for staking GHST are [GAX Liquidity Token Rewards (GLTR)](/own/tokens/gltr-token.md). These GLTR tokens can be used in the Gotchiverse to speed up the crafting and upgrading of Installations, allowing players to progress faster in the game. Additionally, GLTR can be burned to speed up the time for Forging.

In addition to the above, more usecases are being developed for GLTR token and will be announced in the future.

### How to Stake <a href="#how-to-stake" id="how-to-stake"></a>

To stake GHST, you can visit the [Staking](https://dapp.aavegotchi.com/staking?p=gltr) page, where you'll find seven staking pools:

* wapGHST
* GHST-FUD
* GHST-FOMO
* GHST-ALPHA
* GHST-KEK
* GHST-USDC
* GHST-GLTR.

GHST-MATIC also appears on the list, but its rewards have been reduced to zero.

After depositing tokens into these pools via Quickswap or other decentralized exchanges, you'll receive LP tokens, which can then be staked in the Aavegotchi DApp.

The staking process not only offers rewards but also contributes to the alignment of the AavegotchiDAO, GHST holders, and Aavegotchi NFT holders' goals, fostering a sustainable ecosystem.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aavegotchi.com/own/earning-in-aavegotchi/staking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.