https://diyhpl.us/~bryan/irc/bitcoin/bitcoin-dev/linuxfoundation-pipermail/lightning-dev/2023-July/004017.txt

Didn't know. That's a show stopper right there.

What is the contrast here? Static QR codes for invoices can't be done at all with BOLT11. And how is this related to privacy? Blinded paths is often the feature associated with increased (receiver) privacy - and those can be done with BOLT11 as well.

Where can i find out about this? Just skimmed through bolt12 and couldn't find anything pointing me in the direction of understanding it.

You’re misreading the spec. Maybe ask someone who knows how things are implemented before running to nostr to post next time? nostr:nevent1qqsvmk8z37vp0fv0aap4q5ejchwuwv3splnlavlzz0zar7qhg29340qprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqg5waehxw...

What is the point of bolt12 then? Does it just hide your actual pubkey? I don't get it Now that you mention it I think I remember you mentioning something about this on Vlads podcast recently

Reusing BOLT12 offer per inflow = Good Reusing BOLT12 offer for multiple inflows = Bad Just create an offer PER each usecase.