Lightning Payments Explained: BOLT11, BOLT12 Offers, and LNURL
A guide to how Bitcoin's payment layer handles invoices, static payment codes, privacy-preserving blinded paths, and asynchronous settlement.
Key points
- BOLT11 invoices are single-use and reveal the recipient node's public key, requiring real-time node generation for each payment.
- LNURL and Lightning Addresses use standard web servers and HTTPS to deliver reusable static payment identifiers, adding Web2 dependencies.
- BOLT12 Offers bring native static identifiers to Lightning, enabling reusable codes and recurring billing without intermediate web servers.
- Blinded paths in BOLT12 obscure recipient node identities and channel topologies using end-to-end onion encryption across intermediate hops.
The Lightning Network executes fast, low-cost Bitcoin settlements by routing payments through a peer-to-peer web of off-chain channels. To execute a transfer, the paying node requires routing directions and cryptographic instructions from the recipient. The protocols that format and communicate these instructions have evolved from rigid, single-use payment receipts into reusable, privacy-centric standards.
Understanding how value moves across this layer requires dissecting the standards that coordinate transactions: traditional BOLT11 payment requests, the HTTP-based LNURL protocol, and native BOLT12 Offers. Each standard addresses a specific trade-off between user friction, node infrastructure, and recipient privacy.
The mechanics of Lightning payment requests
A traditional layer-one Bitcoin transfer requires only a public key hash or script address. The sender broadcasts a transaction to the network, and miners confirm it into a block without coordinating directly with the recipient. The recipient does not need to be online at the moment of broadcast.
The Lightning Network operates differently. Because payments settle over off-chain channels, transactions rely on Hash Time-Locked Contracts (HTLCs). An HTLC routes funds across intermediate nodes using a cryptographic secret called a preimage. The recipient generates this secret, hashes it, and shares the resulting payment hash with the payer. When the payer routes funds toward that hash, each intermediate node forwards the balance, unlocking funds only when the recipient discloses the original preimage to pull the payment.
This structure requires an exchange of data before a payment can begin. The recipient's node must generate a cryptographic invoice containing the payment hash, expiry timestamp, destination node identifier, and fallback instructions. For background on channel architecture and HTLCs, see The Lightning Network, Explained: How Bitcoin Scales for Payments.
BOLT11: single-use, interactive invoices
The original standard for Lightning payments is defined in the Basics of Lightning Technology repository as BOLT11. A BOLT11 invoice is an encoded alphanumeric string, typically displayed as a QR code, that packages all metadata needed to route a specific transfer.
BOLT11 invoices carry three structural properties: they are single-use, ephemeral, and sender-revealing.
Every BOLT11 invoice binds directly to a single cryptographic preimage. If a node attempts to settle two separate payments against the same preimage, intermediate routing nodes can retain the second payment without forwarding it, causing the sender to lose funds. Consequently, a BOLT11 invoice cannot safely be paid twice.
BOLT11 invoices also include an explicit expiration time. Because channel capacities and routing paths fluctuate across the network, invoices expire to prevent senders from attempting obsolete routes with stale fee calculations. If an invoice expires before broadcast, the payer must contact the recipient to generate a fresh invoice.
Finally, BOLT11 invoices publish the recipient node's public key in plain text. Any party that scans a standard BOLT11 invoice can identify the recipient's node on the public Lightning gossip graph, inspect its public channel capacities, and infer its geographic or network presence. This static linkage creates significant metadata exposure for merchants and continuous payees.
LNURL and Lightning Addresses: web servers as bridges
To overcome the static-address limitation of BOLT11, developers created LNURL, an application-layer suite of protocols that coordinates Lightning nodes via traditional web servers using HTTP endpoints.
Instead of parsing a BOLT11 string directly, an LNURL-compatible wallet queries an HTTPS endpoint hosted on a web domain. In the LNURL-Pay workflow, the sender scans an HTTP link. The sender's wallet executes a GET request against that URL, receiving parameters such as minimum and maximum receivable amounts and metadata descriptions. The wallet then submits a second GET request containing the specific amount the user wishes to transfer. The remote web server coordinates with an underlying Lightning node, generates a single-use BOLT11 invoice on the fly, and returns it to the sender's wallet for immediate settlement.
This architecture enabled the creation of the Lightning Address standard. Structured identically to an internet email address (user@domain.com), a Lightning Address resolves to an LNURL-Pay endpoint through standard internet domain records. This mechanism allows non-technical users to share a readable, static identifier for donations, tipping, or ongoing settlements.
LNURL introduces fundamental trade-offs. It relies on standard Web2 infrastructure: the Domain Name System (DNS), Certificate Authorities, and HTTP application servers. If the host domain expires, faces DNS manipulation, or experiences server downtime, the recipient cannot issue BOLT11 invoices. Furthermore, the web server operator can log the IP addresses of payers, creating a centralized privacy vulnerability external to the Lightning protocol itself.
BOLT12: native offers and blinded paths
To achieve static, reusable payment endpoints natively inside the Lightning protocol without relying on HTTP servers, the Lightning development community introduced BOLT12, commonly known as Offers.
Unlike a BOLT11 invoice, a BOLT12 Offer is not an invoice itself. It is a compact, reusable request for an invoice that travels entirely over the native Lightning peer-to-peer network using custom messaging protocols. An Offer can be printed on physical merchandise, displayed statically on a merchant checkout page, or saved indefinitely in a mobile wallet.
When a payer scans a BOLT12 Offer, the payer's node uses Lightning Network onion-routed messages to send an invoice request directly to the issuer. The recipient node creates a unique, single-use BOLT12 invoice and sends it back to the payer over the network. The payer then settles that invoice through the standard channel routing mechanism.
BOLT12 provides two core technical advances: native subscriptions and blinded paths.
A blinded path is a routing technique that hides the recipient's public key and channel topology. Instead of publishing its real node identifier, the recipient constructs an onion-encrypted route covering the final hops of the payment path. The recipient encrypts the identity of each node along this tail end. The payer can route a payment through the public network to the entry point of the blinded path, but cannot determine which node constitutes the actual final destination. This architecture preserves recipient privacy without external web proxies.
BOLT12 also natively handles recurring billing and payer-initiated refunds. Because the protocol enables bidirectional communication over Lightning transport keys, a merchant node can issue an invoice that permits authorized, programmatic pull requests at recurring intervals, eliminating the need for custodial payment processors.
Receiving without continuous connectivity
A primary architectural hurdle of the Lightning Network is that receiving funds traditionally requires the recipient node to remain online, operational, and connected to peers to execute the cryptographic signature exchange required for HTLC resolution.
Several mechanisms resolve this constraint across the BOLT11, LNURL, and BOLT12 frameworks.
In custodial implementations, a third-party service provider runs an always-on Lightning node on behalf of the user. Invoices generated through the provider's LNURL or BOLT11 systems terminate at the custodian's node, which credits the user's internal database balance. This design removes uptime requirements for the end user but reintroduces counterparty credit and regulatory risks.
Non-custodial mobile wallets handle offline receipt through specialized Lightning Service Providers (LSPs). When an external sender attempts to pay an invoice belonging to an offline mobile node, the LSP intercepts the incoming routing packet. The LSP dispatches an operating system push notification to wake the recipient's mobile application in the background. Once the app launches and restores its encrypted transport connection with the LSP, the node signs the requisite HTLC state update and claims the payment.
Under BOLT12, asynchronous payments are standardized through relay nodes. A recipient can designate an always-online peer to act as an asynchronous storage mailbox. When a payer requests an invoice or transmits an HTLC, the relay holds the encrypted payload until the recipient node establishes a secure connection, retrieves the data, and completes the cryptographic settlement.
Worked example: routing costs and invoice generation
Consider an automated retail merchant that configures a static payment point for a purchase priced at 100,000 satoshis (0.00100000 $BTC). The transaction pathway differs fundamentally across protocol designs.
Under a BOLT11 implementation, the merchant terminal must connect via API to an active node, compute the hash of a fresh preimage, and render an invoice with an expiration window of 900 seconds. If a customer scans the invoice at 901 seconds, the terminal rejects the payment, requiring a regeneration cycle that burdens the server database.
Under a BOLT12 implementation, the merchant prints a single, static Offer QR code on the register. The customer scans the static code. The customer's wallet identifies the blinded path specified by the merchant, consisting of an intermediate gateway node and the merchant's destination node.
Assume the network routing fees to reach the gateway node require a base fee of 1 satoshi plus a proportional fee rate of 100 parts per million (ppm), which equals 0.01 percent.
$$\text{Proportional Fee} = 100{,}000 \times 0.0001 = 10 \text{ satoshis}$$ $$\text{Hop Fee to Gateway} = 1 + 10 = 11 \text{ satoshis}$$
Inside the blinded path, the merchant establishes an additional fixed hop fee of 5 satoshis to cover the private route to the destination node. The customer's wallet computes the total routing outlay:
$$\text{Total Settled Amount} = 100{,}000 + 11 + 5 = 100{,}016 \text{ satoshis}$$
The customer's node issues an invoice request through the Lightning messaging layer, receives the single-use invoice encrypted across the blinded path, and forwards 100,016 satoshis. The gateway node keeps 11 satoshis, forwards the balance across the blinded segment, and the merchant claims 100,000 satoshis while disclosing neither its public key nor its channel balances.
Common misconceptions
Misconception: A Lightning Address is an on-chain Bitcoin address.
A Lightning Address uses an email-style string (such as user@domain.com) to query an internet web server over HTTPS via the LNURL protocol. It is not an on-chain address, it cannot receive base-layer Bitcoin transactions directly, and it depends on traditional web architecture to return dynamic Lightning invoices.
Misconception: Reusing a BOLT11 invoice is a safe way to receive multiple payments.
BOLT11 invoices should never be paid more than once. Paying an identical BOLT11 invoice a second time reuses the original cryptographic preimage. Once that preimage is revealed publicly on the network to settle the first transaction, intermediary nodes can extract it and claim subsequent payments without forwarding funds to the intended recipient.
Misconception: Blinded paths in BOLT12 completely eliminate network routing fees.
Blinded paths protect network identity, not routing costs. Senders still pay the standard base and proportional routing fees levied by each routing node along the path. The recipient incorporates the fees for the blinded segment directly into the encrypted path data provided to the sender.
How invoice standards shape market adoption
The transition between payment protocols reflects Bitcoin's broader infrastructure maturation. BOLT11 established proof of concept for off-chain channel routing, but its rigid single-use constraints created substantial engineering friction for point-of-sale systems, e-commerce checkouts, and peer-to-peer applications.
LNURL demonstrated the market demand for static identifiers and human-readable addresses, yet its dependence on external web domains introduced trust assumptions incompatible with sovereign node operations. BOLT12 internalizes these user experience improvements directly into the Lightning peer-to-peer layer, combining the static utility of web identifiers with cryptographic routing privacy.
For enterprise infrastructure operators and self-custody wallet developers, the widespread implementation of native asynchronous payments and blinded paths reduces reliance on centralized server relays. As node implementations standardize BOLT12 support, off-chain Bitcoin settlements move closer to mirroring the seamless abstraction of conventional payment networks while preserving decentralized execution.
Questions this story raises
- Why can a BOLT11 invoice only be used once?
- A BOLT11 invoice is tied to a unique cryptographic preimage. Once that preimage is revealed to settle the initial payment, any intermediate routing node on the network can use the disclosed preimage to capture subsequent payments without routing them to the destination.
- What is the primary difference between LNURL and BOLT12?
- LNURL uses external web servers and HTTPS calls to fetch fresh single-use invoices, relying on standard domain infrastructure. BOLT12 Offers use the native Lightning peer-to-peer network to request and receive invoices directly between nodes.
- Can a Lightning node receive payments while offline?
- In standard setups, the receiving node must be online to complete the cryptographic signature exchange. Non-custodial mobile applications solve this via background push notifications from Lightning Service Providers, while BOLT12 supports native asynchronous mailbox relays.
- Does a Lightning Address work on the Bitcoin base chain?
- No. A Lightning Address is an application-level identifier designed solely for Lightning transactions. It cannot parse or settle transactions broadcast directly to the Bitcoin base blockchain.
References
- [1] Bitcoin Developer Documentation: Lightning Network — Bitcoin Developer Documentation
- [2] BOLT #11: Invoice Protocol for Lightning Payments — Lightning Network Specifications (BOLTs)
- [3] LUD-01: LNURL Core Specifications — LNURL Community Specifications
- [4] BOLT #12: Offer Protocols for Lightning Payments — Lightning Network Specifications (BOLTs)
Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.