01
Buyer agent
Would define or accept the job terms and fund stablecoin escrow after the Solana programs are deployed.
01 / Protocol
A checkout with a referee.
PactVerity's off-chain evidence stack is operational: Proof Engine v1, a public stateless Receipt API beta and a deterministic scenario simulator. Solana escrow, bonding, custody, disputes and settlement are not deployed.
Evidence stackOperational MVPSolana settlementNot deployed
In plain English
The working evidence layer can compute and recheck a result now. It has moved $0 and holds no customer assets. Future Solana programs would be required before receipts could affect funds, bonds, challenges or settlement.
02 / Planned participants
Clear roles. Clear responsibilities.
These roles describe the broader Solana protocol design. They are not represented as a live network of participants.
02
Service provider
Would accept measurable conditions, post the required collateral and deliver the service.
03
Verifier
Would check agreed evidence and sign an outcome. This role is separate from a Solana network validator.
04
Evidence adapter
Would turn uptime, latency, hashes or compute results into the machine-readable input accepted by the evidence layer.
05
Integrator
Can call the Receipt API beta today; a future SDK or x402 integration could connect the broader protocol.
06
Challenge panel
Would review conflicting evidence that the planned automated settlement rules cannot resolve.
03 / Target lifecycle
Define → bond → verify → settle.
Receipt creation and deterministic verification are operational off-chain. Bonding, funding, custody, challenges and settlement require Solana programs that have not been deployed.
| 01 / Define | The operational engine and API can record measurable criteria with caller-supplied evidence; they do not create an on-chain job. |
|---|---|
| 02 / Bond | A future Solana program would let the provider commit the required performance collateral. |
| 03 / Fund | A future Solana program would let the buyer place the service payment and disclosed fee into stablecoin escrow. |
| 04 / Deliver | A future job flow would accept evidence or a cryptographic evidence commitment after service delivery. |
| 05 / Verify | Proof Engine v1 and the Receipt API beta can apply the four published checks and produce a portable receipt now. |
| 06 / Settle | A future audited program would release payment, apply the recorded refund rules or open a challenge window. |
04 / Boundaries
Start with what machines can recompute.
The current engine proves receipt consistency, not the honesty or completeness of user-supplied measurements.
Suitable first✓
Objective digital services
API uptime, response latency, data freshness, file hashes, deterministic compute and signed delivery events.
Out of initial scope×
Subjective or high-stakes judgement
Creative quality, medical conclusions, legal advice, physical delivery and claims whose correctness cannot be measured reliably.
Evidence is not a guarantee or insurance.
The current stack neither holds funds nor issues refunds. If a future settlement system launches, any refund would be limited to assets available under its published escrow and collateral rules, with smart-contract, verifier and network risks remaining.
Technical detail