# Tokenomics

Upon the Livetree infrastructure deployment, the total supply of Seed NFT Collective (SEDC) tokens was one billion. A (12%) portion of the platform tokens (Treasury Governance Reserve) was reserved to ensure the network could in future apply for a parachain slot on the Polkadot network. Significant portions of the network were also reserved for the Community Incentive (35%), Ecosystem development (10%), and liquidity (9%) .

<figure><img src="https://2817609908-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjWyDAqZecsuDeCNg51f%2Fuploads%2F8Pzf198Nss7cZK9FdqFA%2Ftable.png?alt=media&#x26;token=7ff86e0b-7964-4e62-b63b-13b7c8cedd9b" alt=""><figcaption></figcaption></figure>

**Presented below is an aggregated chart displaying the distribution of tokens across SEDC Allocation categories.**

### SEDC Token Allocation

<figure><img src="https://2817609908-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjWyDAqZecsuDeCNg51f%2Fuploads%2FWsfMTZMnYtp4iOZN56D4%2Fchart-diagramm.png?alt=media&#x26;token=39bff91a-8aa8-4076-9c5b-b266ae94ad09" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="156"></th><th width="135"></th><th width="69"></th><th></th></tr></thead><tbody><tr><td><strong>SEDC Allocation</strong></td><td><strong>Quantity</strong></td><td><strong>%</strong></td><td><strong>Description</strong></td></tr><tr><td>Seed round</td><td>90,000,000</td><td>9</td><td>Seed funding started Q3 2023. Subject to a 10 month vesting schedule from network launch with a 8 month lock and equal vesting in months 9–18.</td></tr><tr><td>Strategic round</td><td>60,000,000</td><td>6</td><td>Strategic funding has not started. Subject to a 8 month vesting schedule from network launch with a 6 month lock and equal vesting in months 7–14.</td></tr><tr><td>Public</td><td>30,000,000</td><td>3</td><td><p>Public round. </p><p>Subject to equal vesting in months 1–6.</p></td></tr><tr><td>Founding team</td><td>130,000,000</td><td>13</td><td>Founding team: Subject to a 36 month vesting schedule from network launch with a 12 month lock and equal vesting in months 13-48</td></tr><tr><td>Advisors</td><td>30,000,000</td><td>3</td><td>Advisors: Subject to a 24 month vesting schedule from network launch with a 10 month lock and equal vesting in months 11-34</td></tr><tr><td>Community Incentives</td><td>350,000,000</td><td>35</td><td><p>Distributed amongst Creators | Ambassadors | Mini-app Devs | SED Upgrade</p><p>Subject to equal vesting in months 1–48.</p></td></tr><tr><td>Liquidity</td><td>90,000,000</td><td>9</td><td><p>Liquidity used for token marketing. </p><p>Subject to equal vesting in months 1–12.  </p></td></tr><tr><td>AI Infrastructure</td><td>100,000,000</td><td>10</td><td>As we continue to grow and enhance our AI infrastructure, we are dedicated to promoting decentralization in our AI model development. To achieve this goal, we have reserved resources for participating in a polkadot parachain slot auction application. This allocation is subject to a 44-month vesting schedule, beginning from the network launch, with a 4-month lock-in period. The vesting will be distributed equally over the months 5 to 44, ensuring a gradual and steady release of resources to support the decentralization process.</td></tr><tr><td>Treasury Governance</td><td>120,000,000</td><td>12</td><td>Strategic governance over platform issues and emergency technical issues are subject to a 36-month vesting schedule from network launch, with a 12-month lock-in period, followed by equal vesting in months 13–48.</td></tr></tbody></table>


---

# 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://livetree.gitbook.io/livetree-whitepaper/business-model/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.