Why a re-uploaded video doesn't match its timestamp
You downloaded a video, checked it against its proof, and it doesn't match. Most of the time that doesn't mean anyone tampered with it. It means you have a different file.
Fingerprints match exact bytes
A timestamp proof covers a file's SHA-256 fingerprint. Change any byte and the fingerprint changes completely, with no “nearly matching”. That's what makes a match meaningful, and it's also why a match is easy to lose.
Most copies aren't the original file
- Video platforms and social networks re-encode uploads into their own formats and sizes, and usually remove metadata. What you download is a new file made from the original.
- Messaging apps often compress videos before sending them, unless they're sent as a document or file.
- Editing apps write a new file on export, even if you changed nothing.
- Screen recordings of a video are new videos.
Every one of these copies can look identical to the eye and still have a different fingerprint.
What a mismatch means
- It doesn't show the video was doctored.
- It does show this proof can't vouch for this copy.
To use the proof, ask whoever stamped it for the original file, sent in a way that keeps it intact: a cloud storage link, a file transfer service, or a messaging app's “send as file” option. Then check that file.
What about “perceptual” matching?
Some systems compare how videos look rather than their bytes, so a re-encoded copy still matches. They're useful for finding copies, but they can also match a cleverly edited version, so they can't show a file is unchanged. Existed By deliberately uses exact fingerprints only.
If you're the one stamping
Stamp the original file from the device, before you send it anywhere, and keep it. If you also stamp the version you publish, you can show both: the original existed by one time, and the published edit by another.