You care about your intellectual property, so you take the proper precautions: you obtain digital timestamps from qualified trust authorities to legally establish that your work existed at a specific point in time.
You store the certificates securely. You keep the files intact. You never intentionally edit or alter them.
Then, when the stakes are high (e.g. defending your copyright or proving prior use in a trademark dispute) you run the verification. It fails.
How does cryptographic proof collapse without any conscious mistake? The answer is subtle: everyday desktop tools routinely alter files in the background without prompting you and without you ever clicking "Save."
Here are three common scenarios that silently break your chain of custody:
1. Reviewing a PDF in macOS Preview
You open a document, a technical drawing or a schematic. A page is sideways, so you rotate it 90 degrees to read it, then close the window. Because Preview autosaves continuously in the background, closing the window commits that change directly to disk. You never pressed Save, but the underlying file has been rewritten—and the certified hash is permanently broken. (Apple documentation)
2. Rotating a photo in Windows File Explorer
You browse photos of a prototype in Windows. One photo appears sideways, so you click "Rotate right." The image still shows the exact same invention, but Windows writes that orientation metadata directly into the file structure. Even a "lossless" rotation alters binary data. To human eyes, the image is unchanged; to a cryptographic verification algorithm, it is an entirely different file. (Microsoft documentation)
3. Playing an audio track in iTunes
You import a demo or interview recording into your library to listen to it. If features like Sound Check are enabled, the player can write volume-normalization tags directly into the file's ID3 metadata. The recorded audio has not changed by a single millisecond, but the container has. The digital fingerprint no longer matches. (ID3 documentation)
Three routine actions: reviewing a document, organizing photos, playing a recording. Three everyday ways to inadvertently sever the link between a certificate and its source file.
A certificate cannot reconstruct the original
A digital certificate anchors a strict cryptographic hash. Change a single bit, even invisible metadata buried in a file header, and the fingerprint mismatch is absolute.
This is true whether your proof is anchored on Bitcoin or issued by a qualified timestamping authority. Neither system can resurrect a lost or modified original; they only attest to the exact sequence of bytes registered at that moment. Overwrite every unaltered copy, and the certificate becomes functionally worthless.
Preserve the version you certified
Your active work shouldn't have to live under glass. You need to review blueprints, organize design assets, and listen to recordings without accidentally compromising your legal proof.
That is why Bernstein couples cryptographic certification with encrypted, versioned storage. Certified versions remain frozen and verifiable as your project develops, while client-side encryption ensures your proprietary assets remain strictly confidential. See: Bernstein features.
An immutable certificate is only as strong as the file it preserves.
