Vela LabsInternal Knowledge Base

Current State ​

Project: VelaPay — privacy-first subscription billing protocol on Solana.

Current milestone: v1.8 Advanced Billing Features — all 3 phases (45–47) verified complete. 28 plans, 69 requirements satisfied.

Total shipped: 8 milestones fully shipped (v1.0–v1.7), v1.8 verified complete. 47 phases, 206+ plans, 529+ commits since March 29, 2026.

Workspace: 11 directories in vela-labs — 9 product repos + internal-wiki + .planning ops layer. Every repo has an independent deploy lifecycle. The workspace runs on Bun (TypeScript repos), Anchor 0.32.1 (Rust), and Cloudflare (infra backbone).

What matters most: The transfer-hook mandate system lets merchants pull exactly what was agreed — and nothing more. If that breaks, everything breaks.

Wiki Sections ​

For Investor Preparation ​

These pages prepare the narrative, numbers, and competitive positioning for investor conversations.

For Understanding the Product ​

The product is a billing primitive. These pages explain how it works end-to-end.

For Understanding the History ​

The project has shipped 8 milestones in 19 days. These pages tell the story.

For Technical Reference ​

The detailed technical documentation for building on or operating VelaPay.

Repositories ​

Milestone Timeline ​

Total: 47 phases, 236+ plans, ~18 days of active development.

Key Numbers ​

Architecture at a Glance ​

VelaPay runs on a 4-layer architecture:

Layer 4: Applications — Dashboard, Portal, Checkout, Admin, Web, Docs, Widget
Layer 3: Revenue Finance — MRR Oracle, Lending, Marketplace (future)
Layer 2: Billing Engine — Mandate Registry, Stream Engine, Usage Meter, Keeper Network
Layer 1: Protocol Core + Privacy — Vela Mandate (Transfer Hook) + Arcium MXE + Credentials
Base: Solana Token-2022, Arcium MXE Network, Helius RPC

The deepest architectural choice is the dual-program split: vela-protocol (billing state transitions) and vela-transfer-hook (transfer-time enforcement). The transfer hook must be isolated because it runs during every transfer_checked — any bug either lets merchants steal or blocks legitimate payments.

See Architecture → for the full system design.

What VelaPay Does (In One Paragraph) ​

VelaPay lets on-chain businesses charge recurring payments — monthly pulls, per-second streams, usage metering, agent budgets — with all billing logic running on encrypted data via Arcium MPC. Merchants create plans, subscribers authorize mandates, keepers execute pulls, and the transfer hook enforces that exactly what was agreed gets pulled — nothing more. No one (validators, competitors, chain analysts) ever sees business metrics. The product spans a merchant dashboard, subscriber portal, hosted checkout, embedded widgets, developer documentation, and an internal admin console.

Quick Links ​

Working Thesis ​

Vela is the primitive. VelaPay is the product.

The way Token-2022 is the primitive for tokens and Squads is the primitive for multisig, Vela becomes the primitive for recurring value transfer on Solana. The product story spans merchant tools, admin ops, subscriber portals, and checkout UX — but the system still lives or dies on the same core property: enforce the mandate at the token-transfer boundary.

The workspace is built around privacy-first recurring payments on Solana using Token-2022 transfer hooks for scoped enforcement and Arcium MPC for encrypted billing logic. Phase 0 proved the billing primitive standalone. Phase 1 layered in Arcium privacy. Phase 2 added operational surfaces. Everything from v1.3 onward has been building product completeness on top of the same unshakeable foundation.

Coverage Sources ​

This wiki is grounded in these primary sources. When in doubt, .planning/ artifacts are more current than root docs or repo READMEs.

1. .planning/PROJECT.md — canonical current-state summary and key decisions
2. .planning/STATE.md — current execution state with machine-readable frontmatter
3. .planning/ROADMAP.md — complete milestone and phase history
4. .planning/REQUIREMENTS.md — product requirements with validation state
5. .planning/MILESTONES.md — milestone completion log with accomplishments
6. Root research docs (01–10) — founding market thesis, competitive analysis, brand identity
7. Repo manifests and READMEs — what each code repository actually contains

About This Wiki ​

This internal wiki is built with VitePress and deployed to Cloudflare Workers. It serves as the navigable knowledge base for the entire VelaPay workspace — covering investor preparation, product understanding, technical architecture, development history, and operational planning.

The wiki is maintained alongside the codebase and should be updated when:

• A new milestone ships (update milestone pages and planning status)
• A significant architectural decision is made (update architecture and decision pages)
• Investor materials change (update pitch pages)
• New repos are added to the workspace (update workspace map)

For the public-facing documentation, see docs.velapay.com (powered by Astro + Starlight in vela-docs/).