BLOG
On provenance, in practice.
Notes on content provenance, the C2PA standard, and the engineering behind verifiable media. Less product news, more how it works.
- 5 min readStandardsC2PA
Why content provenance needs an open standard
Provenance only works if a claim signed by one party can be checked by another. That requires a shared format, not a vendor database. Here is the case for building on C2PA rather than around it.
Read post - 6 min readEngineeringVerification
Soft bindings: finding provenance after the bytes change
An embedded manifest is the happy path. The hard part is recovering provenance after a file has been re-encoded, cropped, or stripped of metadata. That is what soft bindings are for.
Read post - 5 min readEngineeringSigning
Anchoring manifests to a public ledger, without putting them on it
Tamper-evidence does not require publishing your content to a blockchain. It requires publishing a commitment. A design note on how Merkle anchoring would give independent proof without leaking data or paying per manifest.
Read post