> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/espanol/transaction-fees/what-are-mining-fees.md).

# ¿Qué son las tarifas de minería?

Las tarifas de minería son pequeñas cantidades de Bitcoin que pagas para que tus transacciones sean confirmadas por la red. Las tarifas se pagan a los mineros, que son computadoras especiales que aseguran la red y confirman las transacciones. Estas tarifas garantizan que tus transacciones se procesen de manera rápida y segura. Blink no retiene ninguna de las tarifas de transacción, estas van directamente a los mineros.

La cantidad de tarifas de minería que debes adjuntar a tu transacción depende de varios factores, incluido el nivel de congestión de la red, el tamaño de tu transacción en bytes y la demanda actual de espacio en bloque. Durante períodos de alto tráfico en la red, las tarifas tienden a aumentar, y durante períodos de bajo tráfico, las tarifas tienden a disminuir.

Si las tarifas de minería calculadas son más del 10% del monto que estás preparando para enviar, Blink mostrará una notificación: `¡Tarifa alta! Recomendamos Lightning.`


---

# 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://faq.blink.sv/espanol/transaction-fees/what-are-mining-fees.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.