Skip to content
FactLockCam

Anchor the Original.

What an anchored original is

FactLockCam creates the reference first: exact-file fingerprint, signed capture manifest, and a Polygon transaction that stores a fingerprint of the signed record, made when the phone is online. Offline captures are anchored after it reconnects.

Verifies the exact file and signed record—not the physical truth of the scene.

  • SHA-256 fingerprint
  • Signed manifest
  • Polygon anchor
  • Zero-upload check

What the record contains

  • SHA-256 of the captured bytes
  • Canonical capture manifest, hashed and signed by the owner key
  • Disclosed device key class: hardware-backed where the phone has it (Secure Enclave on iOS; StrongBox or TEE on Android). The owner signature uses a software key held in the phone's secure storage.
  • A public Polygon transaction once the device can reach the network (pending until then)

What recipients can check

A small proof opens at factlockcam.com/open. The recipient unlocks it on their own device and sees three separate results: file, signature, and public record. Nothing is uploaded. A large proof opens in the free FactLockFile desktop Viewer, coming for Mac, Windows and Linux once each version is tested.

The capture time is the phone's own clock. Polygon shows the record existed no later than its block.

Verifies the exact file and signed record—not the physical truth of the scene.

See the threat model for deferred anchors, what the unlock link does not prove, and what is not proven.

Next step

Anchor your own original.

Capture inside FactLockCam and the reference exists before anyone can dispute the copy.

with the FactLockCam app.

Tamper-evident archive · signed record · public-record anchor on Polygon.