Current issuance scope
Model artifact certification vs. model artifact attestation
CertifiedData's current Certificate Policy does not certify the provenance or training history of external model artifacts. Existing weights, checkpoints, and model files can instead be notarized to create a signed integrity/existence attestation.
Supported today
Model artifact notarization
- ✓A SHA-256 fingerprint of the submitted model artifact bytes
- ✓An Ed25519-signed record issued by CertifiedData
- ✓A timestamp for the notarization event
- ✓A public verification path for checking the signed record and artifact fingerprint
Not established by notarization
Model provenance and quality claims
- —Who trained the model or which organization created the weights
- —Which training dataset, checkpoint lineage, or fine-tuning process produced the model
- —Model accuracy, safety, fairness, robustness, or fitness for a particular deployment
- —EU AI Act or other regulatory compliance
Use the notary when you need a verifiable model fingerprint
Keep the original model artifact. A verifier can later recompute its SHA-256 hash and compare it with the signed attestation. That demonstrates byte-level integrity relative to the notarized fingerprint without asserting unobserved training or compliance facts.