> For the complete documentation index, see [llms.txt](https://appwhitepaper.gitbook.io/striker-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appwhitepaper.gitbook.io/striker-whitepaper/ecosystem-economics.md).

# Ecosystem Economics

The project team has included transaction fee that allows transaction fees during transfer of token from user to user and trade. This is to enable the project to run seamlessly without external funding required after the TGE and subsequent listings.

During tournaments, players will be required to pay some amount of SUFU native tokens to have access to the tournament and benefit from the prize pool if they win. These SUFU tokens paid into the project tournament wallet will be locked up and later added to the ecosystem reward wallet which will be used as rewards to keep promotional and marketing activities in the community at peak.


---

# 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://appwhitepaper.gitbook.io/striker-whitepaper/ecosystem-economics.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.
