Security
A receipt is only worth something if the signing behind it is sound and the keys behind that are handled properly. This page says how both work — and what the system deliberately doesn't do.
Signing
Every receipt is signed with Ed25519. The record is canonical JSON (RFC 8785), hashed with SHA-256, and the signature covers the whole record: the request hash, the response hash, the model and provider, the time, and your organization. Change any byte of the record and the signature stops verifying. The signing key lives server-side only and is never shown in the portal or the API.
What We Store — and What We Don't
- Prompts and answers are stored as salted SHA-256 hashes only, never as text. The proxy sees the text while a call is running and does not keep it.
- Receipts are append-only: once signed, a receipt row is never edited or deleted.
- Receipts older than your retention period (365 days by default) stop being listed in the API and the portal. The rows stay in the table and their hashes stay in the batch leaf files, so the Bitcoin proof survives — only the listing goes away.
- The verify page sets no cookies and runs no analytics.
Your Provider Keys
Your OpenAI, Anthropic, Google or xAI key is tested against the provider before it is saved, so a mistyped key never sits silently in the account. At rest it is encrypted with AES-256-GCM under a master key held in the deployment environment, and it is decrypted only for the length of a single call. The portal shows only the last four characters. You can also send a provider key per call in the X-Provider-Key header instead of storing one at all.
Your Chain Receipt API Keys
API keys (crk_live_... / crk_test_...) are stored as HMAC-SHA256 hashes, never in plain text, and the full key is shown exactly once, when it is created. Use a test key while you're integrating; test keys can't spend your live quota. Revoke a key in the portal and it stops working immediately.
Anchoring
Receipt hashes are batched into a Merkle tree every 10 minutes and the batch root is submitted to three public timestamp calendars, which commit it to Bitcoin. A receipt's proof is the Merkle path from its hash to the batch root, plus the calendar attestations and the Bitcoin block header — all of it downloadable as a .ots file from the verify page, checkable offline with the OpenTimestamps client. Instant Proof adds a Hedera anchor of the same batch root within a minute; it never replaces the Bitcoin anchor.
What Receipts Don't Prove
A receipt proves the proxy saw exactly this request and exactly this response, at this time, for this account — and that the record hasn't changed since. It does not prove the answer is true, that the provider ran the model it named, or that the person who made the call was allowed to. Those are separate claims, and we don't dress them up as something the receipt covers. What a receipt proves — and doesn't →
Reporting a Security Issue
If you find a vulnerability, write to us through the contact form with the details and a way to reproduce it. Don't test it against other customers' receipts, and don't publish it before we've had a chance to fix it. We'll confirm receipt and tell you what we're doing about it.