Skip to content
You are reading the Ratify Protocol v2 beta documentation. Protocol v1 remains available at the site root.

Receipts and logs

Every terminal result (allow, deny, or indeterminate) has a signed verification receipt (object code 0x0008) signed by the verifier key. It records:

  • the log ID, sequence, and previous_receipt_hash;
  • the verifier ID, the bundle hash, and the issuer IDs in the chain;
  • the decision, reason, identity status, and the trust, status, challenge, and context assessments;
  • the required and granted scope;
  • the digests of the exact signed status evidence used;
  • the evaluator profiles bound to the claim, when any were registered.

Pre-claim failures (bad signature, stale challenge, replay) create no receipt.

A receipt is evidence of the Protocol evaluation. On its own it does not prove that a decision was released or that a receiver performed an action.

Each receipt links to the previous one by StatementBodyDigest of its signed body, so re-signing the same body with new randomized signature bytes is not a fork. Two different bodies at one sequence are a fork, and the log freezes. Recovery starts a new log ID with an out-of-band link to the old one.

Rotating the verifier key drains the receipt outbox and starts a new log. If a key is lost with receipts still pending, those claims are marked receipt_abandoned and are never re-signed under another key.

The checkpoint acknowledges log entries strictly in order, from a failure domain independent of the claim store and the publisher. An acknowledgement is {entry_hash, log_id, sequence, timestamp}. A release needs the acknowledgement of the receipt and of its predecessor; a local log on the verifier’s own storage is not a substitute.

  • Transaction receipts (0x0007) carry up to 32 parties, each with its own proof bundle and signature. Verifying one reports per-party trust, delegation, status, and scope assessments. It is evidence about signed authority, never an allow.
  • Key rotation statements prove continuity from an old key to a new one within v2.
  • Witness entries form append-only logs that auditors compare to detect conflicting statements.

Details: SPEC-v2 §5.8, §7.7, §7.8, §5.7.