Cryptographic Provenance

The property that any unauthorized modification to a data object or its provenance metadata is immediately detectable through cryptographic verification. This is achieved by computing a cryptographic hash of the content and signing it. If a single bit changes, the hash output diverges completely, breaking the signature chain. This ensures that the manifest and the asset it describes remain inextricably linked and auditable.

• Relies on collision-resistant hash functions like SHA-256
• Forms the basis of the C2PA hard binding mechanism
• Enables detection of both malicious tampering and accidental corruption

A guarantee that the creator of an assertion or asset cannot credibly deny having generated it. This is established through asymmetric cryptography, where an actor signs a hash of the content with their private key. Anyone with the corresponding public key can verify the signature, proving the signer's identity. In a W3C Verifiable Credential, this binds the issuer to the claims they make.

• Uses algorithms like ECDSA or Ed25519
• The manifest in C2PA contains a signed set of assertions
• Distinguished from simple attribution, which lacks cryptographic proof

The ability to prove that a specific event, such as a content capture or an edit, occurred before or after another event without trusting a single clock. This is often achieved by anchoring a Merkle root of the event's hash into a public, append-only transparency log or a distributed ledger. The timestamp becomes part of the verifiable provenance trail.

• Prevents backdating of content or signatures
• Uses trusted timestamping authorities or blockchain anchoring
• Critical for establishing priority in intellectual property disputes

The property that the entire history of a data object—from its initial capture through every subsequent transformation—is recorded as a directed, acyclic lineage graph. Each node in the graph represents an entity, activity, or agent, as defined by the W3C PROV standard. This allows an auditor to trace a final output back to its raw source ingredients, verifying the attribution chain in full.

• Models dependencies as a graph, not a simple list
• Enables impact analysis when a source is found to be compromised
• Supports complex editing workflows with multiple contributors

The capacity to cryptographically verify that a specific claim or piece of data is part of a large, hashed dataset without downloading the entire dataset. This is accomplished using a Merkle proof. A verifier only needs the root hash of the Merkle tree and a small set of intermediate hashes to confirm membership. This is essential for scaling provenance verification in systems like Certificate Transparency logs.

• Verification complexity is O(log n), not O(n)
• Enables lightweight clients to verify data integrity
• Used in Hashlink URIs for content-addressable integrity

A privacy-preserving property that allows the holder of a provenance credential to reveal only the specific claims necessary for a transaction, without exposing all associated metadata. Using techniques like BBS+ signatures or zero-knowledge proofs, a subject can prove a statement about an attribute (e.g., 'the author is a verified journalist') without revealing the author's actual identity or signing key.

• Prevents unnecessary correlation of user activity
• A core feature of advanced Verifiable Credential implementations
• Balances the need for trust with the right to privacy

A method of attribution where provenance metadata is cryptographically and inseparably embedded within the bitstream of the content asset itself, ensuring the metadata cannot be lost or stripped during transit or transformation.

• Contrast: Soft binding stores metadata in separate headers or sidecar files, which are easily removed
• Technique: Watermarking or steganographic embedding at the codec level
• Importance: Critical for maintaining an unbroken chain of custody in adversarial environments

A cryptographically signed statement made by an entity about a subject, forming the basic building block of verifiable credentials and content provenance manifests.

• Structure: A JSON-LD object containing a subject, property, and value, signed with the issuer's private key
• Verification: Any party can verify the signature using the issuer's public DID
• Composability: Multiple assertions are bundled into a manifest to create a complete provenance record