# Lightning Address

There are essentially two types of Lightning Addresses that appear similar but function very differently behind the scenes. Each has its own pros and cons and is obtained through different methods.

## Lightning Addresses based on the LNURL protocol

This is the original method, which relies on a web server to handle the payment process. Essentially, you authorize the server to create invoices on your behalf. When someone attempts to pay your Lightning Address, their wallet contacts the server, which in turn connects to your node or wallet to generate an invoice. That invoice is then sent back to the sender. The major drawback here is that the server sees all the payment details—resulting in poor privacy.

### **How to get one**

You have to use a web service that supports this type of Lightning Addresses, such as [lnaddress.me](https://lnaddress.me/) or [getalby.com](https://getalby.com/). Alternatively, you can run your own service, using your own domain and avoiding any third-party privacy concerns. This can be done with LNbits’ lnaddress extension or by self-hosting [satdress](https://github.com/nbd-wtf/satdress).\
A lot of wallets offer built-in solutions with their own servers, so users get a Lightning Address without much effort. BitBanana, though, puts privacy first—and that means not running a server that could see your payment activity.

### Pros & Cons

<mark style="color:green;">✔</mark> **Widely Supported:** Almost all major wallets and services support it\ <mark style="color:red;">**✕**</mark> **Poor privacy:** The web server can see your payment activity and payment details, like amount, comments, etc. (Unless you decide to self-host, which gets more complicated.)

## Lightning Addresses based on DNS Records (Bip353)

This is the newer, privacy-focused way of handling Lightning Addresses, as defined in BIP353. It still uses the familiar email-style format (like `name@domain.com`), but skips the web server entirely. Instead, the sender’s wallet looks up your payment info using DNS, which is then used to initiate an end-to-end encrypted Lightning transaction directly with your node or wallet.

### **How to get one**

Setting up a BIP353-compatible Lightning Address requires publishing a DNS record that others can query. This record contains a static payment code (BOLT12 offer), which you can host via a third-party service like [twelve.cash](https://twelve.cash)—or self-host it running [twelvecash](https://github.com/ATLBitLab/twelvecash) on your own domain.

### Pros & Cons

<mark style="color:green;">✔</mark> **Good privacy**\ <mark style="color:red;">**✕**</mark> **Limited Support (for now):** Only a few wallets (like Zeus or Phoenix) support sending to such an address.\ <mark style="color:red;">**✕**</mark> **Limited Availability (for now):** Setting one up requires BOLT12 support, which currently only works with Core Lightning when using BitBanana.


---

# Agent Instructions: 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:

```
GET https://docs.bitbanana.app/using-bitbanana/lightning-address.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.