Skip to content
FactLockCam
Founder on LinkedIn (opens in a new tab)

Trust bounds

Threat model

Verifies the exact file and signed record—not the physical truth of the scene. Use this page when you need the launch ceiling, not a sales pitch.

  • device_key_class: software
  • No gas or uptime SLA
  • Password ≠ chain attestation

What a passing check can show

  • Inspected bytes match the recorded SHA-256 fingerprint.
  • The canonical manifest hash matches and the owner signature recovers to the recorded address.
  • When a transaction hash is present and confirmed, the manifest hash appears in that Polygon transaction.

What it does not show

  • The physical truth of the scene, a named identity, an exact capture instant, court admissibility, or that a claim will be paid.
  • Hardware camera origin or hardware-backed signing. The device_key_class in a manifest is self-reported by the device, not externally attested; the owner signature is a software key. Attested keys are roadmap.
  • A public record for an offline or deferred seal. Those packages still support file and signature checks; the chain result stays pending.
  • That a correct package password equals a chain attestation. Password unlock only opens the envelope.

Professional evidence rules

Evidentiary discussion for professionals lives in the Terms of Service. It is not a consumer guarantee on this site.

Inspect a live original/altered pair on /deepfake-defense/.

Next step

Know the ceiling. Then capture.

Everything above is disclosed in the manifest and on the certificate. Nothing is hidden behind a marketing claim.