> For the complete documentation index, see [llms.txt](https://docs.gyro.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gyro.win/beginners-guide/what-is-staking.md).

# What is staking?

In the cryptocurrency world, staking is a method of earning rewards by holding specific cryptocurrencies for a set period to support the ecosystem’s operations.

Staking functions similarly to depositing money into a savings account at a bank: the bank lends out your deposits, and you earn interest on your balance.

However, unlike savings accounts, non-stable coins can experience price fluctuations. This means you may incur a loss if the coin’s value declines more than the rewards earned through staking.

For example:

* Non-stable coins: BTC, GYROWIN, ETH, etc.
* Stable coins: USDT, USDC, FDUSD, etc.

Staking can provide substantial returns but carries risks due to the potential volatility of non-stable coins.


---

# 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://docs.gyro.win/beginners-guide/what-is-staking.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.
