> For the complete documentation index, see [llms.txt](https://docs.meerkat.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meerkat.wtf/usdmerk-token/tokenomics.md). # Tokenomics Built for Growth and Sustainability The **$MERK token economy** is designed to incentivize long-term holders, reward early supporters, and ensure deep liquidity for a thriving ecosystem. ### **Initial Distribution (6B Total Supply)** 🔹 **Presale: 50% (3B tokens)**\ The majority of the supply is allocated to the presale, ensuring **fair early distribution and community-driven growth.** 🔹 **Staking Rewards – Presale: 5% (300M tokens)**\ Early buyers can stake immediately, earning high APY rewards before $MERK even launches. 🔹 **Staking Rewards – Post-Presale: 20% (1.2B tokens)**\ Long-term staking incentives to sustain engagement and reward committed holders. 🔹 **DEX Liquidity: 7.5% (450M tokens)**\ A significant allocation to **ensure deep liquidity** at launch for smooth trading. 🔹 **CEX Liquidity: 7.5% (450M tokens)**\ Strategic allocation for **future centralized exchange listings** to maximize accessibility. 🔹 **Development: 5% (300M tokens)**\ Funding for **protocol expansion, AI integrations, and long-term innovation.** 🔹 **Airdrop &** **Marketing: 5% (300M tokens)**\ Driving **brand awareness, partnerships, and ecosystem adoption** through strategic campaigns. With a **balanced allocation** focused on **community incentives, liquidity, and growth**, $MERK is built to **scale and thrive in the long run.** --- # 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.meerkat.wtf/usdmerk-token/tokenomics.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.