Step-by-Step: How Labyrinth 1.1 Strengthens Your End-to-End Encrypted Backups

Introduction

When you send a message via Messenger, you expect it to be safe—even if you lose your phone, switch devices, or take a long break between sign-ins. Labyrinth, Meta's encrypted storage system, has always aimed to make that possible. Now with version 1.1, a new sub-protocol takes reliability further by ensuring messages reach your encrypted backup the moment they're sent, rather than waiting for your device to come online. This guide walks you through how Labyrinth 1.1 works, what it changes, and how you can benefit from more consistent end-to-end encrypted backups.

Step-by-Step: How Labyrinth 1.1 Strengthens Your End-to-End Encrypted Backups — Source: engineering.fb.com

What You Need

Understanding of End-to-End Encryption (E2EE): Familiarity with how E2EE works—messages are encrypted on the sender's device and decrypted only on the recipient's device.
A Messenger account: Labyrinth is built into Messenger’s encrypted backup system. This guide is relevant for anyone using Messenger with encrypted backups enabled.
Interest in protocol improvements: No technical background is required, but knowing that Labyrinth handles message storage on the server side without reading content will help.
Access to the white paper (optional): For deeper technical details, you can read the updated Labyrinth Encrypted Message Storage Protocol.

Step-by-Step: How Labyrinth 1.1 Improves Backup Reliability

Step 1: Understand the Old Way of Backing Up Messages

Previously, when you sent a message in E2EE mode, the encrypted message would be stored locally on your device. It would only be uploaded to the backup server once your device came online and synced. If you lost your phone before that sync happened, or if you switched to a new device without a recent backup, those messages could be lost forever. This delay created a vulnerability: any gap between sending and backing up meant potential data loss.

Step 2: Learn What the New Sub-Protocol Changes

Labyrinth 1.1 introduces a sub-protocol that shifts the timing of backup. Instead of waiting for the recipient's device to come online, the sender directly places each message into the recipient's encrypted backup at the moment of sending. Think of it as dropping a sealed envelope into a locked box that only the recipient can open. No one—not Meta, not a third party—can read that envelope. This ensures that even if the recipient's device is offline, the message is safely stored in the backup server, encrypted and waiting.

Step 3: See How Messages Are Wrapped and Stored

Each message is wrapped with a unique message encryption key. The sender uses this key to encrypt the message before sending. Then, instead of just sending the encrypted message to the recipient's device, the sender also stores the encrypted message (with the key) into the recipient's backup area on the server. This is done through the Labyrinth protocol, which ensures the encryption keys themselves are never accessible to the server. The result: the message is backed up instantly, without requiring the recipient's device to be online.

Step 4: Recognize the Benefits for Device Loss, Switching, and Gaps

With this new approach, your message history becomes far more resilient:

Lost a device? As long as you had encrypted backups enabled, all messages sent to you (even after you lost the phone) are waiting in your backup, ready to restore when you log in on a new device.
Switched devices? No more waiting for old messages to sync from the previous device. Because backups are updated in real-time as messages are sent, your new device can pull the full history from the server.
Long gap between sign-ins? Even if you haven't opened Messenger for months, messages continue to be added to your encrypted backup. When you finally sign in, everything is there.

Step 5: Check the Impact on Your Messenger Experience

Meta has already begun rolling out Labyrinth 1.1 broadly to Messenger users. Early results show meaningful gains in backup success rates and more people restoring complete message histories when changing devices. As a user, you don’t need to do anything—the upgrade happens on the server side. However, you should ensure that your encrypted backups are enabled in Messenger settings. Go to Settings > Privacy > Encrypted Backups and make sure the feature is turned on.

Step 6: Explore the Technical Details (Optional)

If you're a developer or privacy enthusiast, the updated white paper titled “The Labyrinth Encrypted Message Storage Protocol” provides the full specification. It explains the cryptographic primitives, the new sub-protocol’s design, and how it maintains E2EE guarantees while eliminating the online requirement for backups.

Tips for Getting the Most Out of Labyrinth 1.1

Keep encrypted backups enabled: Without this setting, your messages won’t benefit from the new protocol. Verify it’s active on all your devices.
Use a strong account password or PIN: Encrypted backups are protected by a recovery key derived from your password or PIN. A weak one reduces security.
Don’t rely solely on device storage: Even with Labyrinth, it’s good practice to occasionally check that your backup is up-to-date—though with 1.1, it will be automatically updated as you chat.
Remember that only the sender and recipient can decrypt: Labyrinth ensures Meta cannot access message content. This is the core of E2EE—your trust is in the math, not in the service provider.
Stay informed: Follow Meta’s engineering blog for future updates to Labyrinth and other privacy features.

In summary, Labyrinth 1.1 makes end-to-end encrypted backups more reliable by eliminating the dependency on the recipient’s device being online. Messages are backed up instantly as they’re sent, providing a seamless and secure experience even after device loss, switching, or long absences.

Tags: