Audit trail
Recent inference receipts
Every served job produces a receipt: a deterministic SHA-256 hash over the canonical JSON of the job's immutable economic core. The hash is recomputable from the same inputs, so the accounting is verifiable rather than asserted.
Total jobs
0
Completed
0
Receipts
0
Counts are process-local and reset on a cold start; pre-launch they read honestly as zero rather than a fabricated history.
Latest receipts
0 on this instanceNo receipts on this instance yet
The network is pre-launch and this receipt log is process-local. Receipts appear here once the network serves jobs — each one a deterministic SHA-256 record of what was computed, by which worker, at what token count. Read the live feed directly:
curl -s https://basis.watch/api/inference/receipts
How a receipt is verified
A receipt hash is a SHA-256 digest over the canonical JSON of the receipt's immutable economic core — model, token counts, multipliers, charged and reward amounts. Mutable envelope fields (status, signature, settlement pointers) are excluded, so the hash stays stable across the receipt's lifecycle.
Fetch and confirm a single receipt by its hash:
curl -s https://basis.watch/api/inference/receipts/:receiptHash
Recompute the digest from the same canonical inputs and compare — if the hashes match, the accounting was not altered after the fact.
Receipts are billing and reward evidence, not claim-verification records. For how jobs are metered, see /inference; for how receipts settle on Base, see /settlement.