> For the complete documentation index, see [llms.txt](https://wiki.rly.network/rly-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.rly.network/rly-protocol/archived/rly-rewards/mature-phase.md).

# Mature phase

### Introduction

In the mature phase, applications are rewarded RLY in proportion to their contributions to the RLY Network. Contributions to the RLY network are defined by the following behaviors:&#x20;

* Proliferation of RLY and app tokens
* Active usage of RLY and app tokens
* Locking and staking of RLY

### Eligibility&#x20;

Currently only 1st & 2nd party applications and applications partnered with SuperLayer are eligible. Applications must have graduated from the Bootstrap phase by completing all milestones.&#x20;

### Total Weekly Distributions

The amount of RLY to be distributed is calculated based on the total RLY locked in all application economies. The more RLY locked in the RLY Network Ecosystem, the higher the RLY rewards pool.&#x20;

Total distribution of RLY for that week = Total RLY locked in all app economies \* 0.5% \* 7 days

Example: 90,000,000 RLY \* 0.5% \* 7 days = ​​ 3,150,000 RLY for that week

\*Maximum weekly distributions capped at 17,500,000 RLY / week by the Association

### Application allocations&#x20;

Applications will receive a score based on the weighted categories. Scores will provide the percentage of rewards apps will receive from the total weekly distribution amount. The weights are as follows

* Proliferation of RLY and app tokens (25%)
* Active usage of RLY and app tokens (35%)
* Locking and staking of RLY (40%)

### Reference

The full design can be found [here](https://docs.google.com/document/d/13VVTkeMFyWhx-G8lAWfCTU9kRBV-SA57cS0a0EKSUIs)


---

# 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://wiki.rly.network/rly-protocol/archived/rly-rewards/mature-phase.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.
