> For the complete documentation index, see [llms.txt](https://earneo.gitbook.io/welcome-to-earneo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://earneo.gitbook.io/welcome-to-earneo-docs/staking/rno-staking.md).

# RNO Staking

Here you can discover how to buy and stake your RNO token

## RNO Token

RNO is a BEP20 token issued on the  [BNB Smart Chain.](https://bscscan.com/token/0x7F6EE7E043D12C2dE15E9B4Bb6bC0921e86361A9)&#x20;

RNO can be earned by watching videos on Earneo.Tube or the Earneo mobile App. \
They can also be purchased on various crypto exchanges. \
In the near future, Content Creators and Moderators will also be able to earn RNO.&#x20;

As Earneo constantly evolves, we will continue to create new ways to earn RNO and use it in the Earneo ecosystem.&#x20;

## Staking

Staking is a way for us to reward our community members for their long term mindset by giving an incentive to lock up their **RNO** tokens. By staking your RNO you’ll be able to earn RNO rewards once you lock up your tokens through the staking dashboard. In the future, staking RNO will give you access to certains features and rights on Earneo.Tube&#x20;


---

# 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://earneo.gitbook.io/welcome-to-earneo-docs/staking/rno-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.
