> 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/parallel-arbitrage.md). # Parallel arbitrage Capture a price gap with two strategy wallets. [8. Arbitrage strategies](/tutorials/8.-arbitrage-strategies.md) for dual-wallet setup and execution risks. Parallel arbitrage uses two strategy wallets to submit both trade legs at the same time. It reduces execution delay but needs token inventory. ### Before you start Fund **Wallet A** with ADA. Fund **Wallet B** with enough of the token for the largest sell. Keep the Surge tab open while the strategy runs. Wallet A buys on the cheaper DEX. Wallet B sells its token inventory on the more expensive DEX. The bought tokens go to Wallet B, and the ADA proceeds go to Wallet A. ### 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. Select separate wallets for Wallet A and Wallet B. Surge evaluates the full round trip on every price update. It subtracts 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 builds the buy and sell legs when it detects an opportunity. 2. Both transactions are signed and submitted together. 3. Surge records profit after both legs fill. If only one leg fills or submits, the opportunity becomes **Partial**. Use **Force close** to exit the resulting one-sided position after cancelling any parked order. ### Risks Parallel execution reduces timing risk. It does not remove fill risk. One leg can fill while the other fails. Maintain Wallet B's token inventory and set a daily loss limit. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.surgecardano.com/strategies/parallel-arbitrage.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 `automate deployments from our CI pipeline` 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.