# Tokenomics

**Name:** QLix

**Symbol:** QLIX

**Contract address:** 0x0a907B0bBFF60702b29a36b19718D99253cFBD9F

**Network:** Ethereum (ERC-20)

**Total supply:** 1,000,000 QLIX

**Max supply:** 1,000,000 QLIX

**Circulating supply:** 1,000,000 QLIX

**Decimals:** 18

**Tax:** 5% buy, 4% sell (no transfer tax). 

Collected taxes are used to:

* Fund ongoing development by supporting the work of our developers and technical teams.
* Finance marketing campaigns and community-building initiatives.
* Support ambassador programs and onboarding of ecosystem partners.
* Cover other growth-related operational expenses that strengthen the QLix ecosystem.

> This tax structure ensures that every transaction contributes directly to the long-term success and expansion of the platform.

Contract ownership is renounced. There are no whitelisted or blacklisted wallets.

#### Supply Distribution

Liquidity Pool: 85%

Marketing: 9%

Team: 6%

85% of QLIX supply is paired with $5,000 worth of WETH and launched via Uniswap V2.

### Deflationary Token

By integrating buybacks and burns into platform activity, QLix aligns platform growth directly with token holder value.

This mechanism makes QLIX a **deflationary asset** over time, reducing the total supply and aiming to increase the value of the remaining tokens, benefiting long-term holders.


---

# Agent Instructions: 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:

```
GET https://qlixbot.gitbook.io/docs/qlix-token/tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.