Vela LabsInternal Knowledge Base

Current State ​

Project: VelaPay — private, programmable payment authority for any business receiving payments in crypto, built on Solana.

Current milestone: v1.9 Commerce OS — accepted on Solana devnet as v1.9.0-devnet.3.

Current product state: one-time invoices, verified hosted payments, receipts, refunds, Customer Vault, reconciliation, exports, merchant verification, commerce webhooks, and auditor access are live on devnet. Mainnet Commerce OS is not deployed.

Workspace: 15 product/support repos in vela-labs plus internal-wiki and .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). See Workspace Map → for the full inventory.

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 Operating the System ​

These pages are the operational source of truth for release work, incidents, environment constants, repo ownership, and verification.

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 delivered milestone versions v1.0 through v1.9. These pages tell the story and distinguish historical implementation from the current accepted devnet release.

For Technical Reference ​

The detailed technical documentation for building on or operating VelaPay.

Repositories ​

Product Repos ​

Support Repos ​

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 a business receive one-time payments and operate programmable billing on Solana. Commerce OS currently executes public SPL and Token-2022 payments on devnet, while Vela Protocol provides scoped, revocable Token-2022 payment authority for subscriptions, streams, usage metering, and agent budgets. Arcium-backed privacy is a separate protocol capability and roadmap; it must not be implied for v1.9 Commerce transfers. The product spans the merchant dashboard, subscriber portal, hosted checkout, embedded widgets, developer documentation, and 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 private, programmable payment authority — any payment model, any business receiving in crypto. 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 private, programmable payment authority 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.io (powered by Astro + Starlight in vela-docs/).