04 / Roadmap

Milestones before markets.

PactVerity's roadmap is organised around technical evidence, security and product use—not token-price targets, countdowns or promised exchange listings.

Evidence stackOperational MVPSolana settlementNot deployed

01 / Sequence

Build. Test. Prove. Then expand.

Dates are targets, not guarantees. A later phase cannot begin simply because a calendar date arrives; its launch gates must be satisfied.

Phase 012026

Off-chain MVP and specifications

Current

Completed: launch deterministic Proof Engine v1 with export and independent re-verification
Completed: launch the bounded, stateless Receipt API beta, health self-tests and deterministic scenario simulator
Completed: publish selected Solana sale and escrow Rust source, threat model, reserved identities and SBF artifact hashes
Completed: load both SBF programs on an isolated local validator; execute the sale's atomic purchase and rollback paths; and exercise the escrow bootstrap as an unsigned account-meta simulation with RPC signature verification disabled
Completed: create and independently verify the fixed 50,000,000 PVTY mainnet mint, treasury account and authority removal
Pending: deploy the frozen Solana programs to devnet and execute full multi-wallet lifecycle tests
Pending: commission an independent audit and resolve material findings
Keep public purchase disabled until technical, security, operator and sale gates pass

Phase 022027

Devnet and controlled testing

Planned

Deploy Solana programs to devnet after internal adversarial tests
Conduct independent program audits and resolve material findings
Test multiple-verifier, challenge and dispute workflows
Run controlled pilots only with identified participants and explicit limits
Publish verifiable pilot methodology and results without inflating synthetic metrics
Implement disclosed PVTY vesting and treasury controls
Consider a restricted mainnet beta and SOL primary sale only if every gate passes

Phase 032028

Expansion and decentralisation

Planned

Expand independent verifier participation
Add service categories and evidence adapters
Prototype x402 and agent integrations
Introduce public governance in stages
Increase limits only after measured reliability
Develop ecosystem grants and tooling
Consider secondary-market liquidity only after measured utility and legal readiness

02 / Current evidence

A working stack with a stated boundary.

The default scenario executes 1,000,000 checks across 250,000 synthetic agreements at $100 each: $25,000,000 simulated nominal protected volume and $0 service and escrow volume.

Operational✓

Evidence computation

Receipt creation, strict verification, optional signature checking, API health self-tests and deterministic synthetic scenarios are public and inspectable.

Not evidence of×

Market or transaction activity

The synthetic total is not TVL, revenue, customer funds, adoption, historical transaction volume or assets secured by PactVerity.

03 / Mainnet gate

No mainnet by announcement alone.

Before meaningful value is accepted, the following work must be complete and publicly evidenced.

Core program tests cover normal, adversarial and failure cases.
Independent audit reports are published and material findings resolved.
Sensitive authorities are disclosed and protected by appropriate multisignature controls.
Transaction and collateral limits are defined for the initial release.
Verifier monitoring, challenge windows and incident response are operational.
User-facing fees, refund rules and remaining risks are clearly documented.

Roadmap rule

No public sale date is promised.

Evidence first