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

nostr:nevent1qqsvmk8z37vp0fv0aap4q5ejchwuwv3splnlavlzz0zar7qhg29340qprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqg5waehxw309ahx7um5wghx77r5wghxgetkqyf8wumn8ghj7mmxve3ksctfdch8qatz9mjchy

Reply to this note

Please Login to reply.

Discussion

I appreciate the correction you offer in the post I reply to below, and I think this is a good recommendation: for good privacy, don't reuse a bolt12 or any other payment string across multiple services. Instead, make a new payment string for each service you use.

nostr:nevent1qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagqyrqhc0s0qq2ztxl83375cxekhpr5wmlg9at8zzux9aa9dglyp3wfucj0d0g

I also cross-posted your correction on twitter so that it gets more visibility:

https://x.com/super_testnet/status/1894009493068906633