> For the complete documentation index, see [llms.txt](https://docs.defi.app/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defi.app/knowledge-base/reference/solana-transaction-tx-modes.md).

# Solana Transaction (TX) Modes

On Solana, selecting between **Auto**, **Jito**, and **Classic** transaction (TX) modes determines how your transactions are processed, particularly concerning speed, reliability, and protection against [MEV ](#user-content-fn-1)[^1]strategies.

***

## What is Jito?

**Jito** is an advanced Solana validator client developed by [Jito Labs](https://www.jito.wtf/), designed to optimize MEV handling.

Using Jito, users can submit bundles of transactions that are executed atomically, in order. This means all transactions in a bundle either succeed together or fail together, ensuring consistency and predictability for complex operations.

To incentivize validators, users attach a **tip** (an additional fee) to their bundles, which are then prioritized based on these tips.

This TX mode is useful for precise transaction ordering and execution.

***

## Transaction Modes

* **Auto**: This mode automatically selects the optimal transaction path based on current network conditions. It may choose between Jito or Classic modes to balance speed, cost, and reliability.
* **Jito**: This mode routes your transactions through Jito-enabled validators, leveraging the bundling and tipping system. It's useful for scenarios where atomic execution and transaction sequence are important.
* **Classic**: This traditional mode sends transactions through the standard Solana network, without the enhancements provided by Jito. It's suitable for straightforward transactions where advanced MEV protection and bundling are unnecessary.

Configure your transaction strategy on Solana based on your use case, optimizing for speed, reliability, and protection against MEV-related issues. If you aren't sure which mode to use, select **Auto**.

[^1]: Maximum Extractable Value


---

# 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.defi.app/knowledge-base/reference/solana-transaction-tx-modes.md?ask=<question>&goal=<endgoal>
```

`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.