Not exactly. It uses a coordinator where messages are stored so async comms can happen. The coordinator is a cvm server ( which is basically rpc over nostr contextvm.org ) so relays are just uses as an ephemeral bus for commands/messages. All messages are ephemeral and encrypted so the identity of the sender, receiver or even the cordn being used is totally obfuscated across other cvm traffic. Also coordinators are as dumb as relays and learns nothing (almost, nothing insightful in any case), and ofc you can deploy your own coordinator easily for maximum privacy/sovereignty

Replies (1)

I think this usually comes back to. If I deploy my own coordinator why would I need relays at all then, or can we configure them? That's less moving parts and less harvest now, decrypt later attacks. So can clients talk directly with my coordinator to remove the middleman?