> For the complete documentation index, see [llms.txt](https://projectpolyverse.gitbook.io/polyverse-token-economy-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://projectpolyverse.gitbook.io/polyverse-token-economy-whitepaper/user-flow/token-flow.md).
# Token Flow
**Game / NFTs:**
1. User purchases one of the rare NFT Collections - Capital goes into the company treasury.
2. User Mints their Character NFT - Locked $PATIC sent to Treasury.
3. User Turns batches and items into NFT’s using $PATIC - $PATIC sent to the Treasury.
4. User Sells NFT in Marketplace - 20% Fee (10% Into Treasury + 10% into Ecosystem Pool).
5. User participates in the paid tournament - 20% Fee sent to the Treasury.
**Staking:**
1. Staked tokens flow into a staking Pool.
2. Staked tokens + rewards come out of the ecosystem pool.
**Governance:**
1. Converted $PATIC into $GCV will take a 10% cut that is sent to the treasury
2. 90% of $PATIC is kept in the swap.
3. When $GCV is converted all the $PATIC is sent to the user and $GCV stays in the pool.
---
# 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://projectpolyverse.gitbook.io/polyverse-token-economy-whitepaper/user-flow/token-flow.md?ask=&goal=
```
`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.