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

# Staking

Staked tokens will be eligible to receive their portion of rewards.

We at Nuvola believe that you should always have access to your funds at all times, so we opted for non-custodial and liquid staking (no lock-ups). With our non-custodial, liquid staking model, you maintain control of your assets and benefit from our network’s growth.

Staked tokens will accrue their rewards based on active time staked. This will be tracked via our staking portal.&#x20;

* Staking is 100% liquid with no lock periods.
* You start earning rewards from day 1, rewards accrue daily at 00.00 UTC.
* To be eligible to retain/claim your rewards, you will need to stay staked for a min. of 14 days *(unstaking before 14 days will make you ineligible, your rewards will be added back to the rewards pool for stakers).*

Please read our Medium article to learn more about the staking process.&#x20;

{% embed url="<https://nuvoladigital.medium.com/nvl-staking-all-you-need-to-know-e6507392c801>" %}


---

# 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.nuvoladigital.io/nvl-utilities/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.
