> For the complete documentation index, see [llms.txt](https://whitepaper.cubebase.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cubebase.foundation/contents/token-distribution.md).

# Token Distribution

CubeBase does not have a mint function, ensuring that the total supply will never be more than one billion tokens. The token distribution for CubeBase has been carefully planned to ensure fair distribution and liquidity for investors. 50% of the total supply was sold during the fair launch, providing all investors with the opportunity to purchase tokens. 30% of the total supply was sent to the liquidity pool on PancakeSwap, to ensure liquidity and trading activity on the platform. Nearly 20% of the total token supply has already been burned. With the automatic burn function in the contract, the #CubeB token will be forever deflationary.

{% @mermaid/diagram content="   pie showData
title Token Distribution (millions of tokens)
"Burnt" : 192.8
"Presale" : 500
"Liquidity" : 300
"Locked " : 50
" %}


---

# 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://whitepaper.cubebase.foundation/contents/token-distribution.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.