Certified AI Artifact Certificate Record
education_lms-500rows.csv
This certificate records the SHA-256 fingerprint, issuance timestamp, and Ed25519 cryptographic signature for a registered AI artifact. It can be independently checked against the associated verification record without trusting any third party.
What this certificate proves
- ✓The artifact existed at the recorded issuance timestamp.
- ✓Its SHA-256 fingerprint was recorded at the time of certification.
- ✓The certificate payload was signed by Certified Data LLC using Ed25519.
- ✓Any modification to the artifact — even a single byte — produces a different hash and breaks verification.
- ✓The certificate has not been tampered with since issuance.
Certificate record
- Certificate ID
- 84b4ecdb-9404-48b4-814c-a02a3f3334b3
- Certificate Type
- GENESIS
- Issuer
- Certified Data LLC
- Issued At
- April 22, 2026 at 10:00 PM UTC
- Schema Version
- cert.v1
- Signature Algorithm
- Ed25519
- Signing Key ID
- ed25519-prod-2025-02
- Status
- ISSUED
- Artifact Name
- education_lms-500rows.csv
How to verify independently
No account required. Verification only needs the artifact file and the hash above.
sha256sum artifact.zip shasum -a 256 artifact.csv
Get-FileHash .\artifact.zip -Algorithm SHA256
- 01Compute the SHA-256 hash of your local artifact file using any of the commands above.
- 02Compare the result to the artifactHash shown on this page. A character-perfect match confirms integrity.
- 03Use the verification tool below to validate the Ed25519 signature and certificate status.
- 04For programmatic verification, the public key is available at /.well-known/certifieddata-public-key.pem.
Frequently asked questions
What does this certificate prove?
This certificate proves that the associated AI artifact existed at the recorded issuance timestamp, that its SHA-256 fingerprint was recorded, and that the certificate payload was signed with an Ed25519 private key. Any modification to the artifact changes its hash and breaks verification.
How do I verify the artifact hash?
Download the original artifact and compute its SHA-256 hash locally using sha256sum (Linux/macOS) or Get-FileHash (Windows). Compare your result to the artifactHash shown above. A match confirms the file is identical to the certified version.
What is the difference between this page and the verify page?
This page is a static, explanatory certificate record. The verify page (/verify/[id]) is an interactive tool that performs live signature validation and supports file upload for real-time hash comparison.
What algorithm signs the certificate?
Certificates are signed using Ed25519, a modern digital signature algorithm. It produces compact signatures and offers strong cryptographic guarantees. The public verification key is available at /.well-known/certifieddata-public-key.pem.
Can I verify the artifact outside the platform?
Yes. You need only the artifact file and the recorded SHA-256 hash. Compute the hash locally, compare against this record, and validate the Ed25519 signature using the public key without any CertifiedData account.
How this certificate was created
- 1Artifact fingerprinted using SHA-256 at time of registration.
- 2Certificate payload structured under schema version cert.v1 with issuer metadata, hashes, and algorithm specification.
- 3Payload signed using Ed25519 with a key managed by CertifiedData.io.