Summary: Whispr is worth cataloging not as just another encrypted-chat app, but as a messaging stack that tries to decompose secure communication into several explicit lower layers: a desktop client with a cryptographic sidecar, a metadata-minimizing relay, an identity server that distributes composite key bundles and MLS key packages, and a newer whitepaper-defined protocol that combines amortized post-quantum MLS with sealed-sender anonymity. The most reusable insight is that Whispr makes the relay / identity / authorship split legible instead of flattening everything into one generic private messenger label. It is also analytically useful because the reviewed sources expose a live architecture drift: the org README still describes an earlier PRGE pairwise-ratchet design, while the March 2026 whitepaper specifies a more ambitious APQ-MLS + BBS+ anonymous-credential stack.
What it does:
Frames Whispr as a decentralized end-to-end encrypted chat system spread across separate protocol, app, relay, identity, and cryptography repositories under the whisprchat organization
Uses a desktop architecture where a React/Tauri client talks to a Rust sidecar that holds keys, manages protocol state, and handles relay and identity-server communication
Defines a relay role that stores and forwards sealed entries by topic and is meant to verify only membership proofs rather than learn message contents or authorship
Uses a separate identity server for registration, challenge-response authentication, profile data, composite public-key bundles, presence/status, device management, and MLS KeyPackage distribution
In the March 2026 whitepaper, replaces a simple one-layer chat design with APQ-MLS: a post-quantum MLS session for key refresh plus a traditional MLS session for application-message efficiency, linked by periodic PSK export
Adds sealed sender using BBS+ anonymous credentials, a hybrid ML-KEM-768 + X25519 transport handshake, SHA3-256 fingerprints over composite key bundles, and feature surfaces such as message editing, deletion, emoji reactions, typing indicators, direct messages, multi-relay federation, and a server-discovery directory
Key claims:
Whispr clears the corpus bar because it exposes a useful lower comparison layer between wallet-messaging protocols, privacy transports, and app-centric chat products: who knows sender identity, who distributes group state, who authenticates long-lived user identity, and where post-quantum guarantees are actually injected.
The strongest design move in the whitepaper is the split between session A and session B in APQ-MLS. Quantum-resistant key material is refreshed in a heavier ML-KEM / ML-DSA MLS session and periodically exported into a lighter X25519 / Ed25519 MLS session that handles everyday messages.
The relay model matters analytically because Whispr is not merely encrypting content in transit; it is explicitly trying to hide authorship from the relay as well through sealed sender and BBS+ membership proofs. That makes relay-side metadata power a first-class comparison surface.
The identity server remains a meaningful control surface even in the decentralized framing. The reviewed sources assign it registration, authentication, profile management, composite key-bundle distribution, MLS KeyPackage fetch/upload, and server discovery, which means user bootstrap and key-distribution trust do not disappear just because message payloads are encrypted.
The source set reveals a useful implementation-maturity caveat. The organization README still describes Whispr in terms of PRGE, Ed25519, X25519, and ChaCha20-Poly1305, while the newer whitepaper specifies APQ-MLS, ML-KEM-768, ML-DSA-65, BBS+ sealed sender, and hybrid PQ transport. That gap is exactly the kind of architecture drift worth preserving for later comparison.
Because the public docs surface is still thin and some project web properties appear unstable or paused, this entry should be treated as a mechanism-and-source-triangulation page first, not as confirmation of a mature production messaging network.
Whitepaper: Yes. The strongest primary artifact in this pass is the March 2026 protocol whitepaper source, supplemented by the organization README and the thin public docs surface; see ../whitepapers/whispr-primary-sources-2026-05-14.md.