Provenance Chain

Each version of an asset is linked to its predecessor through a one-way cryptographic hash function. The hash of the previous manifest and content is included in the next, creating a sequential chain where any retroactive alteration to a prior state immediately invalidates all subsequent hashes. This provides mathematical tamper-evidence.

• Uses algorithms like SHA-256
• Forms a Merkle-DAG structure
• Ensures edit history integrity

Every claim about the asset—such as its creator, creation timestamp, or an edit action—is recorded as a structured manifest assertion. These assertions are digitally signed and bound to the content's hash, making the metadata inseparable from the specific binary state it describes. This prevents metadata from being swapped between files.

• Uses C2PA standard assertions
• Includes ingredient assertions for composite media
• Creates non-repudiable claims

The chain's trustworthiness depends on strong identity anchoring. Each signature in the chain is generated using a private key whose corresponding public key is bound to a verified identity through an X.509 certificate. This certificate chain must be traceable back to a trusted root Certificate Authority (CA), establishing a trust anchor.

• Validates the signer's real-world identity
• Supports certificate revocation checks via OCSP
• Enables trust list curation by validators

To prove that data existed before a specific moment and to prevent backdating, a Trusted Timestamp Authority (TSA) is used. The TSA cryptographically binds the hash of the manifest to a precise, verifiable point in time, providing irrefutable temporal evidence that is critical for legal and compliance scenarios.

• Complies with RFC 3161 standard
• Provides non-repudiation of time
• Counters signature expiry concerns

The provenance chain's resilience depends on its binding method. Hard binding embeds the signed manifest directly into the asset's binary file structure (e.g., using JUMBF in a JPEG header), ensuring it survives basic file transfers. Soft binding stores the manifest as a separate sidecar file, linked by a content hash, which is useful for formats that don't support embedding but is more fragile.

• Hard binding: embedded in file header
• Soft binding: external sidecar file
• Choice impacts survivability of metadata

A full provenance chain is not just a linear sequence but a directed acyclic graph (DAG). It maps all ingredient assertions—the source media used in a composite asset—and action assertions—the operations performed. This graph provides a complete, auditable visual and programmatic map of every fork, merge, and transformation in the asset's lifecycle.

• Represents complex derivative works
• Tracks all source ingredients
• Models non-linear creation workflows

A sequential chain of hashes linking each version of an asset to its predecessor. Each link contains the hash of the previous state plus the new content, creating a tamper-evident edit history. If any historical version is altered, all subsequent hashes become invalid. This forms the immutable backbone of a provenance chain, ensuring that the complete transformation history can be mathematically verified from the original asset to the final derivative.

Two strategies for attaching provenance manifests to digital assets. Hard binding embeds the signed manifest directly into the file's binary structure (e.g., JPEG header via JUMBF), ensuring the provenance data travels with the asset. Soft binding stores the manifest externally as a sidecar file or cloud URL, referenced by a content hash. Hard binding offers superior portability and resilience, while soft binding enables provenance for formats that cannot be modified.

A visual or programmatic representation of the provenance chain as a directed acyclic graph (DAG). Nodes represent assets or actions, while edges represent derivation relationships. The graph captures complex scenarios like:

• Composite images: Multiple source ingredients merged into one output
• Branching edits: Parallel derivative works from a single source
• Re-signing events: Custody transfers between parties This structure enables auditors to trace any pixel back to its origin.