> 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/luganda/stablesats/how-does-stablesats-work.md).

# Stablesats zikola zitya?

**Stablesats** ekola nga ekozesa obutale bw'ebivaamu ebya Bitcoin okukola ddoola ya Amerika ey’obutonde. Kino kikolebwa nga tuyita mu kukozesa ekintu eky’ebyensimbi ekiyitibwa perpetual inverse swap, nga mu bukulu ye ndagaano wakati w’enjuyi bbiri okuwanyisiganya enjawulo mu muwendo gw’eby’obugagga (mu mbeera eno, Bitcoin) wakati w’ensonga bbiri mu kiseera.

Stablesats zitondebwa mu kusinga Bitcoin ne zigikozesa okuggulawo ekifo eky'okubeerera ekikyuusakyusa. Okuwaanyisa eky'okubeerera ekikyuusakyusa kikoleddwa okukuuma omuwendo gwa doola ya Amerika 1, awatali kulowooza ku nkyukakyuka mu bbeeyi ya Bitcoin. Kino kisobozesa abakozesa okukwata, okusindika, n’okufuna ddoola mu waleti zaabwe eza Lightning nga tekyetaagisa stablecoins oba okugatta awamu fiat.

Mu bukulu, Stablesats ziwa engeri abakozesa Lightning gye bayinza okwekuuma okuva ku nkyukakyuka mu muwendo gw’ensimbi za Bitcoin n’okukakasa nti basobola okutuukiriza obuvunaanyizibwa bwabwe obw’ebyensimbi nga tebalina kukyusa buli kiseera wakati wa ssente za Bitcoin ne fiat.

[akatambi](https://www.youtube.com/watch?v=FGO4dbwMYwg) kiraga engeri enkola eno gy'ekolamu.


---

# 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/luganda/stablesats/how-does-stablesats-work.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.