> For the complete documentation index, see [llms.txt](https://armzlegends.gitbook.io/a/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://armzlegends.gitbook.io/a/prot/innovative-tokenomics.md).

# Innovative Tokenomics

It was essential for us to create a Tokenomics that was different from other games.

**The main point was that the Team does not hold any tokens at any time.**

In our opinion, this is a very big flaw in the usual Tokenomics, because it means that the Teams have to sell their own tokens to get paid, and thus withdraw the liquidity that was brought by the players.\
No way.

It's a bit like Apple having to sell its own shares to pay its expenses. It doesn't make sense..

In ArmzLegends, there is therefore no allocation to the Team, nor is there a fee in PROT (our token) that goes to the Team.

Of course, it's only natural that we should make money from our work, so we've devised a system of fees in BNB.

For each mint, listing on the marketplace, boost win rate and improve rarity, we take 0.05BNB.\
**And 50% of the boost win rate and improve rarity fees will be used to buyback PROT and fulfill the contract that handles fights rewards.**

This way, we sell BNB to pay ourselves, not PROT.\
**We will have absolutely no negative presence on the chart.**


---

# 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://armzlegends.gitbook.io/a/prot/innovative-tokenomics.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.