Nostr Web Client

NWC wallets don't have static IPs and are behind firewalls too. Clients send ephemeral events as requests to wallet pubkey on some relay, wallet subscribes to requests and replies in a similar way tagging the client pubkey.

Same way wallet could talk to a mint doing RPC using ephemeral events.

NWS is doing similar thing but with a much more complex setup - enter/exit nodes socks5 etc, and the payload is arbitrary binary data, wheres mint RPC would be much simpler and more structured - wallet just connects to a relay and writes/reads some encrypted events.

calle 1y ago

Yeah we're not inventing a protocol, just changing the transport layer. Http/s still works like it did before, often no changes necessary to the client and server software.

Reply to this note

Please Login to reply.

Discussion

brugeman 1y ago

So to use a mint which is behind NWS from my browser I would have to set socks5 entry node as proxy?

calle 1y ago

You can use a public socks5 entry node since the traffic will be encrypted via https

calle 1y ago

Or: you can send the requests directly from JS running in your browser through nostr, skipping the entry node.

brugeman 1y ago

So is there a NIP or something for sending requests directly through nostr to a mint?

brugeman 1y ago

Ok I got it, I guess I could form the http request as nws events in js to simulate the behavior of entry point. Thanks, sounds interesting!

brugeman 1y ago

I wonder if I could bypass cors this way to show link previews more reliably...

brugeman 1y ago

This is gonna get out of hand 😂