> For the complete documentation index, see [llms.txt](https://anthive-project.gitbook.io/anthive-project-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anthive-project.gitbook.io/anthive-project-docs/1.-introduction/quickstart.md). # 1.1 Background and Purpose ## **Project Background** In the cryptocurrency market, there have been increasing cases where meme coins like Dogecoin and Shiba Inu have surged rapidly, driven by strong community support. At the same time, Web3 fields such as DeFi, GameFi, and DAO are also expanding at a fast pace, creating a demand for new use cases. ANTH (AntHive) was born out of this trend, aiming to fuse “meme coin + real-world utility + community-driven” elements. This chapter provides an overview of the background behind the launch of the ANTH project and the objectives of this white paper. ## **Purpose of This White Paper** This white paper comprehensively outlines the technical specifications, token design, ecosystem structure, roadmap, and risks associated with ANTH. Its primary goal is to enhance transparency for investors and users, ensuring that decisions are made based on accurate information. As there may be future feature additions or updates, the latest information will be periodically announced through the community and official website. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://anthive-project.gitbook.io/anthive-project-docs/1.-introduction/quickstart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.