Framework overview
Register · transparencyDraft for comment · OCC-E-019 · 2 Oct 2026

Register transparency log

Every listing, record version, status change and public incident on the OCC register is written once to an append-only log. The log is a Merkle tree hashed the way Certificate Transparency does it (RFC 9162), and each new tree head is signed with both register keys. Anyone can check that an entry is in the log, and that later versions of the log still contain everything earlier versions did.

Runs in your browser

Check that an entry is included

The checker fetches an inclusion proof, recomputes the leaf hash from the statement and walks the proof to the signed root using your browser’s own SHA-256.

The log has no entries yet. The checker works as soon as the first public record is listed.

Newest first

Recent entries

No entries yet. Entries appear when operators list public records on the register.

Open, no sign-in, CORS enabled

Endpoints

  • /occ/log/checkpoint.json

    Latest signed tree head: tree size, root hash, timestamp, Ed25519 and ML-DSA-65 signatures. Add ?size=N for an earlier one.

  • /occ/log/entries.json

    Entries in order (?start=0&limit=100), or every entry for one record (?ref=OCC-…).

  • /occ/log/proof.json?index=N

    Inclusion proof for entry N against the latest signed tree head (add &size=M for an earlier head).

  • /occ/log/proof.json?first=M&second=N

    Consistency proof: the tree of size M is an unchanged prefix of the tree of size N.

Format

How it works

  • Statements. Each entry is a small JSON statement (occ.log.statement/v1) in canonical form: sorted keys, no whitespace. A record statement carries the SHA-256 of the canonical record JSON, so a copy of record.json can be matched to the moment it was published.
  • Hashing. Leaf = SHA-256(0x00 ‖ statement). Node = SHA-256(0x01 ‖ left ‖ right). Proofs follow RFC 9162 sections 2.1.3 and 2.1.4.
  • Signed heads. Whenever the tree grows, the register signs occ.log.checkpoint/v1 (log id, tree size, root hash, timestamp) with Ed25519 and ML-DSA-65.
  • Permanent. Entries are never edited or removed, including for records that are later withdrawn. A withdrawal, suspension or unlisting is itself a new entry.
  • Monitoring. Keep the tree heads you have seen. Ask for a consistency proof between an old head and a new one: if it fails, the log was rewritten.

The design borrows from Certificate Transparency and the IETF SCITT architecture. It is not a SCITT transparency service (RFC 9943); mapping log statements to SCITT signed statements is a possible next step, open for comment.

What the log does not say
Inclusion in the log proves that the register published a statement at a point in time and has not since altered or hidden it. It does not prove that the statement is true, or that an agent is safe, approved or compliant. OCC does not certify agents. Browse the register