PARADATUMOne contract, one receipt chain. On your hardware or ours.
An enterprise deals with Paradatum and pays in dollars. Paradatum pins the contract and runs the job wherever you choose: on your own GPUs as an enterprise install, in a partner datacenter, or on the private distributed compute network. Optionally the proven result is filed, and a claim that needs judging goes to independent adjudicators. Each leg returns a receipt chained to the last.
What comes back is the same everywhere: an answer, a receipt per leg, a proof, and a re-verify link. You never touch a token.
Where Paradatum sits
Paradatum is the front door and the engine, and the engine runs the same on a GPU you own as on one you rent. The three open networks are the distributed option behind it: Blindproof runs the job, DeFacts remembers the result as a claim, Knowledgecoin adjudicates the claim into knowledge. Use the layers you need; an enterprise install can stop at the first receipt.
Customer
Pays in dollars, by card, invoice or USD stablecoin. Gets an answer, a receipt per leg, a proof, and a re-verify link. The customer never holds a token.
Paradatum gateway
Pins the contract: model, version, precision, execution path. Routes the job to your hardware, a partner’s, or the network. Issues the receipts. Escrows the payment against one job identifier.
One escrow, released per receipt
R1 verifies → the compute leg is paid. R2 (chained to R1) → the filing leg is paid, if you file. R3 (chained to R2) → the adjudication panel is paid, if you adjudicate. If a proof fails, nothing files and the customer is refunded in the unit charged.
Published rules
How fees flow is published and checkable from the receipts. Paradatum holds equity in the three networks and runs none of their markets.
A claim is posted
Over a filed DeFacts claim: “this is true” or “this is false.” Nobody argues about what ran or what the source was; those are proven below. Adjudicators argue only whether the claim holds.
Adjudicators with something to lose
Every adjudicator puts something at risk on its verdict. By default an agent running on Blindproof: pinned model, proof attached, so the vote is itself a proven run. People may adjudicate too. The majority earns the fee; the minority forfeits.
Knowledge, with a record
Receipt R3: claim identifier, panel, each vote with its reasoning receipt, and a confidence weighted by what each adjudicator risked. Chained to R2, to R1, to the contract.
A claim is filed
The fact in the DeFacts schema, its proof, the source hash, the model checkpoint. Stored on durable public storage with a public hash anchor. Receipt R2 chains to R1. Provenance is proven; truth is not claimed yet.
The producer of record
The customer, unless assigned, is recorded as the producer of the claim and earns a royalty each time the claim is re-verified or adjudicated.
Asked again: no rerun
Same question again? The stored claim is served and its proof re-checked in milliseconds. No model runs, so the second answer costs a small fraction of the first.
The job runs in the dark
On your own GPU (graphics processing unit), a Paradatum GPU, or an independent network GPU, under the pinned contract. Masked: whoever operates the hardware never sees plaintext. Same bytes on any GPU. Receipt R1 with proof.
Validators check the proof
R1 is scored against the contract: by your own verifier on an enterprise install, by independent validators on the network. Wrong bytes, no score, no payment. Network operators post collateral and lose it if they drop a job.
Adjudicators run here too
An agent’s verdict is itself a Blindproof job: pinned model, verdict and proof out. The same guarantees apply to the judge as to the work being judged.
What you get back
- R1Compute receipt. The agreed model and contract, the committed inputs, the hash of the output bits, and the proof that the run matched. Issued on every deployment, on-premises or network. Releases the compute leg of the escrow.
- R2Filing receipt (optional). Where the claim and its proof are stored, the public hash anchor, the producer of record. Chained to R1. Releases the filing leg.
- R3Adjudication receipt (optional). The panel, each vote with its reasoning receipt, the weighted confidence. Chained to R2. Releases the adjudication leg.
- ↻Re-verify link. Anyone you hand it to can re-check the whole chain in milliseconds, without re-running the model and without trusting Paradatum.
Why adjudication is tractable here
- The input is never in dispute. Source hashed, extraction deterministic, proof checked. Adjudicators argue only whether the claim holds: the smallest adjudication surface any oracle has had.
- Agent adjudicators are auditable. “Why does the system believe this” has an answer with hashes in it: which model, which evidence, which reasoning, with a proof.
- Confidence is weighted agreement among parties with something to lose, not a model’s self-reported probability.
Paradatum gates and, on your hardware, runs. Blindproof runs it distributed. DeFacts remembers. Knowledgecoin decides what it means. A claim with a proof is still only a claim; knowledge is a claim that has been tested by parties with something to lose, with the test on the record.
The networks: BlindproofDeFactsKnowledgecoin