← Back to XaephyrComms Secure P2P Connect
XaephyrComms

XaephyrComms Secure P2P Connect · Network Architecture

Message Delivery Path: Client-to-Client via Relay

A logical representation of the network path a message follows between two clients. No direct connection exists between them; all traffic is routed through public relays, with messages encrypted prior to transmission.

PC — Alice

npub1fox21...

A cryptographic keypair is generated locally within the browser. The private key never leaves this device. Messages are encrypted here prior to transmission.

wss:// (TLS)
Publishes an encrypted, gift-wrapped NIP-17 event

Nostr Relays

relay.damus.io
nos.lol
relay.nostr.band

Independently operated store-and-forward servers, not affiliated with XaephyrComms. Relays route the encrypted event but cannot access its contents.

wss:// (TLS)
Recipient's subscription matches their public key; the relay delivers the identical encrypted event

PC — Bob

npub1wolf09...

Only the recipient's private key can decrypt this event. Decryption occurs locally; relays never possess this capability.

Reply traffic follows the identical path in reverse; no alternate route exists.

Information Relays Can Access

  • The recipient's public key, required for the relay to route the event correctly
  • The approximate publication time of an event, intentionally obscured by the protocol to resist precise timing correlation
  • The connecting IP address of any client publishing or retrieving an event, consistent with standard web traffic

This diagram presents a simplified, logical view of the architecture. In practice, each client maintains connections to all three relays for redundancy, rather than a single path.

p2p.xaephyr.net