Verification Receipt Schema

Every crest-verified entry produces a machine-readable receipt. Receipts are version-controlled in the substrate-attestation repository.

Schema: crest-verification-receipt-v1

Field	Type	Description
schema	string	Always crest-verification-receipt-v1
report_id	string	Unique ID (CVR-YYYY-NNN)
subject	string	What was verified
verifier	string	DID of the verifier (did:web:verify.crestsystems.ai)
tool	string	Validator tool and version
source_url	string	URL of the tested artifact
source_hash	string	SHA-256 of the source at verification time
result.total	number	Total vectors tested
result.pass	number	Vectors that passed
result.fail	number	Vectors that failed
result.status	string	Overall: PASS, FAIL, or PARTIAL
vectors[]	array	Per-vector results with IDs and hashes
content_hash	string	SHA-256 of the receipt itself (self-referential integrity)

Example

{
  "schema": "crest-verification-receipt-v1",
  "report_id": "CVR-2026-013",
  "subject": "CTEF canonicalizer byte-match",
  "verifier": "did:web:verify.crestsystems.ai",
  "tool": "rfc8785 Python (v0.1.4)",
  "source_url": "https://example.com/vectors.json",
  "source_hash": "sha256:b655d1b3...",
  "result": {
    "total": 4,
    "pass": 4,
    "fail": 0,
    "status": "PASS"
  },
  "vectors": [
    {
      "id": "envelope_vector",
      "status": "pass",
      "our_hash": "9e7b5031...",
      "byte_match": true,
      "hash_match": true
    }
  ],
  "content_hash": "sha256:099f0db7..."
}

Properties

Receipts are append-only. Published receipts are never modified or deleted.
The content_hash field is a SHA-256 of the receipt body excluding the content_hash field itself.
Receipts are stored in a public Git repository. Every change is version-controlled and auditable.
A receipt is evidence of verification at a point in time. It does not guarantee current conformance.

Published receipts Verification standard