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

# Speed Bump para Órdenes Taker

Backpack aplica un speed bump de 100ms a todas las órdenes taker en mercados spot y de futuros.

Esto refuerza la liquidez en la parte superior del libro. Protege las órdenes en reposo de la selección adversa impulsada por latencia. También favorece libros más profundos y una mejor ejecución para todos los participantes.

#### Cómo funciona

* El speed bump de 100ms aplica a cualquier orden enviada sin el flag `postOnly`. Esto incluye órdenes de mercado y órdenes límite, incluyendo órdenes IOC, incluso si la orden finalmente queda en reposo en el libro.
* Las órdenes con `postOnly` habilitado no están sujetas al speed bump.
* Las cancelaciones de órdenes están exentas. Se procesan sin demora.
* El speed bump aplica de forma uniforme a todos los participantes.

Intentar eludir el speed bump viola los Términos de Servicio.


---

# 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://guide.backpack.exchange/es/trading/speed-bump-para-ordenes-taker.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.