Anatomy of a receipt

Type CAIN42/QUORUM-QAAS/RECEIPT/v1. Values below are from the published sample.

Field	Sample value	Meaning
`type`	CAIN42/QUORUM-QAAS/RECEIPT/v1	Receipt format
`digest`	004e92d9…d6bf	The SHA-256 you notarized. Here: KEYSTONE ledger record 0's hash
`operation`	qaas_notarize, resource qaas, data {digest, v:1}	The only operation the internet can order
`request_id`	keystone-0-004e92d9c27ae51a	Your idempotency key
`client_id`	qaas-d4f988d149200f44fa6f55eb	Pseudonym of the tenant, never the tenant id or key
`cluster_id`, `sequence`	cain-mr-02, 360157	Which cluster, which position in its log
`membership`	4 members, n=4, f=1, quorum 3, epoch 1	Member ids and Ed25519 keys
`configuration_hash`	9ad62c27…7fd2	SHA-256 of the membership: what you pin
`prepare_qc`	3 PREPARE votes + the leader's PRE-PREPARE	The validators agreed on the order
`commit_qc`	3 COMMIT votes, view 180	The validators committed it
`…_qc.bundle.individual_signatures`	one entry per signer	Each vote: type, sender, view, sequence, request digest, nonce, timestamp, signature
`…_qc.certificate_hash`, `decision_hash`	b188276a…, 807d28e2…	Hashes over the certificate's content; the decision hash chains to the previous decision
`issued_at`	2026-10-15T19:16:47Z	The gateway's statement of time, not a consensus fact
`served_by`	cain-mr2-node-1	Which validator the gateway fetched certificates from

FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.