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

Status from signed evidence

A v2 allow requires current signed status for every certificate in the chain. Unsigned, boolean, or self-asserted status can never produce “not revoked”.

Each issuer publishes status under a status key that is separate from its issuer key, its root, and every other key the deployment knows. The separation is permanent: a key ever used for status is never admitted in another role, and the reverse. Status keys are bound per issuer in numbered epochs through caller-authenticated configuration.

  • A RevocationList is a full snapshot: issuer, sequence, updated_at, next_update, and the revoked certificate IDs.
  • A RevocationPush adds newly revoked IDs at the next sequence.
  • Revocation is monotonic. A later list never clears a revocation; correcting one needs a new certificate ID.

Every SDK ships a minimal publisher for one issuer. It refuses to start unless the role configuration proves the status key is separate, then:

  • signs a genesis list at sequence 1 with no revocations;
  • re-signs heartbeats with a strictly later updated_at, without consuming a sequence;
  • on revocation, advances exactly one sequence and emits a push plus the full list;
  • persists its next state before publishing, so it can never sign two bodies at one sequence.

A publisher that stops heartbeating makes status stale at next_update, by design.

The verifier applies status objects to SecurityJournalV2, a rollback-protected journal whose head is independently anchored. For each certificate the result is:

Observed state Result
Revoked in any validly signed object seen, reconciled or not revoked
No accepted snapshot, a missing freshness bound, a future-dated object, or an unresolved gap or fork indeterminate, unavailable
Accepted snapshot is past next_update or the configured maximum age indeterminate, stale
A fresh accepted snapshot covers every observation, and the certificate is absent not_revoked

A missing push, a gap, or two different objects at one sequence (a fork) can never produce “not revoked”. A provider failure is unavailable, which gives an indeterminate decision.

Each SDK reference page renders a signed-status example.

Details: SPEC-v2 §5.4, §6.5, §6.6, §9.6.