nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5 receiving zaps are fixed for coinos lightning addresses. I see my zap receipt on relays, but it’s is not showing on your note on nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 or nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s do you have a zap service pubkey whitelist? Need to add nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch if you do. nostr:note10smaxjxrr3yv7kyw00zc90j42mzwzlvzv7ftp02t4rmpvzuerw2s5m598r
What are you trying to test with Coinos and zapping. I've used Coinos for a few years and it's been great. Let me send from Coinos to you or collect an invoice.
Describe the process and I'll run it, (other than my own LN node at the moment) I can copy npub etc into Coinos, if that's what we're trying to prove.
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.
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 🤣
