> 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/blink-payment-methods/on-chain/how-can-i-send-an-on-chain-transaction-with-blink.md).

# Nsobola ntya okusindika enkolagana ku lujegere ne Blink?

Okusindika enkolagana ku lujegere ne Blink, nsaba ogoberere emitendera gino:

1. Gulawo app ya Blink onyige ku peesa ely'oku `Sindika`.
2. Yingiza endagiriro y’oyo afuna Bitcoin ku lujegere oba sika koodi ye eya QR.
3. Londa oba oyagala okusaasaanya okuva ku akawunti yo eya BTC oba Stablesats (USD).
4. Yingiza ssente z’oyagala okusindika n’akawandiiko ak’okwesalirawo.
5. Koona ku `Kidako` era okebere emirundi ebiri ebikwata ku nsonga eno.
6. Tambuza akaterebusa ku ddyo okumaliriza okusindika.
7. Oluvannyuma lw'okukakasibwa enkolagana, osobola okugabana ID y'okutunda (era emanyiddwa nga `hash` oba `txid`) n'oyo afuna ng'obukakafu bw'enkolagana ewangudde.

Singa ssente z’okusima eby’obugagga eby’omu ttaka ezibaliriddwa zisukka ebitundu 10% ku ssente z’oteekateeka okuweereza Blink ejja kulaga okumanyisibwa: `Ebisale bingi! Tukuwa amagezi ku Lightning.`

Weetegereze nti okutunda ku lujegere kuyinza okutwala ekiseera okukakasa ku mutimbagano gwa Bitcoin, okusinziira ku ntambula y’omukutu eriwo kati n’ebisale by’okutunda ebirondeddwa.


---

# 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/blink-payment-methods/on-chain/how-can-i-send-an-on-chain-transaction-with-blink.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.