Roadmap
Parallel tracks with strict gates: safety, execution, privacy, and community.
Tracks
| Track | Scope | Exit criteria |
|---|---|---|
| Core Protocol | Routing, receipts, limits, program hardening | Audits passed, invariants green, SLOs met |
| Privacy | Profiles, jitter, batching, mixouts | Leakage benchmarks and threat reviews published |
| Integration | Makers, AMMs, relayers, wallets | Coverage KPIs and reliability SLOs |
| Observability | Metrics, tracing, alerting | Playbooks rehearsed; dashboards shipped |
| Governance | RFC process, council, DAO tooling | Quorum met on 3+ proposals; incident MTTR targets |
Phase plan
MVP
RFQ+AMM routing, session privacy, micro‑batches, receipts. Target: private beta.
Phase 2
Commit‑reveal windows, protected relayers, enhanced batching, analytics v1.
Phase 3
Cross‑venue routing, DAO readiness, grants, analytics v2.
Release trains
- Weekly canary to testnet with automated regression suite.
- Monthly stable to mainnet with audit or differential fuzz coverage.
- Hotfix path with scoped adapter toggles and post‑mortems.
Milestones & gates
| Milestone | Gate | Evidence |
|---|---|---|
| Private Beta | All core invariants green | CI artifacts, load tests, receipts sampling |
| Public Beta | Audit pass + incident playbooks | Reports published, drills documented |
| DAO Transition | 3+ successful proposals, quorum | On‑chain records, participation metrics |
KPIs
≥99.9%
Router success SLO
≤150ms
Median RFQ latency
≤2 h
Hotfix MTTR
Risks & mitigations
- Volatility: widen TTL and slippage bounds in extreme regimes; circuit breakers.
- Integration outages: dynamic routing weights; adapter health scoring.
- Privacy regressions: periodic leakage reviews; red‑team exercises.