> For the complete documentation index, see [llms.txt](https://whitepaper.gravityhub.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gravityhub.xyz/ecosystem-features/revenue-redistribution.md).

# Revenue Redistribution

A share of Gravity's game sales revenue is redistributed to players and developers who bring new users to the platform. Benefits for Players Players who invite their friends to the platform will receive GVT Tokens every time their referrals purchase content. Benefits for Developers Game developers are incentivized to direct their marketing efforts towards Gravity to earn an additional revenue stream from their users' purchases — even purchases of content from other developers.

<figure><img src="/files/G7d6KxhtAN2M0SRVdvmB" alt="" width="375"><figcaption></figcaption></figure>

* Any Gravity player or developer can invite new users to the platform
* Referrers can accumulate an unlimited number of referees
* 2.5% of all a referee's game purchases are shared with their referrer
* Referees can, in their turn, also invite new users - earning them a 1.25% ongoing commission.


---

# 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://whitepaper.gravityhub.xyz/ecosystem-features/revenue-redistribution.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.