> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/strategies/sequential-arbitrage.md). # Sequential arbitrage Capture a price gap with one strategy wallet. Sequential arbitrage uses one strategy wallet. It buys a token on the cheaper DEX, waits for the fill, then sells the received tokens on the more expensive DEX. ### Before you start Fund **Wallet A** with ADA. Keep the Surge tab open. The wallet needs your maximum trade size, reserve floor, order deposits, and fees. Sequential execution needs no token inventory. It is slower than parallel arbitrage because the sell begins only after the buy fills. ### Configure the strategy Choose the token and at least two DEX's to monitor. Set your minimum and maximum trade sizes, minimum net profit, daily loss limit, and reserve floor. Choose **Wallet A** as the strategy wallet. Surge compares eligible pools at every price update. It includes pool fees, price impact, batcher fees, network fees, Surge fees, and a 15% safety buffer. It trades only when the expected result meets your minimum net profit. ### How execution works 1. Surge submits the buy leg on the cheaper DEX. 2. After it fills, Surge sizes the sell using the exact tokens received. 3. Surge submits the sell on the DEX offering the best return. If the sell cannot fill, Surge re-offers it using its concession process. After unsuccessful attempts, the opportunity becomes **Partial**. You can then close the remaining position manually. ### Risks Prices can move between the buy and sell. A filled buy does not guarantee a profitable sell. Set a daily loss limit and monitor partial opportunities. See [Signing and approvals](/core-concepts/signing-and-approvals.md) for how strategy trades are signed. --- # 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.surgecardano.com/strategies/sequential-arbitrage.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.