Nostr client devs, what's the status of zaps?

I noticed that I can't be zapped which is due to my LN node not talking nostr yet but some clients don't even allow tips while others allow tips pretending they were zaps. And then there is note1gmlru8n03uvhvf87zrs5me0an8qpdufs77hg6u8ww3uee7s5nklqf552mm who claims somebody zapped him even without any LN setup which makes me suspect there's clients out there that let you zap all the accounts, potentially custodying the sats until the recipient reclaims them?

Should clients allow tipping if zapping is not possible? I think they should but they should warn the user that the tip will not be shown or attributed.

Reply to this note

Please Login to reply.

Discussion

I zapped⚑️ you fine 😁

I received 21sat twice but no nostr zap event and trying with different clients I saw that some even don't show the :zap: symbol.

Thanks for your tips but snort shows zero zaps.

error fetching ln invoice

My suggestion is to have a zap wallet that is hosted at WoS, and just do the fund transfer when needed! Or use ligess to connect to your node!

https://github.com/Dolu89/ligess

🐢🐾🫑

can you recommend a custodial LN service where one can swipe those sats to an onchain address from time to time (with not extreme fees) :) ?

running LN on a node is sadly not possible in my situation..

That's only possible if the clients doesn't care and validate the service public key. Maybe what you are seeing a workaround implementation where the validation of the zap is skipped.

Maybe somebody should spam fake zaps so those missing checks become unacceptable.

Good example where fighting fire with fire actually works

I guess some people would consider it unethical, especially if it was a considerable amount of zap spam but with some few well placed zaps - 30 million Bitcoin for fiatjaf etc. you could make a point, get heard and not disrupt the network.

Unethical sending fake zaps? I believe it's a really good exercise. What can be broken, should be broken.