Zeq Message

ZSP-secured, encrypted real-time messaging. The node is a store-nothing relay — message bodies are never persisted; only hash-only transit receipts land on the sender's entangled state.

App ID message Runs at /apps/message/ Auth framework sign-in (the /apps/* gate) Chapter Cryptography & Identity

What it does

Real-time 1:1 and group messaging between Zeq identities: send / edit / delete / react fan out over the WebSocket relay hub, with presence, typing, and call signalling. Payloads are ZSP-protected; the relay stores nothing.

API routes behind it

• POST /api/msg/* — relay REST (send, edit, delete, react; member-gated) (api/msg)
• WS /ws/msg — the relay hub (presence, typing, calls, message fanout)
• POST /api/zsp/protect / unprotect — payload protection
• POST /api/files/upload — attachments · POST /api/zeq-auth/session-key — session keys

Reference

• Source: apps/zeq-dev/public/apps/message/