> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop/growth-tooling.md).

# Growth Tooling

Our growth strategy also includes robust creator and referral programs designed to align incentives closely with ecosystem health:

* Referral Links: Players earn rewards for referring new active participants. Rewards trigger only if the referred cohort maintains a positive RORS.
* Share-to-Earn Snapshots: Players receive rewards for generating and sharing in-game content, fostering organic user-generated marketing.
* Social Monitoring Tool: An advanced platform that tracks and rewards social engagement around ecosystem games, utilizing sophisticated detection methods to prevent manipulation and ensure genuine community growth.

All rewards within these programs are structured to prioritize ecosystem sustainability, reinforcing positive player behaviors and ensuring long-term value creation.

<br>


---

# 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://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop/growth-tooling.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.