> For the complete documentation index, see [llms.txt](https://docs.basedbot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basedbot.app/quick-setup-guide/based-bot-set-up/transaction-speed.md).

# Transaction Speed

If you want faster transactions or feel like you're getting outbid by other users, here's what matters:

## Pro Mode

Pro Mode skips the price impact check before sending your transaction, which can slightly speed up buys on EVM chains. It does not change slippage, gas or routing. Enable it from the monitor screen (session-only) or set a default in /settings.

Pro Mode is the first thing to try if you feel like other users are landing before you in the same block.

## Gas Fees on L2 Chains (Base, Arbitrum, etc.)

On Base and most L2 chains, transaction ordering is **first-come-first-served** (FCFS), not gas-price based like Ethereum mainnet. This means:

* Paying 10 GWEI instead of 0.1 GWEI on Base gives you **zero advantage** — you're just burning ETH for nothing.
* Other users who land before you in the block simply had their transaction reach the sequencer faster, not because they paid more gas.
* Setting a high custom gas on L2s is a waste. Use the default gas settings or remove your custom gas override in /settings.

Gas bidding only matters on Ethereum mainnet where miners/validators order transactions by gas price.

## Turbo Mode (Sniping only)

Available on sniper targets only. Turbo skips all safety checks (slippage protection, price impact, gas estimation, transaction simulation, token checks) for maximum speed. Use with caution — this removes all safety nets.

## MEV Protection

MEV protection helps protect your transactions from being front-run by bots. Only available on ETH, BASE, and BSC chains. Toggle it from /settings.


---

# 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.basedbot.app/quick-setup-guide/based-bot-set-up/transaction-speed.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.