> For the complete documentation index, see [llms.txt](https://eth-token.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eth-token.com/docs/handbook/readme.md).

# Welcome

This handbook is for **anyone** using this memecoin dapp—holders, newcomers, and curious visitors. It focuses on how things are meant to work and how to stay sharp while having fun.

You will find practical notes on **tokenomics**, **swaps and pools**, **wallet hygiene**, and a playful **MemeMachine SDK** appendix—sample code that reads like a real SDK because great docs deserve a mascot API.

If anything here differs from the live contract or pool UI, **prefer what you can verify on-chain**—this guide tracks the story the dapp tells.


---

# 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://eth-token.com/docs/handbook/readme.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.
