> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/staking-ecosystem-and-token-mechanics/staking/how-to-stake.md).

# How To Stake

**Step-by-Step Process:**

1. **Choose a Game:**
   * Browse game pools at staking.pixels.xyz.
   * Review metrics such as total staked, historical performance (APR), and payout schedules.
2. **Deposit Tokens:**
   * Stake your desired amount of $PIXEL directly into a chosen game.
   * No on-chain minimum; in-game auto-staking requires at least 100 $PIXEL and a login within the past 30 days.
3. **Receive Game Rewards:**
   * Each game distributes rewards periodically based on performance and total staked amount.
   * Rewards can be claimed as $PIXEL (with Farmer Fee) or fee-free as $vPIXEL.
4. **Managing Stake:**
   * Tokens can be unstaked at any time; there's a 3-day waiting period before withdrawal.
   * Restaking during the waiting period resets the withdrawal timer.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://litepaper.pixels.xyz/staking-ecosystem-and-token-mechanics/staking/how-to-stake.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.