> 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/stablesats/how-does-stablesats-compare-to-stablecoins-and-fiat-banking-integration.md).

# ¿Cómo se compara Stablesats con las stablecoins?

El Dollar Balance Custodial (impulsado por Stablesats) se diferencia de las stablecoins tradicionales de varias maneras:

* **Interoperabilidad:** Opera sobre Bitcoin y Lightning, por lo que los usuarios pueden realizar transacciones con cualquier persona en esas redes sin preocuparse por qué blockchain o token usa su contraparte.
* **Sin activos de reserva:** A diferencia de las stablecoins respaldadas por reservas fiduciarias, Stablesats utiliza posiciones de derivados — no hay reservas subyacentes en dólares ni requisitos de colateral en el sentido tradicional.
* **Riesgo de contraparte:** Stablesats depende de los exchanges donde se deposita el colateral para los contratos de swap inverso perpetuo. Esto introduce riesgo de contraparte del exchange, que puede mitigarse diversificando entre múltiples exchanges.

Para riesgos y limitaciones, consulta [¿Cuáles son los riesgos asociados con el Dollar Balance?](/espanol/stablesats/what-are-the-risks-associated-with-stablesats.md) y los Términos y Condiciones.


---

# 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/stablesats/how-does-stablesats-compare-to-stablecoins-and-fiat-banking-integration.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.