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!

Reply to this note

Please Login to reply.

Discussion

This happens to me a lot on nostrudel as well, nwc to my alby hub. Have you opened a console to see if there were any errors or anything?

There are quite some parties involved until a zap receipt is published. Happy to have a look to make sure everything is fine with your Hub. Can you send us a message at support.getalby.com?

Every time I have looked at the console after it happens, it was a failure to get an invoice. So I don't think it is anything to do with my hub, but thanks!

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.

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!

It's the zap receivers' implementation that is broken, it might not be related to the wallet you are sending from. (But it might, the zap spec requires so much back and forth that it is fucking hard to debug sometimes).

It could be:

1. Recipient's LN node doesn't issue a Zap receipt event

2. OR it is issued but it gets lost/deleted on the relay (less likely)

3. OR Yakihonne checking for the Zap receipt event incorrectly

I would say most likely the problem is 3.

And even if it's not Yakihonne, I would definitely apply a timeout on fetching the Zap receipt, like 10 seconds, then I would just alert the user that the payment might have failed

Usually the problem is #1.

Youre right, most often the root cause is the zap receipt not being issued but the actual problem on the user side is not handling this case by the client well.

As Rizful mentioned it is #1 with yakihonne wallets we have our own http-nostr and we distrbute the receipts normally 🙏

I've noticed this a few times but maybe this is a sign I'm bot zapping enough... Pretty sure the issue is on the receive end. Clients could probably provide more clarity. My only issues with Coinos have been purely user error.

The zapping experience has been re-designed, you may check it out 🙏

Noticed already. Goes smoother now.

awsome 🙏