I built a post-quantum encrypted messenger in the browser

说明与用途

chat‑app 展示了如何在浏览器中实现后量子 E2EE，使用混合密码学和盲身份验证，服务器无法看到明文或用户身份。

问题

Most web messengers either skip end‑to‑end encryption or use classical key exchange vulnerable to future quantum computers, exposing chat history to retroactive decryption.

结果

chat‑app demonstrates that a browser‑native messenger can achieve post‑quantum E2EE with hybrid ratchet and blinded authentication, keeping plaintext and user identities hidden from the server while providing full messaging features.

工作流

• 1. User logs in via Bale OTP or quick test login.
• 2. Client generates a hybrid key using ML‑KEM‑768 and ECDH P‑256, feeds secrets into HKDF‑SHA256, and derives a fresh AES‑256‑GCM key per message.
• 3. Client blinds its identity with Ristretto255‑VOPRF, sends blinded token to server, receives DLEQ proof, and unblinds to obtain an unlinkable routing token.
• 4. Messages are sent over Socket.IO/WebSocket, with out‑of‑order handling via a bounded in‑memory vault and group key rotation via a deterministic FSM.
• 5. Server forwards ciphertext and blinded tokens only, never seeing plaintext or identities.
• 6. Messages are stored in PostgreSQL or an atomic JSON fallback, surviving redeploys.
• 7. Optional features: typing indicators, reactions, voice notes, file attachments, read receipts, etc.
• 8. Users can edit, delete, pin, forward messages and use read receipts.
• 9. Admin dashboard is available at an obfuscated server‑side path.
• 10. The demo is available at https://chatapp-server-1i2a.onrender.com.

证据

I built a post‑quantum encrypted messenger in the browser

来源

chat‑app: a real‑time Persian web messenger where every message is protected by PQ‑MPRBA, an original browser‑native protocol combining a hybrid post‑quantum ratchet with blinded authentication.

来源

The server is deliberately a zero‑knowledge forwarder: it routes ciphertext and blinded tokens, nothing more.

来源

It has not been independently audited.

来源