01
Evidence before claims
Deployment, audits, users, partners and performance should only be stated when they can be independently checked.
09 / About
Make machine commerce answerable.
PactVerity is a live public project building open evidence and settlement infrastructure for measurable digital services. Proof Engine v1, a public Receipt API beta, an activity ledger and a deterministic simulator are operational today.
Project statusLive public MVPPVTY tokenLive on Solana
01 / Mission
Open rules for unfamiliar counterparties.
The working engine, API and simulator make evidence rules, receipt calculations and synthetic scenario results inspectable today. On-chain enforcement remains a future layer requiring implementation, testing and independent review.
Working thesis
Autonomous payments need a neutral way to turn measurable promises into reproducible evidence before they can have enforceable consequences.
02 / Principles
The product must earn trust.
02
Markets without false promises
PVTY market access is independent from the planned settlement protocol. The project publishes the exact mint, live route status and risks without promising price, liquidity, adoption or returns.
03✓
Limits before scale
Start with objective services, controlled exposure and challengeable evidence, then expand only after measured reliability.
03 / Founder
Jonathan Koh — founder of PactVerity.
Jonathan Koh is 33 at the time of publication, is based in Singapore and has supplied a degree background in Mathematics and Science.
Founder biography
Building evidence before asking markets for trust.
Jonathan Koh founded PactVerity around a direct problem: autonomous software can initiate work and payment, but the evidence needed to prove whether a digital service met an agreement is often fragmented across private logs, dashboards and counterparties. PactVerity began as an attempt to make that evidence portable, reproducible and open to independent review.
His background in Mathematics and Science informs the project's emphasis on explicit definitions, measurable thresholds and deterministic calculations. Instead of asking a reviewer to accept an opaque score, the working Proof Engine records the supplied evidence, applies a versioned rule set and produces a receipt whose result and integrity digest can be recomputed.
Jonathan's approach has been to build the evidence layer first. PactVerity therefore operates a public Proof Engine, Receipt API beta, known-answer health check, benchmark and evidence surfaces before claiming that custody, settlement, collateral utility or adoption exists. The longer-term thesis is that reviewed settlement programs could consume these receipts when objective service conditions have real contractual consequences.
As founder, Jonathan is responsible for PactVerity's product direction, public roadmap and evidence-first standard. His stated objective is to develop an accountable verification layer for AI agents, APIs and measurable digital services while publishing the project's limitations, token concentration, market status and unresolved milestones alongside its working technology.
04 / Public proof
What participants can verify now—and what remains open.
A live project should distinguish completed public evidence from outstanding organisational, security and settlement milestones.
- Official domain, canonical PVTY mint, fixed supply and removed token authorities.
- Operational Proof Engine, Receipt API beta, public activity and reproducible simulator.
- Independent audit reports, vulnerability reporting and incident response as they are completed.
- Clear fees, refund limits, dispute rules and jurisdictional access conditions.
- Evidence for any named investor, partner, customer or usage claim.
Community access