> For the complete documentation index, see [llms.txt](https://chainontop.gitbook.io/chainontop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chainontop.gitbook.io/chainontop/overview.md). # Overview Quick Guide **Chain On Top** is the first **chain-abstracted social game of world domination** — an explicit battlefield where **tokens become troops**, liquidity is represented as **Hubs on a world map**, and teams rally together to **conquer the world and be the Chain on Top**. *** ### ✨ Why It Matters * **Make your tokens fight for you** — don’t just hold, deploy them as troops to capture rival liquidity. * **Speculation meets strategy** — wins and losses move real liquidity. * **Community over charts** — coordinate with your chain’s degens and flex your victories. * **Liquidity isn’t given. It’s captured.** *** ### 🧭 What You’ll Find Here * **Basic Terms:** tokens, hubs, deployments, battles * **Gameplay Mechanics:** power formulas, time multipliers, resolution logic. * **Liquidity & Consequences:** what moves after battles and why it matters. * **Social Strategy Layer:** the levers (targets, timing, allocation, alliances). *** ### 🔗 Stay Updated Follow us for constant updates: [x.com/ChainOn\_Top](https://x.com/ChainOn_Top) {% hint style="info" %} Note: Chain on Top is going live during Socket Surge, which means this is the first app battle testing the Socket Chain Abstraction Protocol. The game mechanics are inherently risky as well; while you could 100x your buy in, it's likelier that it will go to zero. So only play with $ that you're willing to lose. NFA. DYOR. LFG. {% endhint %} --- # 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://chainontop.gitbook.io/chainontop/overview.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 `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.