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

# 📦 Supply & Allocation

### Tokenomics

The TradeWe ecosystem is powered by TRWE, a utility token designed to align platform growth, trader incentives, and long-term ecosystem development.\
The total supply is fixed at **1.2 billion TRWE**, with minting permanently disabled in the smart contract. Future governance decisions may be managed through decentralized voting mechanisms, ensuring transparency and community participation.

#### Allocation

| Category         |      Tokens | % Supply |
| ---------------- | ----------: | -------: |
| Presale          | 480,000,000 |      40% |
| Marketing        | 120,000,000 |      10% |
| Team             | 132,000,000 |      11% |
| Liquidity        | 120,000,000 |      10% |
| Partnerships     |  96,000,000 |       8% |
| Rewards          |  96,000,000 |       8% |
| Reserve          |  84,000,000 |       7% |
| Development Fund |  72,000,000 |       6% |

#### Presale — 40%

The largest allocation is dedicated to the community through a multi-stage presale.\
These tokens provide the initial foundation for ecosystem growth, platform adoption, and liquidity generation while ensuring broad token distribution among early supporters.

#### Marketing — 10%

Allocated to awareness campaigns, partnerships, content creation, influencer collaborations, and user acquisition initiatives.\
The objective is to accelerate adoption and expand the TradeWe community globally.

#### Team — 11%

Reserved for the core team responsible for building, maintaining, and expanding the ecosystem.\
Team allocations are subject to vesting mechanisms designed to align long-term incentives with platform success.

#### Liquidity — 10%

Dedicated to decentralized and centralized exchange liquidity.\
This allocation supports healthier market conditions and improved trading accessibility.

#### Partnerships — 8%

Reserved for strategic collaborations with brokers, educational platforms, technology providers, communities, and ecosystem partners.

#### Rewards — 8%

Used to incentivize ecosystem participation through staking programs, referral campaigns, trading competitions, seasonal events, and community rewards.

#### Reserve — 7%

A strategic reserve designed to support future opportunities, ecosystem initiatives, and unforeseen operational requirements.

#### Development Fund — 6%

Allocated to continuous platform development, infrastructure scaling, security improvements, AI-powered tools, mobile applications, and future ecosystem products.

***

#### Utility of TRWE

TRWE is designed to be an active ecosystem token rather than a passive asset.

Token holders may benefit from:

* Reduced challenge and subscription costs
* Premium platform features
* Staking rewards
* Referral incentives
* Access to exclusive competitions and events
* Governance participation
* Future ecosystem products and integrations

As TradeWe expands, additional utility layers will be introduced across the platform, creating increasing demand for TRWE within the ecosystem.


---

# 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://tradewe-io.gitbook.io/whitepapper/tokenomics/supply-and-allocation.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.