Ah, this maybe where lnbits LNURLp is making things difficult.

In the invoice description, instead of having the signed kind 9734 it replaces it with the “items description, which is a required field, I wrote “zaps”. And now every invoice that gets paid, the description says zaps instead of the kind 9734 event.

Hence no zaps are showing on my notes anymore?

Again maybe, I’m just trying to trouble shoot where this is all falling apart on my node.

Damus zaps seem to be fine, Amethyst and Primal zaps are not showing up.

Reply to this note

Please Login to reply.

Discussion

Damus doesn’t display any of the zaps I receive to my address at Alby Hub. It’s the only client that has this problem that I’ve tested. I finally got back on Primal again today (there was a bug with how it handled my follow list that just got fixed) and after switching my address to primal.com I can see zaps on Damus again.

damus has never had issues with any zaps except invalid ones. we strictly validate zaps to prevent people from faking them. the only thing this says is that other clients are not validating them properly, or perhaps the alby hub zapper is not sending the zaps to the right relays.

its possible alby hub has introduced some strange edge case that is causing it to be incorrectly marked as an invalid zap, but I have yet had time to investigate

Hopefully this is an easy bug to diagnose and fix because otherwise Alby Hub is the most seamless and fastest self-custodial solution for zapping, and I would love to see more people using it on Nostr.

https://github.com/damus-io/damus/issues/2363