> 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/blink-payment-methods/lightning/why-does-blink-use-lightning-as-default.md).

# ¿Por qué Blink utiliza Lightning como predeterminado?

Además de los beneficios inherentes de la Red Lightning, Blink eligió usar Lightning de forma predeterminada porque se alinea con nuestra visión de hacer que el bitcoin sea accesible para todos.

Al utilizar Lightning, podemos proporcionar a los usuarios transacciones más rápidas, más baratas y más eficientes, lo que facilita el uso de bitcoin para transacciones diarias.

Además, al utilizar la Red Lightning, Blink puede ayudar a reducir la carga general en la cadena de bloques de Bitcoin, contribuyendo así a la salud general y sostenibilidad de la red Bitcoin.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faq.blink.sv/espanol/blink-payment-methods/lightning/why-does-blink-use-lightning-as-default.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.