# Token Distribution and Allocation Strategies

Balanced distribution strategies align incentives, foster trust, and ensure ecosystem stability. Key considerations include:

* Transparent communication of token allocation to stakeholders.
* Fairness across allocations to founders, investors, advisors, community, and operational reserves.
* Alignment of allocations with long-term goals, avoiding excessive short-term incentives.

### Clear Allocation Guidelines:

* Team Allocation: Should be between 10% and 15%; do not exceed 15%. Lower allocations enhance community and investor trust, reducing insider influence risks.
* Liquidity Allocation: Always allocate at least 5% to liquidity—this is the absolute minimum. Ideally, allocate 10% (good) to 15% (great). If liquidity is initially low, establish a rewards program specifically incentivizing liquidity providers or yield farmers.
* Investor Allocations (Pre-TGE): Do not allocate more than 30% of the total token supply to pre-TGE investors to preserve community confidence. Preferably, allocations between 10-20% leave room for more strategic allocations and community-focused incentives.
* Treasury Allocation: Allocate at least 10% to treasury funds, ensuring project sustainability. Avoid allocating more than 20%, as excessive treasury allocations can negatively impact community perception.
* Rewards Program: Having a robust rewards program is highly beneficial for ecosystem engagement and token sustainability. Further guidelines on structuring effective rewards programs will be provided in future sections.


---

# 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://playbook.tokenise.tech/module-2-tokenomics-mechanics/token-distribution-and-allocation-strategies.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.