RFC 9162-style · append-only · verifiable

The receipts
cannot be un-issued.

Every Crovia Seal that enters this log is a permanent, signed commitment. Download the chain as public_log.jsonl, verify offline, and prove inclusion — or prove a seal was never submitted. No account. No trust us.

What you are looking at. This log currently carries Crovia’s normative conformance vectors — a reference chain of Seals from crovia-seal/conformance, not production traffic. That is deliberate: their Ed25519 signatures are real, and your browser verifies every one of them live below (CSC-1 canonicalization + Ed25519, no server in the loop). Production issuer traffic — Causari first — is appended here as issuers onboard. Section 5 of draft-crovia-seal-01 defines the RFC 9162-style log this mirrors.
Seals in log
—
Head sequence
—
Issuers
—
Updated
—
Loading chain integrity…
Download full log (.jsonl) Verify any seal Submit your issuer's seals

Log entries

newest first · click seal id to verify
#Seal IDIssuerGeneratorModalityEmitted
Loading…

Production issuers: run Causari with re proxy --seal, then submit your append-only seals.jsonl for inclusion. A full RFC 9162-style Merkle log service is the subject of a companion profile to draft-crovia-seal (Section 5, Informative); today this page is the human-readable mirror and every entry is independently verifiable — here, or offline with the reference verifier.