Basic Nostr — selected stack

IPv4 / TCP / TLS 1.3 / HTTP Upgrade / WebSocket / NIP-01; optional TLS padding credited architecturally; WSS relay hostnames resolved through DNS; regular events proactively published concurrently over two independent relay paths; separate author contexts; no NIP-17/44/42 or secret-gated camouflage; F21: verified event author to reader, not live publishing connection or relay identity; G01 global deployment: WSS relays over conventional BGP-routed IPv4 Internet C08: operator-controlled nostr-rs-relay at b5c1f642e4f4c3b9c54f5d18d66f4c53642076b4, SQLite in_memory=true, bundled URI-enabled SQLite and memory temporary storage; no file logging, persistent WSS-proxy logs, diagnostics export, swap, dumps, hibernation or snapshots. Apply to both selected relays. Regular events remain in RAM until discarded/restart; other readers/relays can retain copies. F37/F38: explicitly selected optional IPv4 router AQM with congestion-dependent dropping and independently administered DiffServ domains; transport-aggregate classification/conditioning, not NIP-01 functionality or universal relay deployment. No RSVP/IntServ application reservation. F39 witness: host one of the already selected native WSS relays, including its TLS endpoint, on the same Linux host as two distinct application processes. Use a stable relay hostname resolving to its assigned host address, separate WebSocket connections, and a subscription to the publishing process author key. Local IP delivery keeps this relay leg on-host; the same author filter and EVENT/REQ interface deliver to a remote subscriber connection. The second independent relay path is retained and may also carry copies. No new broker, NIP or direct-message protocol is added.

Official project website · Logo credits · Methodology and limits