> For the complete documentation index, see [llms.txt](https://memekombattoken.gitbook.io/meme-kombat-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://memekombattoken.gitbook.io/meme-kombat-whitepaper/presale-sold-out.md).

# Presale (SOLD OUT)

The presale is sold out. If you purchased tokens during the presale you can claim them directly from our website.

## <mark style="color:orange;">Disclaimers</mark>

#### <mark style="color:blue;">The more you know</mark>

**General Disclaimer** - Digital assets, including cryptocurrencies and tokens, may lack regulatory oversight in certain jurisdictions. The market value of these assets can experience significant volatility, rising or falling without warning. Gains realized may be subject to tax liabilities as stipulated by the laws of your governing jurisdiction.

**No Refund Disclaimer** - All contributions to this presale are final and non-refundable. Due to the decentralized nature of blockchain and smart contracts, we are unable to reverse transactions once they have been confirmed.


---

# 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://memekombattoken.gitbook.io/meme-kombat-whitepaper/presale-sold-out.md?ask=<question>&goal=<user_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.