Latency threshold
Working now: compare supplied service latency against an explicit maximum measured in whole milliseconds.
02 / Use cases
PactVerity starts with digital services whose success conditions can be written before payment and rechecked deterministically from supplied evidence after delivery.
01 / Live capabilities
Each receipt exposes its agreement, supplied evidence, individual check results, overall outcome and verification digest.
Working now: compare supplied service latency against an explicit maximum measured in whole milliseconds.
Working now: convert supplied uptime percentages into integer basis points and compare them with the agreed minimum.
Working now: test supplied data age against the maximum number of seconds allowed by the agreement.
Working now: hash expected and observed output text locally, then compare only their SHA-256 commitments.
Working now: export a versioned JSON receipt and re-run its checks and domain-separated digest after import.
Working now when a compatible wallet supports message signing: attach and verify an off-chain Solana Ed25519 signature proving control of that key.
Working beta: submit the same user-supplied evidence to public JSON endpoints that create or verify a receipt without moving funds.
02 / Example
This logic is implemented in Proof Engine v1 and the public Receipt API beta. Both evaluate user-supplied evidence; neither independently collects measurements nor moves funds.
| Agreement records | Maximum latency, minimum uptime, maximum data age and an optional expected-output digest. |
|---|---|
| Evidence supplies | Measured latency, measured uptime, data age, evidence timestamp and optional observed output. |
| Engine calculates | One deterministic status per rule plus an overall PASS or FAIL outcome. |
| Receipt commits | Normalized inputs and results under a domain-separated SHA-256 payload digest. |
| Verifier confirms | Receipt structure, recomputed checks, digest integrity and any optional Solana-wallet signature. |
03 / Synthetic stress test
The live deterministic simulator can reproduce a default $25,000,000 synthetic nominal scenario: 250,000 model agreements at $100 with 1,000,000 checks. Service and escrow volume is $0; the result is not TVL, revenue, customer volume, adoption or assets secured.
Change the agreement count, nominal amount or seed, then reproduce the scenario. The simulator performs computation only and never creates a financial transaction.
Open technology status and simulator04 / Not suitable first
PactVerity should not imply certainty where evidence remains subjective, incomplete or high stakes.
Latency, availability, timestamps, signatures, hashes, schemas and deterministic output with bounded exposure.
Creative quality, medical or legal conclusions, physical delivery and open-ended claims of factual truth.
Try it now