nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr
I was wondering if you could please take a look at NWC in NoStrudel with self-custodial solutions. It's best documented, and I believe applies to NoStrudel as well. Here's a reference that describes NoStrudel's behavior pretty well:
I'm not sure NIP-42 auth mixes well with NWC (nostr wallet connect)...
NWC goal is to allow you (or any other app) to access your wallet in a permission manor from anywhere. if the relay your using requires NIP-42 auth then that seems to directly contradict NWC
Thank you for your reply! I understand your reasoning.
It actually does. I added zap support to ligess (https://github.com/mutatrum/ligess/) , and that has a single purpose relay for handling zaps. Having AUTH on that relay is one more layer of shielding for snooping eyes.
It's also part of the NWC NIP: https://github.com/nostr-protocol/nips/blob/master/47.md#using-a-dedicated-relay
Hope this helps.
If its enforcing AUTH for privacy, then what key is expected to authenticate with the relay? the users key or the temporary key created for the NWC connection?
If its the users key that seems worse for privacy unless you own the relay...
