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 building an open evidence and settlement layer for measurable digital services. Proof Engine v1, a public stateless Receipt API beta and a deterministic scenario simulator are operational today; the Solana value layer is not deployed.
Evidence stackOperational MVPSolana settlementNot deployed
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
Utility before a market
Specifying or creating a fixed-supply token does not justify a public market. Any sale or liquidity decision would follow working protocol demand, security testing and legal readiness.
03✓
Limits before scale
Start with objective services, controlled exposure and challengeable evidence, then expand only after measured reliability.
03 / Public proof
What must appear before participation opens.
A production release needs attributable people and entities, verifiable technical evidence and working support channels.
- Responsible legal entity, project operators and official communication channels.
- Public program IDs, token authorities, treasury controls and release history.
- Independent audit reports, vulnerability reporting and incident response.
- Clear fees, refund limits, dispute rules and jurisdictional access conditions.
- Evidence for any named investor, partner, customer or usage claim.
Inspect the evidence