Media & content

Fakes will circulate. The real one can still be proven.

Attach a proof at the moment you publish, and readers and partners can check for themselves which one is genuine — instead of you chasing every fake after the fact.

Talk to us Verify a proof yourself

Reader's browser — verifying an article

Not tampered with

DOC HASH0x68d4…9f01

IssuerThe Daily Record

Published2026-07-28 09:12

SubjectPublished article & photos

Proof classProvenance

Signature matches Tamper check Issuer confirmed

The proof layer
is running now

Verification Center live 3 proof-backed data feeds Verification is free

See it for yourself →

01 — Why LemmaLooking at it is no longer enough to tell.

Deepfakes and generative models can now produce a photo, a paragraph or a video that nobody can tell from the real thing by eye. What you have to protect is your own output. Finding fakes and taking them down is a race you do not win; being able to point at the genuine one first is both faster and more certain.

Point at the real one.
Stop chasing the fakes.

02 — What changesThree things Lemma changes

Readers can tell which one is yours

Your own output carries the proof, so a reader can confirm which version is genuine without waiting for a takedown to go through.

Reader's verification screen

What is being checkedPublished article

IssuerThe Daily Record

Query to issuerNot needed

VerdictNot tampered with

Incoming material

Field photography (RAW)Photographer knownProof attached

Supplied footageSource knownProof attached

Contributed copyAuthor knownProof attached

AI-assisted imageryDeclaredProof attached

Origin established before you publish

Field photography, contributed copy, generated imagery — establish the origin of everything you use before you publish, and you avoid the corrections and rights disputes that follow publication.

Anyone can check, and no one needs a key

Verification is free and needs no key. Anyone can do it by opening a link, and every check is one more reader who has confirmed it directly.

POST /v1/proofs/verify

// Free, no key — the reader settles it alone { "docHash": "0x68d4…9f01" } // What comes back { "valid": true, "issuer": "The Daily Record" }

03 — Threat casesWhat happened when checking by eye stopped working.

Three cases from this area, drawn from the Lemma Critical Briefs. In each one, nothing about the appearance or the format separated the genuine from the fake.

No. 105Over 40,000 unauthorized likeness and voice posts — a 100% takedown rate, and the same models reappearedData Provenance No. 053Fake celebrities drew 200 million views, and nobody checked where the likeness came fromData Provenance No. 011The SynthID watermark was stripped statisticallyData Provenance

See every Brief in this area →

04 — How it worksThree steps, and that's it.

Issuing the proof

RecordPublished article & photos

IssuerThe Daily Record

What is sentHash only

Issued 0x68d4…9f01

01Attach a proof

Why it holdsChange one character in the piece and it no longer matches the proof.

One API call at publication. The body of the piece is never sent.

What you publish