# Token Distribution Model

Distribution prioritizes user rewards and sustainable development over speculative trading.

**Token Allocation:**

| Category              | Percentage | Purpose                            |
| --------------------- | ---------- | ---------------------------------- |
| **User Rewards**      | **50%**    | Transaction rewards over 5 years   |
| Ecosystem Development | 20%        | Partnerships, growth, integrations |
| Team & Advisors       | 15%        | Incentives with 4-year vesting     |
| Platform Development  | 14%        | Technical enhancement, operations  |
| Public Sale           | 1%         | Community access, liquidity        |

<figure><img src="/files/c2hU2oeFMLKg2FWVZurG" alt=""><figcaption></figcaption></figure>

**User rewards** represent the largest allocation with 50% of total supply dedicated to transaction-based distribution. This substantial commitment demonstrates platform focus on user value creation rather than team enrichment.

**Distribution timeline** provides sustainable reward availability: Year 1 releases 40% of rewards pool for user acquisition, Years 2-3 release 30% for sustained engagement, and Years 4-5 release final 30% creating natural scarcity as individual token value increases.

Vesting schedules prevent market manipulation while ensuring stakeholder alignment. Team allocation includes four-year vesting with one-year cliff, while performance milestones tie releases to platform achievements. Transparent schedules provide community visibility into token release timing.


---

# 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://skxs-organization.gitbook.io/skx_v1.4/skx-tokenomics-and-reward-structure/token-distribution-model.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.