> For the complete documentation index, see [llms.txt](https://docs.sigma.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigma.win/setup-trading-and-management/sol/trading/limit-orders/sell-orders.md). # Sell Orders ## Interactive Guide {% embed url="" %}
Multiple orders You can set as many simultaneous orders as you like in the bot, just keep entering your desired settings and creating orders! ![](https://3662047399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCpxhAXHLRUbZGnCXYQne%2Fuploads%2FjayHJ34HAA5GLBGQYtE4%2FCleanShot%202025-09-23%20at%2012.16.06%402x.png?alt=media\&token=c49897ac-a06a-46d9-ac1a-5c4a6e915f11)
Slippage Slippage is the difference between the price you anticipate for a trade and the actual price at which it executes, often influenced by market volatility or low liquidity. A higher slippage setting can speed up trade execution but increases the risk of being sandwiched (leading to unfavorable prices and reduced returns). A lower slippage setting reduces these risks but may prevent the tx from executing.
Gas Gas is the fee for processing Solana transactions. The more gas you use, the faster your tx will be processed.
MEV Protection and Anti-MEV Tips When you use high slippage, your tx becomes susceptible to sandwich attacks. A sandwich attack is when MEV bots see your tx, buy ahead of you, raise the price, then sell after, making you pay a higher price and lowering your returns. MEV protection on Sigma shields you from this by routing your txs through private relays, but may make your tx slower. Adding an anti-MEV tip prioritizes tx being processed when MEV protection is on.
--- # 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.sigma.win/setup-trading-and-management/sol/trading/limit-orders/sell-orders.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.