Looking for the macOS AI video creation suite? Visit Wonek Video Studio for Mac (studio.wonek.com) →
Wonek icon Wonek Pre-Release
Cryptography & E2EE · 8 min read

MLS (RFC 9420) End-to-End Encryption Explained: Scaling Private Groups & Multi-Device Chat

First-generation encrypted messengers used pairwise ratchets designed for two phones—forcing group chats and multi-device setups to encrypt keys repeatedly for every participant device. Standardized by the IETF as RFC 9420, Messaging Layer Security (MLS) upgrades group and multi-device E2EE to logarithmic efficiency.

Key Architectural Takeaway Wonek implements MLS (RFC 9420) inside a dedicated Rust cryptographic core, delivering forward secrecy, post-compromise security, efficient group key rotation, and authenticated Noise-protocol QR multi-device enrollment.
Pairwise Double Ratchet vs IETF MLS (RFC 9420) Architecture
Cryptographic PropertyLegacy Pairwise Ratchet (v1 E2EE)IETF MLS — RFC 9420 (Used in Wonek)Why Users Notice the Difference
Member Key Update CostO(N) — scales linearly with devicesO(log N) via asynchronous ratcheting treesInstant membership & key updates across multi-device groups
Multi-Device SynchronizationSeparate pairwise session per linked deviceEach authorized device is a first-class leaf nodeReliable sync across iPhone, iPad, Mac & Apple Watch
Forward SecrecyYes — per pairwise chainYes — epoch-based group key ratchetingPast messages stay unreadable if future state is exposed
Post-Compromise SecurityRequires pairwise message exchange with each peerSingle tree update heals group secret for all membersFaster cryptographic self-healing across entire rooms
Open IETF StandardizationProprietary / de-facto variantsPeer-reviewed IETF RFC 9420 standardAuditable, modern cryptographic design

Why Multi-Device Apple Ecosystems Outgrew Pairwise Sessions

Suppose a 25-person project team uses iPhones, iPads, Macs, and Apple Watches—totaling nearly 80 active client endpoints. Under older pairwise encryption designs, adding or removing a teammate or rotating compromised keys requires linear work across dozens of individual sessions, often causing out-of-sync 'waiting for this message' placeholders.

MLS (RFC 9420) organizes authorized client devices as leaves in a balanced cryptographic tree (TreeKEM). Updating a device's leaf secret refreshes the shared epoch key in O(log N) operations—even when offline teammates are not currently connected.

Inside Wonek's Native Rust Cryptographic Core & Noise QR Enrollment

In Wonek, plaintext never leaves your device unencrypted. Encryption and key schedule derivation run inside a memory-safe native Rust cryptographic core shared across Apple platforms.

When you add your Mac or iPad to your account, Wonek does not upload raw private keys to a cloud backup. Instead, you scan an authenticated QR code that establishes a direct Noise-protocol encrypted enrollment channel between your existing iPhone and the new device.

  1. Install Wonek on your primary iPhone and generate device-local cryptographic identity keys in the native Rust core.
  2. Open Wonek on your Mac or iPad and scan the enrollment QR code to complete an authenticated Noise-protocol device handshake.
  3. Create 1:1 or group conversations where every message, voice/video call key, CRDT document update, and file transfer is protected under MLS (RFC 9420).
  4. Send messages freely to offline contacts—Wonek's offline server queue holds only opaque ciphertext until their devices reconnect.

What Servers and Relays Can—and Cannot—See

Wonek's signaling infrastructure, offline message queues, and fallback media relays never possess group epoch keys or private device keys. Combined with QUIC / WebTransport TLS 1.3 wire encryption, infrastructure nodes handle exclusively encrypted payloads.

Practical Readiness Checklist

Stored locally in your browser—nothing leaves your device.

Frequently Asked Questions

Is end-to-end encryption enabled by default in Wonek group chats?

Yes. Unlike messengers where only 1:1 'Secret Chats' are end-to-end encrypted, Wonek applies MLS (RFC 9420) end-to-end encryption by default across 1:1 chats, group chats, voice/video calls, screen sharing, and file transfers.

How do offline messages work with end-to-end encryption?

When a recipient's device is offline or in Airplane Mode, Wonek queues the already-encrypted MLS ciphertext on the server and delivers it the moment their device reconnects. The server cannot decrypt the queued payload.

How does QR multi-device linking protect my keys?

Scanning the enrollment QR establishes a mutually authenticated Noise-protocol channel directly between your trusted device and the new Apple device, preventing man-in-the-middle server key injection.

Related Guides & Comparison