pull down to refresh

When you send a zap and it shows up on Nostr, what happened is that your recipient's Lightning Address server published a note upon receiving the payment to acknowledge reception. See NIP57 for more details about that.
So usually if the zap doesn't show, it's either that:
  • your recipient's Lightning Address server doesn't support this feature,
  • implemented it incorrectly,
  • receipt note publication is failing for some reason,
  • you just don't see the receipt node (because your set of relays and the server's set of relay don't intersect).
Thank you! From my experience it seems that the third and fourth causes you have stated are the most probable because it is an intermittent issue. I would like to zap your answer but I don't know how. I am still learning to use this platform.
reply
Oh that's interesting! So for the same user and Lightning Address sometimes it works and sometimes it doesn't? Is it from the same Nostr client as well? Sometimes the set of relays can change between two clients, which could make the case for cause n°4.
I'm asking because in my own experience it's mostly a persistent issue, which can very often be attributed to cause n°1.
Thanks for the zap!
reply
Only emphasizing that the payments have always been successful as far as I know. The issue is that sometimes it is not displayed on the nostr profile being zapped although most times it is. There is no pattern for nostr clients or nostr profiles:
  • it is intermittent for the same lightning address on the same client
  • it is intermittent for the same lightning address on different clients
  • it is intermittent for the same client on different lightning addresses
reply
Okay, so probably some notes getting lost somewhere 😁
reply
I figured it out how to zap you :)
reply