Tools/Explorers

BOLT12 vs BOLT11 vs LNURL: Lightning Invoice Format Comparison

Compare Lightning payment request formats by privacy, reusability, offline receiving, wallet support, and QR code size. BOLT11, BOLT12 offers, and LNURL side by side.

Spark Team

Lightning Payment Request Formats Compared

Lightning payments rely on payment request formats to coordinate transfers between sender and receiver. Three standards dominate the ecosystem: BOLT11 invoices, the original format shipped with the Lightning Network in 2017; BOLT12 offers, a reusable replacement merged into the BOLT specification in September 2024; and LNURL, a family of HTTP-based protocols that added features like static payment links and authentication on top of BOLT11.

Each format makes different tradeoffs across privacy, reusability, infrastructure requirements, and wallet compatibility. The following table summarizes the key differences.

FeatureBOLT11BOLT12 OffersLNURL
ReusabilitySingle-use (expires, typically within 1 hour)Reusable until revokedReusable (server generates fresh BOLT11 per request)
Receiver privacyNode ID exposed in invoiceHidden via blinded pathsIP/domain exposed (HTTPS endpoint)
Sender privacySender node visible to receiverEphemeral payer key per paymentSender IP may leak to LNURL server
TransportOut-of-band (QR, URL, copy-paste)Onion messages (native Lightning)HTTPS (requires web server)
InfrastructureLightning node onlyLightning node onlyLightning node + web server + TLS certificate
Recurring paymentsNoneNative recurrence fieldsPossible via LNURL-pay with comments
Refund supportNoneBuilt-in via invoice requestsNone (manual coordination)
Fiat-denominated amountsBitcoin onlyISO 4217 currency codes (USD, EUR, etc.)Possible (server-side conversion)
Offline receivingNoProposed via static invoices (bolts PR #1149)No (server must be online)
SpecificationBOLT #11 (2017)BOLT #12 (merged September 2024)LUD specs (community-driven, no formal BOLT)
Encoding prefixlnbc / lntblno (offer), lnr (request), lni (invoice)lnurl (bech32-encoded URL)

How Each Format Works

BOLT11: The Original Invoice

A BOLT11 invoice is a one-time payment request. The receiver generates a random 32-byte preimage, computes its SHA-256 hash (the payment hash), and encodes the hash along with an amount, expiry, and optional route hints into a bech32 string prefixed with lnbc. The sender pays by constructing an HTLC route locked to the payment hash. When the payment reaches the receiver, the receiver reveals the preimage to claim the funds, and the preimage propagates back to the sender as proof of payment.

BOLT11 invoices are single-use by design: once the preimage is revealed, every forwarding node on the route has seen it. Paying the same invoice twice would let any of those nodes intercept the second payment. Invoices also expose the receiver's node public key directly, and route hints can reveal channel partners, reducing privacy.

BOLT12: Reusable Offers via Onion Messages

BOLT12 offers separate the static "pay me" identifier from the per-payment invoice. The receiver publishes an offer (prefixed lno) that contains a description, optional amount or currency, and blinded paths. When a sender wants to pay, their wallet sends an invoice request to the receiver over onion messages (routed through the Lightning Network itself, not over HTTP). The receiver responds with a fresh, single-use invoice containing a unique payment hash.

This design delivers several advantages. The offer string never expires and can be shared publicly without risk of replay. Blinded paths hide the receiver's node ID and channel topology from the sender: the sender sees only an introduction node, not the final destination. The sender uses an ephemeral payer key for each payment, preventing the receiver from correlating multiple payments to the same wallet. BOLT12 also adds native support for recurring payments, fiat-denominated amounts via ISO 4217 currency codes, and a built-in refund flow where the payer sends an invoice request back to the original payee.

LNURL: HTTP-Based Payment Coordination

LNURL is a family of protocols (defined by LUD specifications) that use standard HTTPS to coordinate Lightning payments. The most widely used variants are LNURL-pay (LUD-06), LNURL-withdraw (LUD-03), and LNURL-auth (LUD-04). A bech32-encoded URL (prefixed lnurl) points the wallet to a server that handles the interaction.

LNURL-pay makes static payment links possible: the server generates a fresh BOLT11 invoice on each request, so the same QR code or link can be paid repeatedly. Lightning Addresses (user@domain format, defined in LUD-16) are built on top of LNURL-pay. LNURL-withdraw lets a service push funds to a user's wallet, and LNURL-auth provides passwordless login by signing a challenge with the wallet's key.

The tradeoff is infrastructure: LNURL requires a web server with a domain name, TLS certificate, and ongoing uptime. The server also sees the payer's IP address and request metadata, which is a privacy cost that the on-network transport of BOLT12 avoids entirely.

Privacy Comparison

Privacy is one of the sharpest differentiators between the three formats. The table below breaks down what metadata each party can observe.

MetadataBOLT11BOLT12LNURL
Receiver node IDVisible in invoiceHidden (blinded path)Visible in generated BOLT11
Receiver channel partnersLeaked via route hintsHidden (blinded path)Leaked via route hints in BOLT11
Sender node IDVisible to receiverEphemeral key (unlinkable)Visible to receiver
Sender IP addressNot leaked to receiverNot leaked to receiverLeaked to LNURL server
Payment correlationEach invoice is unique (low risk)Ephemeral keys prevent linkingServer sees all requests
Invoice delivery metadataOut-of-band (depends on medium)Onion-encrypted (no metadata leak)HTTPS (server logs, TLS metadata)

BOLT12's use of blinded paths and onion messages represents a significant privacy improvement. The receiver constructs a blinded route where only the introduction node is known to the sender: the rest of the path is encrypted. The sender attaches a blinded reply path so the receiver cannot learn the sender's node key either. For a deeper look at how this works, see our research on blinded paths in Lightning.

QR Code Size and Encoding

BOLT11 invoices are encoded in bech32 and can grow large when route hints are included. Each route hint adds roughly 51 bytes per hop (encoding a channel ID, node public key, fee parameters, and CLTV delta). Invoices with multiple hints can exceed several hundred characters, producing dense QR codes that some mobile cameras struggle to scan reliably. The BOLT11 spec recommends uppercase encoding for QR codes, which enables QR alphanumeric mode and reduces pixel density by roughly 45% compared to binary mode.

BOLT12 offers are typically shorter than BOLT11 invoices because they omit per-payment details like payment hashes and expiry timestamps. A basic offer might be under 200 characters, producing a compact QR code. The actual invoice is negotiated over onion messages after scanning, so the QR code only needs to carry the static offer data.

LNURL encodes a URL in bech32, which is usually shorter than a BOLT11 invoice but requires the payer's device to make an HTTP request. Lightning Addresses (user@domain) are even shorter but need a DNS lookup and HTTPS call under the hood.

Node Implementation Support

BOLT12 adoption depends on which Lightning implementations support it. The gap between implementations is the main barrier to universal BOLT12 usage.

ImplementationBOLT11BOLT12LNURL
Core Lightning (CLN)FullFull (default since v24.11)Via plugins
EclairFullFull (official since v0.11.0)Via plugins
LDKFullFull (stable since v0.1, January 2025)Via application layer
LNDFullNo native support; LNDK provides interim BOLT12 via LDKVia LNbits / application layer

LND remains the most widely deployed Lightning implementation, and its lack of native BOLT12 support is the single largest blocker to ecosystem-wide adoption. Users running LND can use LNDK, a companion daemon that bridges LDK's BOLT12 support into LND nodes. Initial BOLT12 offer and invoice codecs are under development in LND's codebase. For a full implementation breakdown, see our Lightning implementation comparison.

Wallet Compatibility Matrix

End-user wallet support determines what formats people can actually use. BOLT11 is universally supported. BOLT12 and LNURL support varies.

WalletBOLT11BOLT12 SendBOLT12 ReceiveLNURL-payLightning Address
PhoenixYesYesYesYesYes
ZeusYesYesYesYesYes
StrikeYesYesYesYesYes
CoinOSYesYesYesYesYes
Alby HubYesYesYesYesYes
Wallet of SatoshiYesNoNoYesYes
BlueWalletYesNoNoYesNo
MuunYesNoNoNoNo

LNURL-pay and Lightning Addresses have broader wallet support today because they build on top of BOLT11, which every wallet already handles. BOLT12 requires implementation-level changes, so adoption trails behind. For a broader wallet breakdown, see our Lightning wallet comparison.

Migration Path: BOLT11 to BOLT12

BOLT12 does not replace BOLT11 overnight. The two formats will coexist for years, and wallets already handle both by detecting the prefix (lnbc for BOLT11, lno for BOLT12 offers). The practical migration path looks like this:

  1. Node implementations add BOLT12 support (CLN, Eclair, and LDK have done this; LND is in progress)
  2. Wallets add offer creation and payment (Phoenix, Zeus, Strike, and CoinOS ship this today)
  3. Services adopt offers for static payment codes, replacing LNURL-pay endpoints where the HTTP infrastructure is unnecessary
  4. Lightning Addresses evolve to resolve to BOLT12 offers instead of LNURL-pay callbacks, preserving the user@domain UX while gaining BOLT12 privacy
  5. BOLT11 remains as a fallback for one-off invoices and interoperability with older wallets

The key insight is that BOLT12 and LNURL solve overlapping problems (reusability, static payment codes) but through fundamentally different architectures. BOLT12 moves coordination onto the Lightning Network itself, eliminating the web server dependency. LNURL will likely persist wherever HTTP infrastructure is already in place or where features like LNURL-auth (passwordless login) have no BOLT12 equivalent.

Offline Receiving and Async Payments

Standard Lightning requires both sender and receiver to be online simultaneously. This is a significant limitation for mobile wallets, which are frequently offline. BOLT12 opens a path to solving this through async payments.

The proposed mechanism uses BOLT12 static invoices: the receiver pre-generates an invoice and gives it to their LSP, which stores it and returns it to senders on demand. The LSP holds the HTLC until the receiver comes back online and reveals the preimage. This work is tracked in bolts PR #1149.

Neither BOLT11 nor LNURL can support offline receiving natively: BOLT11 invoices expire and cannot be pre-distributed safely (preimage reuse risk), and LNURL requires the server to be online to generate invoices. Protocols like Spark take a different approach to this problem entirely: by using a VTXO-based architecture rather than payment channels, Spark users can receive payments without being online, sidestepping the limitation at the protocol level.

How Spark Handles Payment Requests

Spark is a Bitcoin Layer 2 that supports Lightning payments without requiring users to manage channels directly. When a Spark wallet receives a payment via Lightning, the protocol handles channel management, liquidity, and routing transparently. Spark wallets can generate and pay both BOLT11 invoices and BOLT12 offers, providing full compatibility with the broader Lightning ecosystem while offering a simplified UX.

For users who want reusable payment codes without managing infrastructure, Spark's approach removes the need to choose between running an LNURL server or waiting for BOLT12 wallet support. The wallet abstracts the underlying format, and recipients can share a static identifier regardless of which invoice format the sender's wallet supports.

Frequently Asked Questions

Is BOLT12 ready for production use?

BOLT12 was formally merged into the Lightning specification in September 2024, and three of four major implementations support it: Core Lightning (enabled by default since v24.11), Eclair (official since v0.11.0), and LDK (stable since v0.1). LND does not yet have native support, though LNDK provides an interim bridge. Wallets like Phoenix, Zeus, Strike, and CoinOS support BOLT12 in production. The format is production-ready for use cases where both sender and receiver wallets support it, but BOLT11 remains the universal fallback.

Can BOLT12 replace all LNURL use cases?

BOLT12 covers LNURL-pay's core use case (reusable payment requests) with better privacy and no server requirement. However, LNURL-auth (passwordless login) and LNURL-withdraw (service-initiated payouts) have no direct BOLT12 equivalent. LNURL will likely persist for authentication workflows and for services that already operate HTTP infrastructure. Over time, Lightning Addresses may transition from resolving to LNURL-pay callbacks to returning BOLT12 offers, bridging both worlds.

Why does LND not support BOLT12 yet?

LND's development team at Lightning Labs has historically prioritized other features, including Taproot Assets for token issuance on Lightning. BOLT12 requires onion message relay, which LND did not implement natively. The community-built LNDK daemon fills this gap by running LDK alongside LND to handle BOLT12 onion messages and offer payments. Initial BOLT12 codec support has appeared in LND's development branch.

Do I need to run a web server for BOLT12 offers?

No. BOLT12 offers are exchanged entirely over the Lightning Network using onion messages. This is one of the primary advantages over LNURL, which requires a web server with a domain, TLS certificate, and ongoing maintenance. With BOLT12, a Lightning node is the only infrastructure required.

What happens if I pay a BOLT11 invoice twice?

Paying the same BOLT11 invoice twice is dangerous. After the first payment settles, the preimage is known to the receiver and every forwarding node on the route. A second payment using the same payment hash could be intercepted by any of those nodes. This is why BOLT11 invoices are strictly single-use. BOLT12 solves this by generating a fresh invoice (with a new payment hash) for every payment to the same offer.

How do Lightning Addresses relate to LNURL and BOLT12?

Lightning Addresses (user@domain format) are defined by LUD-16 and built on top of LNURL-pay. When a wallet encounters a Lightning Address, it performs an HTTPS request to the domain to retrieve payment parameters and generate a BOLT11 invoice. Some implementations are experimenting with Lightning Addresses that resolve to BOLT12 offers instead, which would preserve the familiar email-like UX while gaining BOLT12's privacy and removing the server's role in invoice generation. BIP 353 (DNS payment instructions) also provides a path for human-readable names to resolve to BOLT12 offers via DNS TXT records.

Which format should I use for recurring subscription payments?

BOLT12 is the only format with native recurring payment fields in the specification. An offer can include recurrence parameters that tell the payer's wallet to repeat the payment on a defined schedule. BOLT11 has no mechanism for this, and LNURL-pay can approximate it only through application-level logic on the server. For a deeper look, see our research on BOLT12 recurring subscription payments.

This tool is for informational purposes only and does not constitute financial advice. Protocol specifications and wallet support change frequently. Always verify current implementation status against official release notes before making infrastructure decisions.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →