> For the complete documentation index, see [llms.txt](https://sportsearn.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://sportsearn.gitbook.io/whitepaper/rewards.md).

# Rewards

With our experience in producing and operating Blockchain projects, we have learnt that if a blockchain project cannot find a real stream of revenue, it will be extremely difficult to maintain the value of the token. When the amount of minted tokens exceeds the amount of burnt ones, inflation happens, leading to a great deterioration in the price of the tokens.

With that in mind, we avoid building Sportearn based on an economic model where the money of the latter pays for the former. We aim to make Sportearn sustainable by generating revenue from real-world business activities. Parts of the profits will go to the project's reward pool.

| NFT   | NFT Level |     Daily EARNING     |
| ----- | :-------: | :-------------------: |
|       |    1-10   |  5$(Sportearn Token)  |
|       |   10-20   |  7$(Sportearn Token)  |
| Basic |   20-30   |  10$(Sportearn Token) |
|       |   30-40   |  15$(Sportearn Token) |
|       |   40-50   |  20$(Sportearn Token) |
|       |           |                       |
|       |    1-10   |  30$(Sportearn Token) |
|       |   10-20   |  35$(Sportearn Token) |
| Pro   |   20-30   |  40$(Sportearn Token) |
|       |   30-40   |  45$(Sportearn Token) |
|       |   40-50   |  50$(Sportearn Token) |
|       |           |                       |
|       |    1-10   |  60$(Sportearn Token) |
|       |   10-20   |  70$(Sportearn Token) |
| Ultra |   20-30   |  80$(Sportearn Token) |
|       |   30-40   |  90$(Sportearn Token) |
|       |   40-50   | 100$(Sportearn Token) |

<figure><img src="/files/i3t9gl1eBHxDJqokvLu6" alt=""><figcaption></figcaption></figure>


---

# 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://sportsearn.gitbook.io/whitepaper/rewards.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.