9 min read
Hash each AI output, prompt, manifest, or Content Credentials record, batch the hashes into Merkle roots, and publish timestamped Label 309 commitments — proving any single item existed without putting every asset or private prompt on chain.
AI & ProvenanceDevelopers
9 min read
Commit a private dataset snapshot to a hash or Merkle root and publish one timestamped proof. The data stays private; later you can selectively prove a file, row, or version was in the committed set.
AI & ProvenanceSecurity
8 min read
C2PA describes where media came from; Label 309 anchors the asset or its manifest to an independent public Cardano timestamp. Here is how the two layers fit together.
AI & ProvenanceThe Standard
8 min read
Hash a dataset manifest, batch it with a Merkle root, and anchor it on Cardano with Label 309 — so you can later prove what a dataset snapshot contained without publishing the dataset.
AI & ProvenanceDevelopers
8 min read
Hash your source files, drafts, prompts, exports, or whole project folders and publish a timestamped Label 309 proof that they existed by a given time — without making the work public.
AI & ProvenanceGuides
7 min read
A Label 309 proof shows that a media file existed by a public time. Authenticity needs more: capture context, provenance, signatures, and human verification. Here is how the timestamp layer fits.
AI & Provenance
8 min read
C2PA describes the provenance of a media asset; Label 309 anchors a timestamped commitment to its bytes on Cardano. Here is what each one proves, and why most workflows want both.
The StandardAI & Provenance