> For the complete documentation index, see [llms.txt](https://whitepaper.wicrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.wicrypt.com/4.-tokenomics/4.1-wicrypt-network-token-usdwnt.md).

# 4.1 Wicrypt Network Token ($WNT)

$WNT token is an underlying foundation of Wicrypt ecosystem. $WNT is an EVM-compatible token launched on Polygon. Most of the interactions occurring within Wicrypt platform are tied directly or indirectly to $WNT, making it a means of utility and governance.

The maximum supply of $WNT is set as 200,000,000, meaning that unless future DAO decides otherwise, there can never be more tokens in circulation. Wicrypt token is already listed and publicly tradable on Quickswap and MEXC.

More details related to the economy of $WNT and its allocation and release details were included in the next chapter (‘Wicrypt token economy’), while an in-depth overview of detailed token utilities is included in section 5  (‘Overview of other token-based utilities’).


---

# 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://whitepaper.wicrypt.com/4.-tokenomics/4.1-wicrypt-network-token-usdwnt.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.