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

# 🔒 RICO Staking System

### <mark style="color:$primary;">Why staking exists</mark>

Staking is designed to:

* reward long-term holding
* discourage short-term exits
* strengthen token retention
* create productive utility for holders
* and align long-term participants with ecosystem growth

### <mark style="color:$primary;">Core Design</mark>

Users stake RICO for fixed periods and earn rewards based on duration.

#### Available Lock Durations

* **30 days**
* **180 days**
* **365 days**

Longer lock durations are designed to offer stronger reward potential.

### <mark style="color:$primary;">Strategic Purpose</mark>

The staking layer helps transform RICO from a simple utility token into a longer-duration ecosystem asset.

That matters because:

* staked supply may reduce liquid market pressure
* longer-duration users become more aligned with growth
* compounding can strengthen retention behavior

<mark style="color:$success;">Next: 📈 APY, Bonuses & Penalties</mark>


---

# 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:

```
GET https://rico-matrix.gitbook.io/whitepaper/rico-staking-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.