A simple block diagram on how two instances of #nostr #safebox instances dynamically interact with one another. I have successfully de-coupled the interaction so that each user interacts with their https server only and all interactions are marshalled through relays. For example the QR that is scanned contains only the #nauth information required to create the channel - the npub, the relays to listen on etc. What is really cool is that I can have a #nostr #safebox running as localhost, behind a firewall, and it can communicate seamlessly with any other nostr safebox on the planet, automatically. Throw in WebSockets, I have full-duplex dynamic interaction channels intermediated via relays. For fun, I might add in real-time chat (but not to replace @White Noise ) Plus the added bonus - I decided to bite the bullet on integrating post-quantum algorithms, so no PQC-FUD. The next major lift is integrating Blossom blob support. I have mapped out the approach and plan to add the same PQC-resistant scheme for encrypting the blobs. Onward! image

Replies (3)

modalplex's avatar
modalplex 2 weeks ago
Well done. So is the idea that you'll have a safebox client (multibox), or just one that connects to many?
Every safebox instance has its own private key. You can associate it with an owner pubkey (or not) . You can have as many safeboxes as you wish - they are all first class citizens on the nostr network.
A key point here is that the #nauth protocol uses https/TLS as a publicly available road - not as the secure delivery vehicle as does #OAuth. This is basically a state/agent-resistant protocol. Using relays as the secure transmittal backbone, it can punch through, route around anything. View quoted note →