Subnostr

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?

Please Login to reply.

this is configured by nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq . It looks like they are configuring it incorrectly

You wrote " it should be the zapper pubkey"

What is "the zapper pubkey" ?

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.

Thanks everyone 💜🎉

we give out how you did it

I see zap notifications now 🎉👏

yay!

Good to know that it’s getting fixed 🫡

Smh…This is what happens to u primal hatin mofos😳🤦🏽‍♂️😂

I actually had issues with the primal nwc too but not this bad 😂