Use case
Media Authenticity and Provenance Verification
How Noesea uses cryptographic provenance and content-addressed evidence to make images, video and documents verifiable at the receiving side — provenance over deepfake detection.
On this page
The problem with detection
As generative models improve, forensic deepfake detection becomes a losing arms race: the score is probabilistic, it degrades over time, and the person receiving the media still has to trust the detector. Newsrooms, courts and platforms need something that holds up regardless of how convincing synthetic media gets.
Provenance-first verification
Noesea records where an artifact came from and how it changed. Media is hashed, anchored under a Merkle root, and tied to custody events and C2PA-style provenance signals. A receiver can confirm the origin and integrity of a file without trusting whoever sent it — and without relying on Noesea-operated infrastructure.
When authenticity is contested
If a media claim is challenged, the protocol settles it with stake-backed juror voting and records the outcome, the confidence, and the dissent. The result is a durable, auditable record of how a contested piece of media was reviewed — not an editorial verdict you are asked to take on faith.
FAQ
Common questions about media authenticity
Does Noesea detect deepfakes?
Noesea prioritizes provenance over detection. Instead of guessing whether media is synthetic, it records and anchors verifiable origin and custody so authenticity can be checked directly. Detection signals can be attached as evidence, but the durable basis is provenance.
How does a receiver verify a piece of media?
The receiver checks the content hash against the anchored evidence record, reviews the custody chain, and confirms provenance signals — using a browser check, the verification console, or a portable report. No trust in the sender is required.
Does Noesea store the media itself?
No. Noesea anchors hashes, Merkle roots, custody events and outcomes — never raw content on-chain. The media stays in content-addressed storage (such as IPFS) while the proof record references it.
Continue