> 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/stablesats/what-makes-stablesats-stand-out-from-stablecoins-like-tether-and-usdc.md).

# What makes Stablesats stand out from stablecoins like Tether and USDC?

While stablecoins like Tether and USDC have become increasingly popular, they can be limited by the blockchain they are built on, and users may have to worry about which stablecoin or blockchain their counterparty uses.

Stablesats offers a unique solution to this problem, as it is fully interoperable with anyone using Bitcoin and Lightning. This means that users can hold and transact dollars without worrying about the specific blockchain or stablecoin being used by their counterparties.

Additionally, because Stablesats uses derivatives products, it can offer a more flexible and scalable solution compared to traditional stablecoins. Overall, Stablesats provides an exciting new way to hold and transact dollars within the Bitcoin and Lightning ecosystem, offering greater flexibility and interoperability than other stablecoin options.


---

# 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/stablesats/what-makes-stablesats-stand-out-from-stablecoins-like-tether-and-usdc.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.