Roadmap & Gates¶
Vauban Pay phases are gated, not scheduled. A phase begins only when the prior phase's exit criteria are met. A stage gate that fails triggers a documented freeze-or-pivot review rather than silent continuation.
Phase timeline¶
| Phase | Window | Goal |
|---|---|---|
| MVP | Q3 → Q4 2026 | Stwo integration + Cairo settlement extension + ⊕ aggregation + ∧ humanity binding + x402 V2 alignment + Sepolia public |
| Shielded 2a | Q1 2027 | Strk20Backend + strkBTC shielded ; SdJwtVcExporter (ES256, RFC 9901) |
| Shielded 2b | Q2 2027 | VppBackend ML-KEM-768 stealth + ClaimExporter (BBS-2023, mDoc) + PQ-strict mode |
| Agentic | Q2 2027 | DelegationGrant → AgentPayment + capped-spend circuits |
| Cross-Chain | Q3 2027 | First non-Starknet adapter testnet |
| Audit & Mainnet | Q4 2027 | Tier-1 audit + Stwo-cairo audit + theorem review ; mainnet after closure |
Dates are targets re-baselined for realistic slack ; phase entry is gated on the prior phase's exit criteria, not the calendar.
Stage-gate discipline¶
Each phase carries explicit stage gates covering standards traction, prover stability, audit readiness, and the chain-agnostic milestone. A gate that fails does not end the project ; it mandates a documented review (fresh axiom check + exit-cost re-evaluation) and a freeze-or-pivot decision. This is encoded in governance, not goodwill.
Standardization engagement¶
- x402 Foundation TSC ; Vauban targets co-author status for a STARK Receipts Extension sub-standard (per ADR-ECO-024).
- IETF ;
draft-vauban-x402-stark-receiptsand companion Internet-Drafts (progressive submission). - IETF ;
draft-vauban-claim-algebra(VPSF grammar), work in progress.
Engagement preference is upstream standardization ; self-hosted fallbacks exist as disaster-recovery only.