Zapper doesn't need an nsec for publishing zap note!
And Alby Account has nothing to do with your keys. They might have been created and are used within your Alby Browser Extension but they are not linked to your Alby Account.
Discussion
Ohh… so NIP-57-Zap receipt doesn’t need a signed event from the receiver?
the person who requests a zap invoice embeds a signed note into the invoice, called the zap request (kind 9734). this is how you know a person initiated a zap toward you. you don't know for sure if they were the ones who paid it, but its implied.
the lightning node that sends the zap is another signed note (the zap kind 9735). they are typically two different keys. you list the lightning node pubkey in your lightning address and clients use that to authorize zaps from that node.
A user does not send the zap, only the lightning node does when it receives confirmation of payment.
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.
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.
I saw your zap but only because I was able to set my address back to nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg. I’d still prefer to keep my zaps in my nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Hub, but only after it works correctly on nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 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.