> 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/evm/trading/selling/sending-a-sell-transaction.md).

# Sending a Sell Transaction

Interactive tutorial

{% embed url="<https://app.guideflow.com/player/8konqn9i5p>" %}

### Additional information

<details>

<summary>Slippage</summary>

Slippage is calculated after taxes. For example, if you plan to sell a token for 1 ETH, and there's a 50% tax on the token, your initial 1 ETH will be reduced to 0.5 ETH due to the tax. Then, the slippage is applied. Consequently, the actual minimum amount you'll end up selling may be much less than 0.5 ETH.&#x20;

**For tax protection you can select the maximum buy and sell taxes in the settings. Slippage is calculated not on token price fluctuation, but on the amount you are trying to sell. For example: You are trying to sell 1 Eth worth of Pepe and you have slippage set at 50%. This means that right after selling you are accepting that your tokens will be worth anywhere from 0.5 Eth to 1 Eth (if taxes are at 0%)**&#x20;

**Keep in mind, there is no anti-mev on Binance Smart Chain, so please use Slippage!**

</details>

<details>

<summary>Gas</summary>

Select the amount of Gas you would like to use for your transactions by pressing the ⛽️GWEI button. The more Gas you use, the better position in the block you will get, but the transaction will cost you more.

</details>

{% content-ref url="/pages/QscbXaOQNdpphuat0FZn" %}
[Sell Orders](/setup-trading-and-management/evm/trading/limit-orders/sell-orders.md)
{% endcontent-ref %}


---

# 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/evm/trading/selling/sending-a-sell-transaction.md?ask=<question>&goal=<user_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.
