> For the complete documentation index, see [llms.txt](https://docs.ecko.finance/eckodao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecko.finance/eckodao/eckodex/eckodex-litepaper/why-eckodex/solution-slippage-control.md). # Solution: Slippage Control The gas problem affects more than just performance and economics. Miner Extracted Value, frontrunning and gas auctions all take advantage of the underlying blockchain’s inability to properly scale in order to take advantage of users and their trades. This often results in massive amounts of gas being spent to eke out every bit of profit opportunity, failing users’ transactions in their wake. Users then worry more about the cost of their transactions failing than their want to trade. Kadena, with its multi-chain architecture, offers a unique opportunity to minimize this into oblivion by being able to scale any time there is a threat of mempool queues. eckoDEX uses this to create a DEX with no transaction wait times (lightning fast), giving little opportunity for others to frontrun, increasing the success rate of trades, while giving the users industry-leading slippage control to maximize profit. --- # 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://docs.ecko.finance/eckodao/eckodex/eckodex-litepaper/why-eckodex/solution-slippage-control.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.