BOLT 12 Offers

Definition: BOLT 12 Offers is a Lightning Network protocol for reusable payment requests. A recipient publishes an offer; a compatible payer requests a fresh invoice through Lightning; and the recipient returns that invoice for the payer to review and pay. The offer is not an invoice or a payment, and publishing one does not move bitcoin. 1

Date created ACINQ’s Eclair v0.11.0 release notes, dated December 4, 2024, said BOLT 12 had been accepted into the Lightning BOLTs. This is a specification milestone, not a Bitcoin network activation date. 4
Protocol specification Read BOLT 12
Directories Bitcoin Directory

How an offer payment works

BOLT 12 separates a reusable offer from the invoice that authorizes one particular payment. In the common customer-to-merchant flow, the merchant publishes an offer, often as a QR code or link. A compatible wallet reads it and sends an invoice request over Lightning. The merchant’s node replies with an invoice, and the payer’s wallet presents the details for approval. The wallet then attempts the Lightning payment described by that invoice. 1

  1. Offer: The recipient publishes a reusable request that can contain details such as the issuer, description, amount rules, expiry, or supported chains.
  2. Invoice request: The payer’s node asks the recipient for an invoice. The request can include payment-specific details, such as the amount the payer chooses when the offer allows it.
  3. Invoice: The recipient returns an invoice for that request. It contains the payment information the payer’s wallet needs to attempt one payment.
  4. Payment: The payer checks the amount and recipient context in the wallet, then authorizes or declines the payment.

This exchange also supports other arrangements, such as a merchant asking a customer for an invoice to pay a refund. The offer and invoice-request formats provide the negotiation data; Lightning still carries the resulting payment. 1

What the offer contains

BOLT 12 offers use the human-readable prefix lno. An offer can be long-lived and can describe a fixed amount or allow the payer to supply one. Depending on the offer and what the wallet supports, its fields can also describe a currency, item quantity, expiry, or recipient information. The invoice request and invoice are separate messages with their own fields; changing an offer does not itself create or settle a payment. 1

The recipient can publish an offer without publishing a new invoice for every customer. A wallet that understands BOLT 12 can contact the recipient’s node to request a fresh invoice for the current payment. This is why an offer can be reused while the invoice is specific to the payer’s request.

BOLT 12 and BOLT 11

BOLT 11 defines the familiar Lightning invoice format. A BOLT 11 invoice is created for a particular payment; it can be shared as text or a QR code and is typically replaced when a new payment is needed. BOLT 12 adds a reusable offer and an invoice-request exchange so a payer can obtain a fresh invoice from the recipient. The two formats can coexist: BOLT 12 is not a promise that BOLT 11 support is unnecessary or that every Lightning wallet can pay an offer. 12

CryptoGloss also covers the separate Bitcoin Payment URI (BIP 321). BIP 321 can carry a BOLT 12 offer using the lno payment-instruction key; it is a way to package payment instructions, not the offer protocol itself. 16

Privacy and practical limits

BOLT 12 supports blinded paths, which can help a recipient avoid revealing a direct public route to its node in an offer. That is a privacy feature with limits, not an anonymity guarantee. A public offer can reveal information about its issuer or purpose, and payment amount, timing, wallet behavior, or other data can still help connect activity. The exact details depend on the offer, node, wallet, and route used. 1

  • Check that the wallet recognizes the offer and shows an invoice before approving a payment.
  • Confirm the displayed amount, currency, recipient, and any expiry information. An offer code is not proof that the issuer is trustworthy.
  • Support varies among Lightning implementations and wallets. Core Lightning documents commands for listing offers, Eclair’s release notes document BOLT 12 payment support, and LND tracks its own implementation work separately. Check the current documentation for the software you use. 345

History

  • December 4, 2024: ACINQ’s Eclair v0.11.0 release notes said BOLT 12 had been accepted into the BOLTs and described full offer-payment support in that Eclair release. The same notes also discuss configuration limits for creating offers, so this milestone should not be read as support across every wallet or node. 4
  • April 16, 2026: Lightning Network Daemon opened a public BOLT 12 implementation-roadmap issue. As of this page’s update date, that issue remains open; its status is specific to LND and does not describe every Lightning implementation. 5

Last updated: 2026-11-12

Related Terms

Related Articles

These articles offer broader wallet, Bitcoin-fee, and market context; none is a dedicated BOLT 12 guide.

See Also

Sources

  1. Lightning Contributors, “BOLT #12: Negotiation Protocol for Lightning Payments,” Lightning BOLTs repository, accessed November 12, 2026.
  2. Lightning Contributors, “BOLT #11: Invoice Protocol for Lightning Payments,” Lightning BOLTs repository, accessed November 12, 2026.
  3. Core Lightning Contributors, “listoffers,” Core Lightning API Reference, accessed November 12, 2026.
  4. ACINQ, “Eclair v0.11.0,” release notes, December 4, 2024.
  5. Lightning Network Daemon Contributors, “BOLT 12 Implementation Roadmap,” issue #10736, opened April 16, 2026, accessed November 12, 2026.
  6. Bitcoin Improvement Proposals, “BIP 321: URI Scheme,” assigned November 15, 2024, accessed November 12, 2026.