# Vesting Visualization

To ensure **long-term sustainability**, **investor confidence**, and **ecosystem growth**, Lucidai (LUCI) implements a carefully structured vesting and cliff plan across all allocation categories.

**Cliff & Vesting Overview**

| Allocation              | Cliff Period | Vesting Period      | Start of Vesting | Unlock Profile                                  |
| ----------------------- | ------------ | ------------------- | ---------------- | ----------------------------------------------- |
| **Ecosystem & Rewards** | None         | 48 months (dynamic) | TGE              | Continuous emission based on platform activity  |
| **Team & Advisors**     | 12 months    | 36 months           | Month 13         | Monthly linear vesting post-cliff               |
| **Private Sale**        | 3 months     | 18 months           | Month 4          | Monthly linear vesting post-cliff               |
| **Public Sale (IDO)**   | None         | 6 months (80%)      | TGE              | 20% at TGE, then linear monthly over 6 months   |
| **Strategic Partners**  | 6 months     | 24 months           | Month 7          | Monthly linear vesting post-cliff               |
| **Liquidity**           | None         | -                   | TGE              | 100% at TGE (with partial lock for LP security) |
| **Development Reserve** | 6 months     | 30 months           | Month 7          | Monthly vesting post-cliff                      |
| **Marketing & Growth**  | 1 month      | 12 months           | Month 2          | Monthly vesting post-cliff                      |
| **Treasury & Ops**      | 6 months     | Flexible (governed) | Month 7+         | Disbursed via internal policy or governance     |

#### **Unlock Milestones**

<table data-header-hidden><thead><tr><th width="164"></th><th></th></tr></thead><tbody><tr><td><strong>Month</strong></td><td><strong>Description</strong></td></tr><tr><td><strong>TGE (Month 0)</strong></td><td>- 100% of Liquidity Pool tokens unlocked<br>- 20% of Public Sale unlocked<br>- Initial emissions for Ecosystem Rewards begin<br>- Total circulating supply: ~12–15%</td></tr><tr><td><strong>Month 3</strong></td><td>- Private Sale cliff ends → linear vesting begins<br>- Reward token emissions increase based on user activity</td></tr><tr><td><strong>Month 6</strong></td><td>- Strategic Partners &#x26; Development Reserve cliff ends → monthly unlock begins<br>- Marketing &#x26; Growth tokens start vesting</td></tr><tr><td><strong>Month 12</strong></td><td>- Team &#x26; Advisors cliff ends → 36-month linear vesting starts<br>- Approx. 25–30% of total supply in circulation</td></tr><tr><td><strong>Month 24–36</strong></td><td>- Private Sale, Strategic, Marketing allocations mostly vested<br>- Ecosystem Rewards continue emission based on platform use<br>- 50–66% of Team allocation vested</td></tr><tr><td><strong>Month 48+</strong></td><td>- Final Team &#x26; Advisor tokens fully unlocked<br>- Development &#x26; Ecosystem allocations continue use<br>- Treasury remains for governance-directed initiatives</td></tr></tbody></table>

**Note:** This timeline reflects a balanced strategy between early liquidity and long-term sustainability, protecting against inflation while incentivizing long-term contribution.

**Key Principles**

* **Delayed Team Access**: 1-year cliff for Team & Advisors ensures long-term commitment.
* **Controlled Market Impact**: No major early unlocks for investors; slow release prevents supply shock.
* **Performance-Based Emission**: Ecosystem tokens only unlock with real user activity — not time alone.
* **Security of Liquidity**: A portion of LP tokens can be locked in smart contracts for LP confidence.


---

# 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://dream-lucidai.gitbook.io/dream-lucidai-docs/tokenomics/vesting-visualization.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.