The problem was on the receiving end specifically for zaps and not regular lightning payments, but they fixed it. Now the problem seems to be on the nostr client side. I don’t see the zaps on nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5's note even though the zap receipt was broadcast by coinos.
Discussion
The zap shows up on my own app, so my theory is Damus and Primal are filtering the zaps in some way that I’m not
https://notazap.vercel.app/note1cmpmjyu08he89adhlzqvuqvnv9jc3szhtnxxnnqssx9x7w90hxqq03uqsq
I checked that nostr account and I see the zap notification on Nostur but I don’t see the amount on the note and it says it’s an “unverified zap” whatever that means. I don’t see it at all on Primal.
nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 what does unverified zaps mean?
Unverified means the zap receipt is not coming from the wallet provider published on the recipient’s profile
nostr:npub12ekpvme6m2cv37a9mgq4kzemej8tx6ttg40j582rh77ewpvkg65qj8tq0f the pubkey that the coinos LNURL server returns doesn’t match the pubkey that broadcasts the zap receipts.
Pubkey that the LNURL server returns is b38877ef65530f09e6db43bb8ec141c38cd01f9a6436d563dddcc3b156a01365
Zap receipt is published with ba80990666ef0b6f4ba5059347beb13242921e54669e680064ca755256a1e3a6
Looks like that first pubkey you mentioned (the incorrect one) corresponds to the Pubkey CoinOS has assigned to my account.
Ah. That’s not correct. I just filed another issue. It’s supposed to be the pubkey that is being used to broadcast the zap receipts. Now I understand why no one has been using coinos as their lightning address on nostr. I think their LNURL server was never correctly set up for zaps.
I hope they’re ready for the next zapathon once it’s fixed 🤣