nws/README.md

Nostr Web Services (NWS)

NWS replaces the IP layer in TCP transport using Nostr, enabling secure connections between clients and backend services.

Exit node domain names make private services accessible to entry nodes.

Prerequisites

• A list of Nostr relays that the exit node is connected to.
• The Nostr private key of the exit node.

Overview

NWS main components

1. Exit node: A TCP reverse proxy that listens for incoming Nostr subscriptions and forwards the payload to your designated backend service.
2. Entry node: A SOCKS5 proxy that forwards TCP packets and creates encrypted events for the exit node.

NWS domain names

There are two types of domain names resolved by NWS entry nodes:

1. .nostr domains, which have base32 encoded public key hostnames and base32 encoded relays as subdomains.
2. nprofiles, which are combinations of a Nostr public key and multiple relays.

Both types of domains will be generated and printed in the console on startup

Quickstart

Using Docker to run NWS is recommended. For instructions on running NWS on your local machine, refer to the Build from source section.

Using Docker-Compose

Navigate to the docker-compose.yaml file and set NOSTR_PRIVATE_KEY to your private key. Leaving it empty will generate a new private key upon startup.

To set up using Docker Compose, run the following command:

docker compose up -d --build

This will start an example environment, including:

• Entry node
• Exit node
• Exit node with HTTPS reverse proxy
• Cashu Nutshell (backend service)
• nostr-relay

You can run the following commands to receive your NWS domain:

docker logs exit-https 2>&1 | awk -F'domain=' '{if ($2) print $2}' | awk '{print $1}'

docker logs exit 2>&1 | awk -F'domain=' '{if ($2) print $2}' | awk '{print $1}'

Sending requests to the entry node

With the log information from the previous step, you can use the following command to send a request to the exit node domain:

curl -v -x socks5h://localhost:8882 http://"$(docker logs exit 2>&1 | awk -F'domain=' '{if ($2) print $2}' | awk '{print $1}' | tail -n 1)"/v1/info --insecure

If the exit node supports TLS, you can choose to connect using the HTTPS scheme:

curl -v -x socks5h://localhost:8882 https://"$(docker logs exit-https 2>&1 | awk -F'domain=' '{if ($2) print $2}' | awk '{print $1}' | tail -n 1)"/v1/info --insecure

When using HTTPS, the entry node can be used as a service, as the operator will not be able to see the request data.

Build from Source

To make your services reachable via Nostr, set up the exit node.

Exit node

Configuration can be completed using environment variables. Alternatively, you can create a .env file in the current working directory with the following content:

NOSTR_RELAYS='ws://localhost:6666;ws://localhost:7777;wss://relay.domain.com'
NOSTR_PRIVATE_KEY="EXITPRIVATEHEX"
BACKEND_HOST='localhost:3338'
PUBLIC=false

• NOSTR_RELAYS: A list of Nostr relays to publish events to. Used only if there is no relay data in the request.
• NOSTR_PRIVATE_KEY: The private key to sign the events.
• BACKEND_HOST: The host of the backend to forward requests to.
• PUBLIC: If set to true, the exit node will announce itself on the Nostr network, enabling other entry nodes to discover it for public internet traffic relaying.

To start the exit node, use this command:

go run cmd/nws/nws.go exit

If your backend services support TLS, your service can now start using TLS encryption through a publicly available entry node.

---

Entry node

To run an entry node for accessing NWS services behind exit nodes, use the following command:

go run cmd/nws/nws.go entry

If you don't want to use the PUBLIC_ADDRESS feature, no further configuration is needed.

PUBLIC_ADDRESS='<public_ip>:<port>'

• PUBLIC_ADDRESS: This can be set if the entry node is publicly available. Exit node discovery will still be done using Nostr. Once a connection is established, this public address will be used to transmit further data. (<ip/domain>:<port>)
• NOSTR_RELAYS: A list of Nostr relays to publish events to. Used only if there is no relay data in the request.