Research
0k-sync is built on research, not assumptions. Every major design decision — from the choice of transport layer to the post-quantum cryptographic strategy — was preceded by investigation, comparison of alternatives, and honest assessment of trade-offs. The protocol exists in its current form because each component was validated against real-world constraints before being committed to the specification.
This page catalogues the research that informed the project and links to the featured deep-dive documents.
Research Summary
Section titled “Research Summary”| Research Area | Key Finding | Status |
|---|---|---|
| iroh Ecosystem Deep Dive | Not reinventing the wheel — custom protocol solves a different problem (ZK relay-buffered sync). Missing opportunity with iroh-blobs for large content. Dependency sovereignty confirmed safe (MIT/Apache 2.0, fully self-hostable). | Architecture validated |
| Technology Validation | iroh QUIC transport, Noise Protocol (snow/clatter), XChaCha20-Poly1305, Argon2id — each choice validated against alternatives. | Choices confirmed |
| PQ Crypto: SHAKE/ML-KEM | ML-KEM handles SHAKE internally — no benefit to “SHAKE everywhere.” BLAKE3 for app layer (5-10x faster), SHA-512/BLAKE2s for Noise (clatter-compatible). | Design confirmed |
| OPRF Passphrase Hardening | OPRF can eliminate offline dictionary attacks by requiring relay cooperation per guess. Used by WhatsApp and Signal. Trade-off: requires relay online for pairing. | Optional enterprise enhancement |
| Blind Replica Architecture | ”The relay with one config change: no TTL.” Existing relay storage engine configured for permanence instead of transit. Two modes, one binary. | Integrated into spec |
Featured Research
Section titled “Featured Research”The detailed design for 0k-sync’s post-quantum readiness. Specifies ML-KEM-768 + X25519 in a hybrid scheme so that security holds if either classical or post-quantum cryptography is broken. Covers layer-by-layer analysis, algorithm selections, compliance mapping (FIPS 140-3, PCI-DSS 4.0, CNSA 2.0), integration strategy using the clatter crate, migration path, and implementation checklist. This is the cryptographic foundation that gives 0k-sync protection against both current adversaries and future quantum computers.
An exploratory architecture study examining how relay-sync — designed to sync encrypted journals across phones and laptops — maps architecturally to coordinating autonomous drone swarms. The central insight: relay-sync is a context distribution network for onboard AI, not a control bus. This ~1,000-line strategic portfolio document covers swarm role definitions, compartmentalized sync groups, communication modes, relay drone architecture, the competitive landscape, export control considerations, and an honest critical analysis of limitations. It serves as both a design validation tool (stress-testing the protocol against a harder use case) and a conversation piece for enterprise and defense engagement.