> For the complete documentation index, see [llms.txt](https://docs.glue.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glue.net/white-papers/white-paper-governance/foundation-allocation.md).

# Foundation Allocation

In the genesis block, 10% of the total token supply will be allocated to the Glue foundation. The foundation is tasked with executing the main sale as well as the token generating event. While the specific details are still to be finalised, it is anticipated that up to 5% of the total token supply may be sold in the next sale. However, this percentage is subject to change based on market dynamics and the strategic needs of the Glue Network.

### Utilisation of Foundation Tokens

The remaining tokens allocated to the foundation will be used for several key purposes:

1. **Market Maker Incentives:** To ensure liquidity and stability in the market, the foundation will allocate a portion of its tokens to incentivize market makers. This will help maintain a healthy trading environment, reduce volatility, and ensure that users can buy and sell tokens with minimal slippage.
2. **Operational Funding:** The foundation will use its token allocation to fund its operations, including ongoing development, marketing, community engagement, and other essential activities. This funding is crucial to support the continuous growth and evolution of the Glue ecosystem.

By strategically allocating tokens to the foundation, Glue ensures that it has the necessary resources to execute its vision and maintain a robust and dynamic ecosystem. The foundation's role in managing token sales and funding operations is vital to the long-term success and sustainability of the network. This structured approach to token allocation reflects our commitment to transparency, efficiency, and strategic growth.


---

# 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://docs.glue.net/white-papers/white-paper-governance/foundation-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.