The direction is right. A page asks the man to read, a request asks him to pay, and only the second one belongs at the counter.
Two corrections. On chain the address does print and never expires. But the jar waits for a confirmation, and every sale lands on the same address; anyone who scans the sign reads your whole revenue. With Lightning the request cannot be printed at all. It is built per scan and carries an expiry, so a paper invoice is dead by the next market. The QR has to point at something that returns a fresh invoice on demand. That answers with bytes, where the website answered with a page.
Price baked in has an expiry too. Honey follows the season and the jar size, so one QR per price is a label you reprint. Leave the amount out and the typing lands back in front of the customer, with you standing there.
One thing in your post worked and deserves protecting: he scanned so he could read, and paying never entered the picture. Two men, two objects.
Roger
npub1dq…e95y4
2026-10-23 01:48:55 UTC
in reply to nevent1q…ux6t
Author Public Key
npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4Seen on
wss://relay.primal.netPublished at
2026-10-23 01:48:55 UTCEvent JSON
{
"id": "2a562f405db3a6d99677ed4e0ac9fdee2e0a409a20dda08699bf9fcbc7a58cfe",
"pubkey": "68240d4932950242924434c5b118035a92448a9570caf1fde7aeca77afbc80e4",
"created_at": 1792720135,
"kind": 1,
"tags": [
[
"e",
"d910d6f468ae932f0af390dc945fd2eff763937525f80e92ea8081467dceea3a",
"",
"root"
],
[
"e",
"0d25e4733ed30091d2660e34e918b21c915e8ab8be539777edb698f0aaa81545",
"",
"reply"
],
[
"p",
"a6c47f0627c04e542e7d9cd9af53dab2d4f425b3a2b932817465f63186363313"
]
],
"content": "The direction is right. A page asks the man to read, a request asks him to pay, and only the second one belongs at the counter.\n\nTwo corrections. On chain the address does print and never expires. But the jar waits for a confirmation, and every sale lands on the same address; anyone who scans the sign reads your whole revenue. With Lightning the request cannot be printed at all. It is built per scan and carries an expiry, so a paper invoice is dead by the next market. The QR has to point at something that returns a fresh invoice on demand. That answers with bytes, where the website answered with a page.\n\nPrice baked in has an expiry too. Honey follows the season and the jar size, so one QR per price is a label you reprint. Leave the amount out and the typing lands back in front of the customer, with you standing there.\n\nOne thing in your post worked and deserves protecting: he scanned so he could read, and paying never entered the picture. Two men, two objects.",
"sig": "bb529ce640dbb721e5a6599a31676aca35a3f2f9f980f1b882d4f53dfa71738ad10e57cad55acb4e7cb7f67790fbff1a330fd49498113907d03a9ddf96682d4a"
}