# Jeff Czyz - BOLT12 Has Arrived (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/42750689) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Jeff Czyz]] **Full Title**:: BOLT12 Has Arrived **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [lightningdevkit.org](https://lightningdevkit.org/blog/bolt12-has-arrived/) **Host**:: [[lightningdevkit.org]] **Highlighted**:: [[2024-07-30]] **Created**:: [[2024-08-03]] ## Highlights - BOLT11 defined an invoice format that, while useful, has some shortcomings. Invoices are communicated out-of-band—typically via a QR code—from recipient to sender. They are signed, making them large and thus difficult for some devices to scan. But more importantly, they can’t be safely reused since they contain a payment hash. ([View Highlight](https://read.readwise.io/read/01j40vbhfx97trphpymm009jcm)) ^752210721 - Someone scanning an offer sends an *invoice request* to the intended recipient, who replies with an invoice containing a unique payment hash. ([View Highlight](https://read.readwise.io/read/01j40vdeg6byaw8nfja7y8rr1n)) ^752214532 - It also contains a *reply path*—another blinded path—back to the sender, allowing the recipient to respond similarly to an invoice without revealing the sender’s node ID. ([View Highlight](https://read.readwise.io/read/01j40vgjnha7jx27ay4kfs1caq)) ^752214783 - This is taken further with the invoice, which contains *blinded payment paths*—essentially blinded paths with some additional payment information. ([View Highlight](https://read.readwise.io/read/01j40vh4pexn1kbp8xvzfbgacg)) ^752214793