> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/solana/bot-features/settings/fees-tips-and-slippage.md).

# Fees, Tips and Slippage

{% hint style="info" %}
Sets the priority fee, tip, Auto Tip, slippage and MEV protection used by your token panel trades.
{% endhint %}

## Fee

Tap <kbd>⛽ Fee</kbd> in Settings. The priority fee is extra SOL you pay on a transaction so the network processes it sooner.

A tip is an extra payment, in SOL, that gets your trade into a block. The priority fee and the tip are paid in SOL, on top of Bloom's trading fee.

<div align="left"><figure><img src="https://4108356913-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLeahxvohQr3fYBgeulA%2Fuploads%2FPq71sIDxcFyOxHN5Pix8%2Ffees-tips-and-slippage-fee.png?alt=media&amp;token=b024465e-a9f1-45ac-b523-ccc2545a8991" alt="The Fee screen with its five buttons."><figcaption></figcaption></figure></div>

| Button                            | Action                                                                                                                         |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **💰 Buy Fee**                    | Priority fee for your buys. A new account starts at 0.001 SOL.                                                                 |
| **💰 Sell Fee**                   | Priority fee for your sells. A new account starts at 0.001 SOL.                                                                |
| **💰 Buy Tip**                    | Tip for your buys. A new account starts at 0.001 SOL.                                                                          |
| **💰 Sell Tip**                   | Tip for your sells. A new account starts at 0.001 SOL.                                                                         |
| **🔴 Auto Tip** / **🟢 Auto Tip** | Lets Bloom set the fee and tip for token panel trades and Degen Mode buys, from here or the token panel's **Auto Tip** button. |

## Slippage

Tap <kbd>🛍️ Slippage</kbd> in Settings. Slippage is the most the price may move against you before your trade fills, in percent. A higher slippage gets a trade through faster, but makes it more likely to be sandwiched.

| Button                 | Action                   |
| ---------------------- | ------------------------ |
| **🛍️ Buy Slip: 10%**  | Slippage for your buys.  |
| **🛍️ Sell Slip: 10%** | Slippage for your sells. |

## MEV Protection

MEV bots watch pending trades and trade around yours to profit from it, which is called a sandwich. MEV protection protects your trade from sandwich bots.

| Button              | Action                                                                                         |
| ------------------- | ---------------------------------------------------------------------------------------------- |
| **Buy Protection**  | Switches MEV protection for your buys, from the Settings screen or the token panel's buy side. |
| **Sell Protection** | Switches MEV protection for your sells, from the token panel's sell side only.                 |


---

# 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.bloombot.app/solana/bot-features/settings/fees-tips-and-slippage.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.
