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

# Economy

The sale of energies in the Aicrowd game is split into two equal parts: half is burned and the other half is converted into USDT. The part that is burned is taken out of circulation, which reduces the supply of Aicrowd coins in the market and, in theory, increases their value. The other half is added to the reward payout pool to remunerate players according to their performance in the game.

To feed a liquidity pool for in-game player rewards payments, all transactions on the platform are taxed at 5%. Player rewards are paid daily from the liquidity pool fed by transaction fees, with a minimum value of 10 USDT or similar currency.

The liquidity pool accumulates the amounts and distributes them daily to the players who have won the game according to the established rules. Each 30-day cycle, the accumulated value in the liquidity pool is divided into 30 equal parts for daily distribution. This process is repeated continuously, so that the liquidity pool is always being fed by the sales of energy and items and the 50% of the fees from the sales of NFTs, ensuring the long term sustainability of the game.


---

# 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://aicrowd.gitbook.io/whitepaper-eng/ecosystem/economy.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.