Roadmap 7 phases shipped

Where .GDBx is headed

Every phase below is tracked in the open — specs and plans live in conductor/tracks/. Shipped means live on gdbx.pages.dev, not just merged.

Shipped

Phase 0 · Scaffold

Conductor setup, Cloudflare Pages + Worker, CI-ready repo

Phase 1 · Address Codec

.GDBx format — Version+Network+SHA256(pubkey)+BLAKE3 checksum → 58 base32 chars; JS codec + Python parity vectors

Phase 2 · DID Registry + PoW Gate

GDBxStorageDO (Durable Object SQLite), did:gdbx:<addr> documents, adaptive SHA-256 PoW anti-spam

Phase 3 · CRDT Sync Engine

LWW merge with deterministic tie-break, flat-primitive schema, presence heartbeat, Pages API v1

Phase 4 · Hardening + Real-time

Replay protection (60s window + nonce), GDPR purge, rate limits, strict validation, WebSocket hub inside the DO, encrypted export, leaderboard

Phase 5 · Self-Sovereign Mesh

Gun-free crypto core (GDBx envelope, pure WebCrypto ECDSA P-256, SEA v1 compat) · zero-trust FirewallGuard (PoW→replay→sig→RBAC→ACL) on every mutation · GDBxMirrorDO replication pool with rejoin healing · hybrid transports WS → Nostr kind-23124 → WebRTC signaling · supply-chain hardening (@noble/hashes only, npm audit 0)

Phase 6 · Org Fabric & Developer Platform

Python SDK (gdbx-py) with JS↔PY cross-verified GDBx vectors · AiA + OS bridges · Live P2P Playground (rooms, E2E AES-GCM private rooms, imgbb proxy + sovereign chunked files) · CLI (identity / sync / vector / backup / ftp gateway) · Sovereign FTP Gateway (ftp-srv loopback, FileZilla-compatible, 256KB AES-GCM BLAKE3 chunks) · Gun-compat engine absorbed (serverless relay semantics natively)

In progress & next

Pulled from the live tracks registry — statuses move as work lands.

Gun-Compat Wire Engine

Full legacy wire-protocol surface so existing Gun clients peer with a .GDBx address unmodified.

track spec

Vector Search (sqlite-vec)

Native cosine search inside the Durable Object for AI-agent memory at scale — replaces client-side brute force.

Public Audit & Formal Spec

Independent security review, load testing, and a versioned protocol specification document.

Tor v3 / I2P / IPFS Transports

Dark-net and content-addressed routing behind the same .GDBx address — adapter interfaces already reserved.

Multi-Region Backup Relay

Cross-cloud snapshot mirroring (R2/S3/Fly.io) beyond the built-in MirrorDO pool.

DIDComm v2 · UCAN · Verifiable Credentials

SSI interoperability, offline capability delegation, and verifiable badges on did:gdbx identities.