Technical Whitepaper • WP-SYNC-2026
Multi-Device Sync & Conflict Resolution Specification
How decentralized Bring-Your-Own-Storage (BYOS) achieves zero-loss concurrency without central ACID database honeypots.
🔄
1. Vector Clock Tracking
Every vault commit carries a monotonic Lamport timestamp and device ID header embedded inside the encrypted envelope.
🛡️
2. Client-Side Resolution
Conflict merges execute purely in local RAM after AES-256-GCM authentication. Google Drive never inspects vault contents.
📦
3. Non-Destructive Forks
If offline simultaneous writes occur, the newer write adopts the main slot while divergent keys are preserved as conflict snapshots.
Multi-Device Concurrency Protocol State Machine
Visualizing two offline devices reconnecting with divergent mutations.
[T0: BASELINE] Device A & Device B synchronized at Lamport Epoch V1 (Hash:
SYNCHRONIZED 0x7f8a...) [T1: OFFLINE FORK] Device A updates Stripe Key (V2-A) • Device B creates AWS Secret (V2-B)
CONCURRENT OFFLINE EDITS [T2: RESOLUTION] Client merges non-conflicting item sets into V3; archives snapshot as
CLEAN UNION MERGE (0 LOSS) vault.conflict.v2b.enc Architectural Comparison: Concurrency vs Privacy
| Architecture | Concurrency Model | Honeypot Exposure | Conflict Recovery |
|---|---|---|---|
| 1Password / LastPass | Central AWS Cloud DB locks | CRITICAL: All vaults on company servers | Server timestamp overwrites |
| Bitwarden | Central PostgreSQL / MSSQL | HIGH: Central server metadata liability | Last-Write-Wins (silent replace) |
| AuricPass Sovereign | Decentralized BYOS (Drive/iCloud) | ZERO: €0 company honeypot liability | Non-destructive snapshot archive |