Skip to content
dfpn. Read the protocol

← Use cases · Newsrooms & content-trust ops

Audit-trailed verdicts for unsigned media

When a viral clip arrives without provenance, newsrooms need a defensible answer — a verifiable consensus of many detectors, plus a record of how they got it.

The problem

Most media a newsroom evaluates arrives without a signed manifest: reposts, screen recordings, anonymous tips. A single-vendor detection API gives a verdict but no reconstructable evidence, and its definition of "real" can change with a policy update. For editorial trust, "trust our model" is not enough — you want a staked, auditable consensus you can show your work on.

Where dfpn fits

How the flow works

  1. 01

    Submit

    Post the media hash and a fee through the SDK. The media stays in your storage; only its hash goes on-chain.

  2. 02

    Consensus

    Several independent workers analyze it and reach reputation-weighted consensus on a label and confidence.

  3. 03

    Cite

    Attach the on-chain audit trail — assigned workers, commits, reveals, contributing models — to your editorial record.

Honest caveat

dfpn is a detection signal, not an oracle. Adversarial media can bypass any detector; treat the verdict as strong evidence, not proof, and pair it with provenance when the producer cooperated.

Other use cases

Put it to work

Wire verdicts into your pipeline, or read how a verdict is produced end to end.