Certificate verified — production
Certificate integrity · ISSUED · cert.v2 · GENESIS
The certificate exists, its Ed25519 signature is valid, and it has not been revoked. To check that a specific file matches the artifact recorded in this certificate, use the Verify Your File section below.
Certificate Details
Certificate ID
0f3f24da-1dd4-4b4a-b204-4c97a5932f18
Issuer
Certified Data LLC
Issued
August 29, 2026 at 06:40 PM UTC
Signature Algorithm
Ed25519
Signing Key ID
Dataset / Project
41e9d470-3d91-4721-9045-608705e4ac46.prediction_receipt.v1.json
Verification Evidence
Certificate record
Certificate 0f3f24da… found (cert.v2)
Canonical signature input
Payload canonicalized with RFC 8785 JCS; the signature covers these exact bytes.
Signing key
key_id ed25519-prod-2025-02 — resolves to the published Ed25519 public key.
Key status
Key is active.
Signature authenticity
Ed25519 signature valid against the published public key.
Verdict: Certificate verified — production
Raw check flags (API)
✓ signature_valid
✓ schema_valid
✓ not_revoked
Certified Artifact Hashes
ZIP artifact SHA-256 (41e9d470-3d91-4721-9045-608705e4ac46.prediction_receipt.v1.json)
b21ab7b9b56e927e1a8d6f11eb8d02a9d577b5c0a8cee39ab2c79ab2746a63ed
Verify locally without this website:
# Linux / macOS sha256sum dataset.zip # macOS alternative shasum -a 256 dataset.zip # Windows PowerShell Get-FileHash dataset.zip -Algorithm SHA256
The output must match the artifact_hash above. Full verification guide →
Verify Your File
Check artifact integrity
Upload the original artifact file to confirm its SHA-256 matches the fingerprint stored in this certificate. Files are hashed server-side; this is independent of certificate-signature verification above.
What This Certificate Proves
This certificate proves that a synthetic dataset was generated by CertifiedData and its contents match the cryptographic fingerprints recorded at issuance time.
The Ed25519 signature covers the full certificate payload including artifact hashes. Any modification to the ZIP file or inner CSV files will produce a different SHA-256 hash that will not match the certified values.
The certificate does not verify statistical quality or differential privacy unless explicitly stated in the generation metadata.