> For the complete documentation index, see [llms.txt](https://dogex-3.gitbook.io/dogex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dogex-3.gitbook.io/dogex-docs/introduction.md). # Introduction ## Dogex Protocol - Much Leverage, Very Trading Welcome to Dogex, where your DOGE dreams either go to the moon 🚀 or crash harder than a Windows 98 computer! Our protocol lets you trade DOGE with leverage that would make even Elon Musk nervous. We're talking 10x to 200x leverage because apparently, regular trading is for people who enjoy sleeping at night. ### What Makes Us Special? * **Insane Leverage**: Up to 200x because YOLO, right? * **USDC Collateral**: We accept the "boring" stablecoin as collateral * **Auto-Liquidation**: Our robots are very efficient at taking your money * **One Position Rule**: Because multitasking is overrated * **Oracle Magic**: Real-time DOGE prices usually accurate and we're getting them from a few reliable sources such us Binance ### Fair Warning **Contract Stats:** * Network: Hyperion * Contract Address: 0xa1c6144c2aFa413329A82A942237Af2ED8452a03 * Collateral: USDC * Underlying: DOGE * Leverage: 10x-200x * Liquidation: 90% loss threshold --- # 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://dogex-3.gitbook.io/dogex-docs/introduction.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.