# Token Distribution

While the VCloud ecosystem is fully functional and the tokens have immediate utility, all tokens distributed during this period will be concretely distributed at the moment of token generation, ensuring pre-launch backers, team members, and the early community members are on equal footing.

The largest recipients of token distribution will be the public presale and liquidity pool. Necessitating a majority of the token flow, the presale, and liquidity are necessary to facilitate platform growth. Just 12% of VCloud tokens will be set aside for the project team to help bootstrap the VCloud Social and ensure a diverse and accessible community over the coming years. The remaining number will be allocated to other areas of infrastructure and VCloud schemes to keep the ecosystem projects afloat.

![](/files/sXjY6qIfEzS74GeS9RHt)

**Total Supply: 100，000，000 VCloud**

**Initial Token Distribution:**

* Public Presale:45%
* Liquidity**:**20.655%(Locked on Pinksale Platform)
* Team Vesting:12%(Locked and vested on Pinksale Platform)
* Partners and Advisors:12.345%
* Marketing and Exchange Listing:10% (Locked and vested on Pinksale Platform)

{% hint style="info" %}

#### How Token Vesting Can Help Your Project

A clear token vesting schedule with Proof-Of-Lock (how the tokens are managed and unlocked), may help gain the trust of the supportive communities, facilitating sustainable growth of the project through a commitment to the community.
{% endhint %}


---

# 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://vcloud-social.gitbook.io/vcloud-social-whitepaper/token-distribution.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.