Multi-Device Sync

Overview

Your HUMΛN Passport isn't tied to a single device—it syncs securely across your Device Mesh: phone, laptop, tablet, watch, and any other trusted device you own. This creates a distributed personal identity network where no single device holds complete authority, and losing one device doesn't mean losing your identity.

Why Multi-Device Sync?

Think of it like: Your phone, laptop, and tablet form a secure "council" where any majority can authenticate you—even if one is stolen or broken.

How Device Mesh Works

HUMΛN uses a threshold identity model to distribute trust:

1. Device Enrollment: Each device gets a unique Device Passport Key 2. Threshold Authentication: Any N-of-M devices (e.g., 2-of-3) can authenticate you 3. Encrypted Sync: Each device holds an encrypted replica of your Passport data 4. Local-First: Data originates on your device, encrypted before sync 5. Cloud-Agnostic: You choose where encrypted data is stored (iCloud, Google Drive, OneDrive, S3, etc.)

`` ┌─────────────┐ ┌──────────────┐ ┌───────────────┐ │ Phone │────│ Laptop │────│ Tablet │ │ (Device 1) │ │ (Device 2) │ │ (Device 3) │ └─────────────┘ └──────────────┘ └───────────────┘ │ │ │ └────────────────────┼─────────────────────┘ │ ┌────────▼────────┐ │ Encrypted Sync │ │ (Your Cloud) │ │ iCloud/Drive/ │ │ Self-Hosted │ └─────────────────┘ ``

Any 2 of these 3 devices can:

SDK Examples

1. Enroll a New Device

2. Sync Passport Updates Across Devices

3. Recover Identity After Device Loss

Use Cases

1. Add Work Laptop to Personal Device Mesh

Scenario: You have a phone and personal laptop (Device Mesh). Now you want to add your work laptop.

2. Revoke Compromised Device

Scenario: Your phone was stolen. Immediately revoke its access using remaining devices.

3. Peer-to-Peer Local Sync (No Internet Required)

Scenario: You're offline but have multiple devices nearby. Sync via Bluetooth/Wi-Fi Direct.

Conflict Resolution

When multiple devices update the Passport simultaneously, conflicts are resolved using:

1. Newest Valid Signature (Default)

// Device A and Device B both add capabilities offline
// When they sync:
const resolvedUpdate = {
  capability1: { timestamp: '2026-01-10T12:00:00Z', signature: '0xabc...' }, // Device A
  capability2: { timestamp: '2026-01-10T12:05:00Z', signature: '0xdef...' }, // Device B (newer)
};
// Device B's update wins (newer timestamp + valid signature)

2. Manual Resolution (Human Override)

await HumanOS.Passport.resolveConflict({
  conflictId: "conflict-abc123",
  resolution: 'manual',
  selectedVersion: 'device-b-version', // Human chooses
});

Security Considerations

DO:

DON'T:

Privacy by Design

HUMΛN never sees your Passport data:

We cannot:

Next Steps

---

See Also