> For the complete documentation index, see [llms.txt](https://docs.memecore.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.memecore.com/memecore/token/token-allocation.md). # Token Allocation
CategoriesRatioPurpose
Community 58%The purpose of community allocations in tokenomics is to activate the ecosystem and incentivize participation.
(e.g. maximizing network effects, Encouraging governance participation, building long-term loyalty)
Foundation15%Supports long-term project development, ecosystem growth, and community.
Core Contributor13%Rewards key team members and early contributors for ongoing contributions and innovation.
Investor12%Provides funding for investors and strategic partners.
Meme Treasury2%The Meme Treasury funds community incentives, supports creators, ensures ecosystem stability, and engages in fun activities
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.memecore.com/memecore/token/token-allocation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.