> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/rewards/overview.md).

# Rewards Overview

Onyx uses several reward concepts that should not be combined:

| Reward type                     | Recipient                                            | Where to verify                                     |
| ------------------------------- | ---------------------------------------------------- | --------------------------------------------------- |
| Liquid staking                  | stXCN holders                                        | Onyx App and Markets staking API                    |
| Protocol/native account staking | Eligible ledger accounts under current network rules | Network state and applicable protocol documentation |
| Validator/node rewards          | Eligible node operators                              | Validator dashboard and operator records            |

Liquid staking is a smart-contract product with owner-adjustable parameters. Validator rewards are a network/operator mechanism. A rate shown for one is not the rate for another.

Avoid fixed APY, validator-count, reward-budget, or USD examples. These values change and must be read from the relevant live source.


---

# 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.onyx.org/rewards/overview.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.