We could do this on nostr:nprofile1qqsra2ey033mkdwl5w8q0jss9ak69zafh82xsuvhwsaauw3trkq2amgpz9mhxue69uhkummnw3ezuamfdejj7qg7waen5te0vask6etn9enkzmt9wf68ymmw9ehx2ap6xsurgwp0qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99u247xz7 with the boosting of locations. 👀
Discussion
Would this mean modifying nip-57? Cause zaps currently must have at least a nostr pubkey that is being zapped.
No, boosts currently go to BTC Map and so we could use our pubkey.
Or a zap split if the merchant is a Place (new kind being worked on). Although that is more a merchant tip rather than a boost (which provides value to the merchant in other ways).
In that case, you could create zaps for locations using your pubkey and `i` tags using OSM node as the identifier. Maybe something like ["i", "osm:node:10840926352", "https://www.openstreetmap.org/node/10840926352%22%5D.
Another way is to just create Nostr events for every location and the use https://lnurlzap.vercel.app to create LNURLs for each location. Anonymous zap receipts are broadcasted whenever these LNURLs are paid. I’m going to make an npm package to generate the LNURLs.
Yeah, I'm against the blanket creation of Place events. We think they should be created by merchants when they are ready.
Can’t you create the Nostr event for them when they create the place?
I just published the package to generate zap LNURLs.
Yep, that could work.
Will look into it as we nostrfy!
Exactly. I literally just referenced NIP-73 from the Places NIP after listening to that nostr:nprofile1qqs2m82zyqlayjqw5tjuf3j9jwszwuy2a03tq24xp0tmr4nxm2jmprgprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0hpztpr pod and discussing with nostr:nprofile1qqsqvcu68pkfcyq5y9mz9n9u7sys33835rpnuglc6mtg7j4lv40c7ugpr9mhxue69uhkummnw3ezuum9vfshxarf0qhxgetk9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0nx4nqe.
Yesss 😎🤓