Replying to Avatar bumi

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.
Avatar
k00b 2y ago

Yeah, npubs are bech32 encodings of the pubkey and are meant for user facing pubkeys.

In the protocol pubkeys are usually encoded as hex.

Reply to this note

Please Login to reply.

Discussion

89
nobody 2y ago

Yes. We are just saying.... in your json you have OUR user hex.... whereas Alby/WoS have their hex 🤔

89
nobody 2y ago

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

Avatar
k00b 2y ago

WoS/Alby have it right I think.

89
nobody 2y ago

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

Avatar
k00b 2y ago

Yeah I'm signing it and everything ... just returning the wrong pubkey on the lnurl endpoint.

Is it still free if I zap you?

89
nobody 2y ago

Heheh not if you zap me lol v4v

89
nobody 2y ago

Oh shit, appreciate it. I'm coming to Rust lesson this Saturday. I'm dumb, but I'll be there... are you? Cheers mate

Avatar
k00b 2y ago

Yeah! I'll be around the lab working at least.

89
nobody 2y ago

Oh, no clue if MeetUp address is at the PlabLab.... I was once at ABC...and once at PBS 😭year ago (I broke a beer, that's me)... sorry folks