> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/cn/jiao-yi/jiao-yi-ji-chu/turbo-mo-shi-solana.md).

# Turbo 模式（Solana）

Solana 上最快的交易执行路径，无需支付额外费用。

TURBO 帮助受支持的 Solana 交易更快成交，不收取额外交易手续费。它会自动运行，无需为每个钱包单独开启。

### **ON / OFF 代表什么？**

交易面板中的 TURBO 状态取决于你设置的小费（Tip）：

* **ON：** 小费达到 **0.0001 SOL 或以上**，可使用更快的发送方式。
* **OFF：** 小费低于 **0.0001 SOL**，仍可正常交易。

开启自动费用（Auto Fee）后，状态会随小费变化自动更新。

### **如何开始使用？**

对于尚未完成设置的钱包，当余额高于 **0.1 SOL** 时，Frontrun 会自动完成设置。设置时会预留少量 SOL，这部分金额与交易手续费分开。

### **每笔交易都会使用 TURBO 吗？**

即使显示 ON，部分交易仍会使用常规方式处理。ON 仅表示小费达到使用门槛，并不代表该笔交易实际使用了 TURBO。Frontrun 会自动处理，无需额外操作。


---

# 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.frontrun.pro/cn/jiao-yi/jiao-yi-ji-chu/turbo-mo-shi-solana.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.