02 / Use cases

Protect what software can measure.

PactVerity starts with digital services whose success conditions can be written before payment and rechecked deterministically from supplied evidence after delivery.

Evidence stackOperational MVPSolana settlementNot deployed
Working technology:Proof Engine v1 and the public stateless Receipt API beta perform deterministic checks for maximum latency, minimum uptime, maximum data freshness and an optional SHA-256 output hash. The scenario simulator is also live at Technology. These operational off-chain tools move no funds and are not evidence of customers, integrations, revenue or adoption.

01 / Live capabilities

Objective signals first.

Each receipt exposes its agreement, supplied evidence, individual check results, overall outcome and verification digest.

01

Latency threshold

Working now: compare supplied service latency against an explicit maximum measured in whole milliseconds.

02

Uptime threshold

Working now: convert supplied uptime percentages into integer basis points and compare them with the agreed minimum.

03

Freshness threshold

Working now: test supplied data age against the maximum number of seconds allowed by the agreement.

04

Output integrity

Working now: hash expected and observed output text locally, then compare only their SHA-256 commitments.

05

Portable receipts

Working now: export a versioned JSON receipt and re-run its checks and domain-separated digest after import.

06

Wallet key control

Working now when a compatible wallet supports message signing: attach and verify an off-chain Solana Ed25519 signature proving control of that key.

07

Stateless API

Working beta: submit the same user-supplied evidence to public JSON endpoints that create or verify a receipt without moving funds.

02 / Example

A measurable API receipt, in plain English.

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.

Working PactVerity API evidence receipt inputs and outputs
Agreement recordsMaximum latency, minimum uptime, maximum data age and an optional expected-output digest.
Evidence suppliesMeasured latency, measured uptime, data age, evidence timestamp and optional observed output.
Engine calculatesOne deterministic status per rule plus an overall PASS or FAIL outcome.
Receipt commitsNormalized inputs and results under a domain-separated SHA-256 payload digest.
Verifier confirmsReceipt structure, recomputed checks, digest integrity and any optional Solana-wallet signature.

03 / Synthetic stress test

Model scale without inventing activity.

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.

Inspect the model and its digest.

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 simulator

04 / Not suitable first

Some outcomes cannot be reduced to a clean proof.

PactVerity should not imply certainty where evidence remains subjective, incomplete or high stakes.

Good fit

Pre-agreed machine tests

Latency, availability, timestamps, signatures, hashes, schemas and deterministic output with bounded exposure.

Not an initial fit×

Subjective or safety-critical judgement

Creative quality, medical or legal conclusions, physical delivery and open-ended claims of factual truth.

Try it now

Run the working engine yourself.

Open Proof Engine