Oddbean new post about login | logout 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 @corndalorian's note even though the zap receipt was broadcast by coinos. nostr:nevent1qqsvdsaezw8nmunj7kml3qxwqxfkzevgcpt4enrfesggrzn08zhmnqqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgcwaehxw309aex2mrp0yhxummnwa5x2un99e3k7mgpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzpvvv6zz75nq0uhzwmj2ufnawaaz7xy3qm205fy2mesanyc3cuuklpvdhyn https://njump.me/nevent1qqspkhtqlyl8y0f8r69n5k89p3lau6c26475q9dhawyyeu880n4hj3qprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqyf8wumn8ghj7mmxve3ksctfdch8qatzqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsyg96szvsveh0pdh5hfg9jdrmavfjg2fpu4rxne5qqex2w4f9dg0r5ca0hhup
hmmm
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. https://image.nostr.build/4090387771a48d30f070e136aafe7a6bc4cd8473380a63314d1fc5fbaed4ce5d.jpg https://image.nostr.build/dd4393e71d0c1f469070db4e9898b1a054e590401f778a6ca4fc5ac853a8abf6.jpg
@Nostur what does unverified zaps mean?
@Fabian
Unverified means the zap receipt is not coming from the wallet provider published on the recipient’s profile
@asoltys 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. https://image.nostr.build/844224d653b94ae9e7f1c0d732c2129f61270a525a8dedfb06ab18af22c5dbf7.jpg
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 🤣
