> For the complete documentation index, see [llms.txt](https://mdexdoc.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mdexdoc.gitbook.io/doc/announcement/announcement-on-mdexs-deployment-on-ethereum-network.md). # Announcement on MDEX’s deployment on Ethereum Network Dear MDEXers Since the start of DAO governance, users have enthusiastically participated in community proposals. "cross-chain to Ethernet / polygon / Solana" is one of proposals that passed the referendum. MDEX teams began to implement the proposal and successfully launched the ETH network at 19:15 (UTC+8) on October 2, 2021. Only the swapping feature is laid out at this phase. More powerful features will be equipped soon to meet the demands of the majority. To celebrate the success of cross-chain to ETH, all transaction fees on ETH will be rewarded to the LP providers. Multi-chain deployment is the future of DeFi protocol for which MDEX is striving so as to create a high-performance composite DEX ecology that brings users more valuable and user-friendly products. --- # 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://mdexdoc.gitbook.io/doc/announcement/announcement-on-mdexs-deployment-on-ethereum-network.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.