# Aureus (AUREUS)

AUREUS is a limited token, with a maximum supply of 21,000,000 that will be distributed to metaverse users over the course of 10 years. 50% (10,500,000) of the AUREUS will be reserved for WAX users of Farming Tales, stakeholders of SEST (40%) and CBIT (10%).

| YEARS | SEST      | CBIT      |
| ----- | --------- | --------- |
| 1     | 4,200,000 | 1,050,000 |
| 2     | 2,100,000 | 525,000   |
| 3     | 1,050,000 | 262,500   |
| 4     | 525,000   | 131,250   |
| 5     | 262,500   | 65,625    |
| 6     | 121,250   | 32,812.50 |
| 7     | 65,625    | 16,406    |
| 8     | 32,812.50 | 8,203.19  |
| 9     | 16,406.25 | 4,101.56  |
| 10    | 8,203.13  | 2,050.78  |

AUREUS is airdropped directly into the stakeholder wallets once a week, according with the amount of SEST or CBIT in stake.

Remaining AUREUS can be released in different ways:

* 10% via stake of $ REBUS or $ LUDUS on the Rebus (Cosmos) blockchain
* 10% through dedicated activities on the Solana blockchain
* 10% reserved for listing on a CEX
* 20% future events and partnerships

AUREUS is meant to be the token of the metaverse, and all activities within New Waxchester will be paid or rewarded thanks to it. In our plans this should be a great advantage for Farming Tales users and farmers who will be the only ones able to "farm" large quantities of the token. Indeed, while the metaverse will open its doors to different blockchains and to users from different realities, the heart of the farm, the production center of the Farming Tales metaverse, will remain firmly on WAX.


---

# Agent Instructions: 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://nodo42.gitbook.io/farming-tales-the-game/tokenomic/aureus-aureus.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.