Overview
A Lightning Address is a human-readable identifier in the format [email protected] that allows anyone to receive Lightning Network payments as easily as receiving an email. Built on top of the LNURL-pay protocol, it transforms the complex process of generating and sharing Lightning invoices into something as simple as sharing a static, memorable string. When someone sends a payment to a Lightning Address, their wallet automatically resolves the address, fetches a fresh invoice, and completes the payment behind the scenes.
Before Lightning Addresses, receiving a Lightning payment required generating a single-use invoice (a long encoded string or QR code) and sharing it with the sender before it expired. This flow was functional but awkward: it required both parties to be coordinating in real time and made it impossible to, say, put a payment address on a business card or website in a way that would work for future visitors. Lightning Addresses solve this by providing a stable, reusable identifier that works indefinitely.
How It Works
The Lightning Address protocol leverages the well-known LNURL-pay flow combined with a simple HTTP resolution step. When a wallet encounters an address like [email protected], it performs the following:
1. Wallet receives: [email protected]
2. Wallet constructs URL:
https://example.com/.well-known/lnurlp/alice
3. Wallet fetches that URL and receives:
{
"callback": "https://example.com/pay/alice",
"minSendable": 1000, // 1 sat (millisats)
"maxSendable": 100000000, // 100k sats
"metadata": "Pay alice",
"tag": "payRequest"
}
4. Wallet sends amount to callback URL:
GET https://example.com/pay/alice?amount=50000
5. Server responds with a fresh BOLT11 invoice:
{
"pr": "lnbc500n1p...", // Lightning invoice
"routes": []
}
6. Wallet pays the invoice automatically.
The entire process is invisible to the user. From their perspective, they type or paste a Lightning Address, enter an amount, and confirm the payment.
Setting Up a Lightning Address
There are several ways to obtain a Lightning Address:
Wallet providers: Many Lightning wallets (such as Wallet of Satoshi, Blink, or Alby) provide Lightning Addresses to their users automatically, typically in the format [email protected].
Self-hosted: Users running their own Lightning node can set up a Lightning Address by running a small web server that responds to LNURL-pay requests at the .well-known/lnurlp/ path.
Domain-based: Organizations can offer Lightning Addresses to employees or members on their own domain, enhancing brand identity while enabling instant payments.
Lightning Address vs. Other Payment Methods
Method Reusable Memorable Server needed Privacy
─────────────────────────────────────────────────────────────────
BOLT11 Invoice No No No Moderate
LNURL-pay QR Yes No Yes Low
Lightning Address Yes Yes Yes Low
BOLT12 Offer Yes No No High
On-chain Address Yes* No No Moderate
* On-chain address reuse is possible but discouraged for privacy
Privacy Considerations
Lightning Addresses have meaningful privacy trade-offs that users should understand. The domain operator can log every payment request, seeing when payments are requested and for what amounts. The sender's wallet connects to the recipient's HTTP server, potentially revealing the sender's IP address. Additionally, the domain in the address reveals where the recipient's Lightning infrastructure is hosted.
For users who prioritize privacy, BOLT12 offers an alternative that operates entirely within the Lightning protocol layer without HTTP dependencies, providing stronger privacy through blinded paths. However, Lightning Addresses remain the most user-friendly option for everyday use and are widely supported across the wallet ecosystem.
Adoption
Lightning Addresses have seen rapid adoption since the protocol's introduction. They are supported by most major Lightning wallets, integrated into social media platforms, and used by businesses accepting Lightning payments. The familiar email-like format removes a significant barrier to Lightning adoption by giving users something they immediately understand how to share and use.
Related Concepts
- LNURL — the underlying protocol suite that Lightning Addresses are built on
- Lightning Invoice — the payment request format fetched behind the scenes when paying a Lightning Address
- BOLT12 — an alternative approach to reusable payment identifiers with stronger privacy
- Lightning Network — the payment network that Lightning Addresses provide a user-friendly interface for