afaik the npubs is mainly a representation for users. apps use hex.
we (the zapper/zap provider) sign the zap when the payment is received with that key.
this way clients can validate that the zap event is actually signed by the server that received the payment.
I noticed WoS and Alby have their hex keys, wherease Stacker news has my hex key in their LNURLp json. I guess #[5] does things differently on the back
hmm. afaik zap requests must be signed by the zapper/the zap provider, so I don't think it can be your key. 🤔
The hex in their json is my npub, ia why I was also curious. Maybe they still sign like you say, but json just returns it? Dunno guessing without knowing impls
89d1ce9164f1f172daaa9c784153178cb1dec7912bf55f5dc07e0f1dabe40e6c
Yeah, npubs are bech32 encodings of the pubkey and are meant for user facing pubkeys.
In the protocol pubkeys are usually encoded as hex.
Yes. We are just saying.... in your json you have OUR user hex.... whereas Alby/WoS have their hex 🤔
Why you have our user hex? Don't have to answer cuz it works though 😄I tried Stacker NIP57 the other day. But still bothers me diff provides put diff hex in there. Wondering who is correct for no reason other than knowing
WoS/Alby have it right I think.
Roger. So you are still zapping and signing some receipts using your hex behind scenes, but just erroneously returning user HEX from lnurlp endpoint is my guess 🤙right? Free debug serrrrrr
Oh shit, appreciate it. I'm coming to Rust lesson this Saturday. I'm dumb, but I'll be there... are you? Cheers mate
