> 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/deutsch/blink-payment-methods/lightning-address/what-is-a-lightning-address-and-what-does-it-look-like.md).

# Was ist eine Lightning Adresse, und wie sieht sie aus?

Lightning Adressen sind eine Art von Lightning Netzwerk-Zahlungsanforderung, die auf dem LNURL-Protokoll basiert und es Nutzern ermöglicht, Bitcoin-Zahlungen direkt auf ihre Lightning Wallet zu erhalten. Sie sehen genauso aus wie eine E-Mail-Adresse, aber anstelle von E-Mails können Sie damit Lightning-Zahlungen empfangen.

Lightning Adressen können je nach dem Dienst, den der Zahlungsempfänger nutzt, unterschiedlich aussehen.

Die Lightning Adresse eines Blink-Benutzers sieht zum Beispiel aus wie <username@blink.sv>, während die Lightning Adresse eines Wallet of Satoshi-Benutzers wie <username@walletofsatoshi.com>.\&#x20 aussehen könnte;

Unabhängig vom Format sind alle Lightning Adressen für den Empfänger eindeutig, so dass er Lightning Zahlungen sicher und einfach empfangen kann.


---

# 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/deutsch/blink-payment-methods/lightning-address/what-is-a-lightning-address-and-what-does-it-look-like.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.