> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/technical-docs/trading/taker-speed-bump.md).

# Taker Speed Bump

Backpack applies a 100ms speed bump to all taker orders across spot and futures markets.

This reinforces top-of-book liquidity. It protects resting orders from latency-driven adverse selection. It also supports deeper books and better execution for all participants.

### How it works

* The 100ms speed bump applies to any order submitted without the `postOnly` flag. This includes market orders and limit orders, including IOC orders, even if the order ultimately rests on the book.
* Orders with `postOnly` enabled are not subject to the speed bump.
* Order cancellations are exempt. They are processed without delay.
* The speed bump applies uniformly to all participants

Attempting to circumvent the speed bump violates the Terms of Service.


---

# 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://support.backpack.exchange/technical-docs/trading/taker-speed-bump.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.