maybe nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq is failing to send zaps to the relays listed in the zap request?
Discussion
Actually sending some test zaps to currently to nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat to try to figure this out. I noticed on my end that I didn't see the zap receipts from nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat , which is super weird, because they are clearly seen on the network.
OK so in our test zap client, we are making a zap event for nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat which includes these relays:
[
[0] "wss://relay.damus.io",
[1] "wss://relay-nwc-dev.rizful.com/v1",
[2] "wss://hist.nostr.land",
[3] "wss://relay.nostr.band",
[4] "wss://sendit.nosflare.com",
[5] "wss://relay.primal.net",
[6] "wss://nos.lol",
[7] "wss://relay.snort.social",
[8] "wss://nostr-01.yakihonne.com"
]
I can manually zap nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat also using nostrudel, and the zap receipt shows up in the browser, with these relays:
The only relay on that list which I’m connected to is the damus one. I used to be connected to those other two.
You are using only one relay? Can you add morfe mainstream relays, maybe the yakihonne and primal relays?
his nostrPubkey (zapper pubkey) is incorrect. its listed as his pubkey, but it should be the zapper pubkey
Is that under nostr profile? What do I change it to?
this is configured by nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq . It looks like they are configuring it incorrectly
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s can you confirm that you believe that this "nostrPubkey" is configured incorrectly?
I think nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is likely right. Currently I am mystified why this is the first time we've run into this issue.
maybe because many clients don’t verify zaps which is pretty bad
nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat I am 94% sure that nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is correct and this was a subtle error with our implementation. I am rolling out out a fix now. Will ping you in about 5 minutes so we can test the fix.
Excellent. Thank you everyone 💜
I’m also 92% sure I understand why our monitoring and tests didn’t trigger the error.
nostr:npub1ghcetnluhryhynhuyj8s2pazldjm27wl40nu6dfeskvpv09twcnsneygat now 99% sure that nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s was right, and our implementation is now fixed.. I just ran some tests on my end and the thing that was previously failing is no longer failing.
Good to know that it’s getting fixed 🫡
"his nostrPubkey (zapper pubkey) is incorrect. its listed as his pubkey, but it should be the zapper pubkey"
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Could you be more explicit about what these terms mean...
"his nostrPubkey"
"zapper pubkey"
"listed as his Pubkey"
thanks
These are my relays currently. I barely removed primal last week.
