> For the complete documentation index, see [llms.txt](https://sweetdao.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sweetdao.gitbook.io/whitepaper/white-paper/token-allocation.md).

# Token Allocation

SweetDAO wants to ensure there is an equal opportunity for all those that want to be involved with the SweetDAO community. The token supply allocation will be made as follows:

* 50% will be available to the community through the liquidity mining programs.
* 25% will be made available to the development team. This will vest over a 3 year period. 
* 25% will be given to the Sweet Protocol instantly. Since liquidity service charge fees are based on how many tokens a user owns, by allocating 25% of the SWEET tokens to the Sweet Protocol it means the Sweet Protocol will collect liquidity service fees for itself. These collected fees will go directly into the Sweet Protocols treasury, ultimately as [Protocol Owned Liquidity](/whitepaper/white-paper/protocol-owned-liquidity-pol.md). Doing this ensures the long term viability of the project and will increase SweetDAO’s ability to be a self sustaining independent long term business.

\
We would like to ensure that the token distribution is as fair as possible, for this reason we won't be holding an ICO or IDO.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://sweetdao.gitbook.io/whitepaper/white-paper/token-allocation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.