BOLT 12 Offers Explained: Reusable Lightning Payment Requests

BOLT 12 Offers explained: learn how reusable offers request unique invoices through onion messages, blinded paths, TLVs and payer proofs.

Offer, request and invoice

A BOLT 12 offer is a reusable description from which a payer requests a fresh invoice. The payer sends an invoice_request and the recipient responds with a signed invoice containing payment details. This avoids reusing one BOLT 11 invoice for multiple attempts and lets a merchant publish a stable QR code while issuing a unique payment condition for each payer.

Start with the validating node, because the ASIC only hashes the candidate header it receives. Record the node release and the pool component that assembled the block. If those facts are unknown, the operator cannot show which rules were actually applied before electricity was committed to the work.

Reusable does not mean payable forever

An offer can include an absolute expiry, quantity limits, issuer information, currency or amount guidance and feature requirements. The resulting invoice has its own payment hash and expiry. Wallets must validate both stages. A cached offer may remain readable while its issuer is offline or unwilling to issue an invoice. So the offer itself is not proof that payment will succeed.

Treat status dashboards as observations, not as the source of truth. Compare them with an independently operated node and retain the raw deployment or template response. Period boundaries, chain reorganisations and cached pool pages can otherwise make a correct-looking percentage describe the wrong state.

Onion messages

Invoice requests and replies can travel as Lightning onion messages without carrying a payment. The sender wraps routing information so intermediate nodes forward the message without reading the complete payload. Support depends on node features and connectivity. Message delivery is best effort and separate from the later HTLC route used to pay the invoice.

Build the failure response before the boundary arrives. Define which rejection messages trigger an alert, who can pause a template source and how failover is prevented from returning miners to the same faulty validation stack. A second hostname is not independent when both endpoints share one node.

Blinded paths and recipient privacy

An offer can include blinded paths that reveal an introduction point but obscure the recipient and later hops. Each node learns only what it needs to forward the message. Privacy depends on route construction, anonymity set and implementation support. Repeated probing, timing or a small network can still reveal information. Blinding is a tool, not an absolute anonymity guarantee.

Separate readiness, signalling and enforcement in the operating log. Readiness is a claim about software and process, signalling is data carried by blocks, and enforcement is a validation result. Combining them into a single supported or unsupported label hides the point at which revenue is actually at risk.

TLV encoding and extensibility

Offers, invoice requests and invoices use typed length-value streams with rules for unknown even and odd feature bits. Merkle-style signature commitments allow selective field proofs. The ASCII form uses prefixes such as lno and a bech32-style data string. Implementers must follow canonical encoding and validation rather than treating the string as an ordinary BOLT 11 invoice.

Map responsibility across the full path: validating node, template server, pool protocol, proxy, firmware and ASIC. For each layer, state what it can alter and what it merely relays. This prevents a version-bit setting in firmware from being mistaken for complete consensus-rule support. Relate that responsibility map to the pool and job-control boundary in our Stratum V2 guide.

Payment and payer proofs

Knowledge of a BOLT 11 payment preimage proves an invoice was paid but not who paid it. BOLT 12 invoice requests can include a payer key, and proof structures can support selective disclosure. Businesses still need order records, refund authentication and data-protection controls. Cryptographic proof does not replace every legal or customer-service requirement.

Test the primary and failover paths with the same checks. Compare chain tip, chainwork, deployment state, required rules and template age, then save the result with a timestamp. The process should be repeatable by another operator without relying on an undocumented pool conversation.

Deployment checks

Confirm wallet and node feature support, onion-message reachability, blinded-path handling, offer expiry and invoice validation. Test fixed and payer-specified amounts, duplicate requests, refunds and offline recipients. Preserve the exact offer and resulting invoice in records. Because the BOLT repository remains an evolving specification, pin and document the implemented version.

Turn the conclusion into a business decision. State which chain and settlement venues the operation intends to serve, the maximum acceptable stale-block exposure and the point at which mining pauses. This connects protocol evidence to electricity cost, pool revenue and payout finality.

Operator decision record

A concise decision record for BOLT 12 Offers explained should name the source documents, their dates, the node release tested, the responsible pool or template provider and the exact trigger for action. Include screenshots or machine-readable output for the deployment state. But keep the raw node response as the stronger evidence.

State whether a change affects policy, block construction or consensus validity, because those layers have different failure costs.

Run the check on every production and failover path. Confirm that monitoring alerts on stale templates, unexpected chain tips, rejected proposals and a rise in stale shares. Keep rollback instructions for node and pool configuration. But do not roll back across an active consensus boundary without understanding the rules the older release enforces.

If the evidence conflicts, pause the affected path and investigate before committing more electricity to uncertain work.

For related background, read our plain-English BIP-110 guide and technical BIP-110 review. Those articles use a modern proposal to show why signalling, activation, template construction and accepted chain history must be examined separately.

Conclusion

Bolt 12 offers explained is best understood as a defined interaction between validating software, mining infrastructure and economic acceptance. The safest operator does not infer consensus from a dashboard percentage or a pool slogan. They verify the rule source, the activation boundary, the template fields and the chain their payouts ultimately settle on.

That discipline reduces the chance of hashing an invalid or commercially unwanted block.