Standard tier only
Provn has no confidential or TEE-attested tier. The upstream model host processes your prompt in plaintext on every model, including extra models an operator connects.
Check it, then trust it
Provn sells compute you can check. Live figures on this site come from the running gateway through public endpoints such as GET /v1/status and GET /v1/explorer/stats, and on a new deployment some of them read zero or null. The list below covers what Provn does not prove, does not run and has not launched, so you can weigh each claim against its limit.
Live system posture
GET /v1/status · reading…
Gateway
…
Uptime 24h
…
Store latency
…
Upstream
…
Uptime comes from probes the gateway stores on each status read, at most one a minute. It reads “not enough samples” until there are enough to compute, and it is never filled in. Store driver: …. Upstream: ….
Receipt signing key
Every billable response is signed by this address with secp256k1 (EIP-191 personal_sign). Pin it and verify receipts offline.
reading…
source: …
Switches on this deployment
- Anchoring to chain 4663
- …
- Needs a funded signer. Off means batches seal without an on-chain root.
- ETH top-ups
- …
- Needs a treasury address.
- Keyless Terminal
- …
What we do not claim
The free upstream has no SLA from Provn
provn and provn-nano run on a free public upstream that Provn does not operate. Provn gives no uptime or latency guarantee for it, and GET /v1/status shows whether the gateway can reach it.
A receipt does not prove the answer is right
A valid receipt shows that the gateway metered the call, routed it to the named engine and signed the stated cost. It says nothing about the quality of the output, and Provn can't attest what ran on the upstream host.
Anchoring is off without a funded signer
Public anchoring needs a funded key in PROVN_ANCHOR_KEY. Without one, Provn still seals each batch, labels it unanchored and reports that through the proof endpoint. An unanchored batch has no timestamp on chain.
No operator network, no marketplace
No third-party machine serves Provn traffic. Calls go through the Provn gateway and the upstream its operator configured. Provn plans an operator network and has set no date for it.
Passports hold facts and no score
A passport lists receipts, runs, activity dates and anchored receipts from the account's own history. It carries no trust score or quality rating and says nothing about profits or off-platform actions.
A fresh deployment signs with a temporary key
Until an operator pins PROVN_SIGNER_KEY, the gateway signs with an ephemeral development key. Receipts from that key won't match the signer the deployment settles on, so pin an address after the operator fixes it.
The token is not live
The $PROVN contract is not deployed. Any address presented as $PROVN before Provn posts one on /faq and on X belongs to someone else.