OK, I think what you are talking about is that the recipient of your zap is not generating a "zap receipt" .. one of the most difficult and unreliable parts of the zap spec ( https://github.com/nostr-protocol/nips/blob/master/57.md ) ..... Can you tell me, are the failures "consistent per recipient"? You should find that there are some recipients who always produce zap receipts (you see the confirmation) and others that never produce zap receipts (you never see the confirmation). If you look at our home page rizful.com you can see an example of a user (Peter Todd) whose implementation is broken, his implementation doesn't produce zap receipts.
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q , nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch , or nostr:npub1wl3cs46hek62jm4j3x3k5etut3dkghlqfq6satsxa8q5s3tngcps22kjnr ... whoever’s responsible for this, you guys need to fix this bug.
Lately, it’s been happening more and more (feels like 50% of the time) that when I zap a note, I don’t get any feedback. I zap from Yakihonne, the waiting dialog pops up, and then it just sits there for minutes.
In the meantime, I go to the Coinos dashboard and see that the zap actually went through, the Sats were transferred.
But when I go back to the zap window in Yakihonne, the dialog is still there and it looks like the zap hasn’t gone through. Sometimes it just stays like that for half an hour — I know because I went off to do something else and checked back later.
Sometimes I get an error message saying there was no response, but sometimes I don’t. Either way, there’s nothing to do but close the dialog. And even though the zap went through according to the Coinos dashboard, it doesn’t show up under the note.
I get it, it’s all new and buggy and all that, but this is about payments, and it needs to be fixed. Before I knew about this bug, I accidentally zapped the same amount multiple times until I thought to check my Lightning dashboard — and sure enough, there were multiple zaps in a row with the same amount.
Happy to share more details if one of you reaches out!
Discussion
I haven't tested it out, but I think yes. It looks like it depends on the recipient's Lightning wallet.
And yes, it behaves exactly like in your example on your home page.
So the problem lies in the recipient's Lightning wallet?
Yes. This happens to be exactly what we are working on -- benchmarking wallet implementations and seeing where the problems are for zaps. The best way to receive zaps is with an always-on lighting node like Alby Cloud or Rizful.com -- yes, self-hosting is great for other reasons, but we are seeing a LOT of self-hosted nodes that fail to receive zaps, or take 10+ seconds to send zap receipts -- and lots of other problems.
That explains it. Thank you!