> 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/welcome.md).

# Welcome

Welcome to Meme Kombat

## Overview

Meme Kombat is an innovative blockchain project that brings together the exciting world of memes and the competitive thrill of battle arenas. By leveraging cutting-edge technology and the decentralized power of the Ethereum network, Meme Kombat aims to create a unique and engaging gaming experience.

## Purpose of Meme Kombat Token ($MK)

The Meme Kombat Token ($MK) serves as the core currency of the Meme Kombat arena, creating an ecosystem where players, stakeholders, and enthusiasts can interact and participate. The $MK is designed to be used in various ways within the Meme Kombat ecosystem:

* Automated Battles: Characters representing various Meme Coins engage in automated battles, with outcomes determined on-chain. These battles are brought to life through advanced AI technology, providing a captivating and unpredictable gaming experience.
* Wagering: $MK holders can stake and wager their tokens on the outcomes of battles. Victorious players have the opportunity to win valuable prizes, including additional $MK tokens.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://memekombattoken.gitbook.io/meme-kombat-whitepaper/welcome.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 `build a script that syncs our docs to a CMS` 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.