Guide · Evidence

Tamper-evident records explained: how a hash chain shows changes

A tamper-evident record is one where any later change shows. It works by giving each entry a fingerprint of its content plus the fingerprint of the entry before it, so the entries form a chain. Edit, remove, add or reorder anything and the fingerprints after it stop matching. It does not stop changes, and it is not proof that the content was true in the first place.

Last checked

On this page

The problem with ordinary records

Most digital records can be changed without a trace. A photo can be edited and saved, a note rewritten, a file’s date reset. When it matters what a file looked like on a certain day, a plain folder can’t tell you. Tamper-evident records solve one part of that: they make changes visible.

Step 1: a fingerprint for each item

Start with a hash, a short fingerprint of a file’s exact bytes. The guide to hash checksums explains it. Change one byte of the file and the fingerprint changes completely.

A list of files with their fingerprints already helps: check a file later, and if its fingerprint differs, it changed. But the list itself could be edited too. Someone could swap a file and update its line.

Step 2: link each entry to the one before

Here is the trick. Each entry in the record holds:

  1. what was added, and when,
  2. the file’s own fingerprint,
  3. the fingerprint of the previous entry,

and then the entry gets a fingerprint of its own, over all of that. Now every entry depends on every entry before it.

Picture a row of sealed envelopes, where each one also holds a photocopy of the seal on the envelope before it. Steam open one in the middle, and its seal no longer matches the copy inside the next.

What the chain catches

Because of those links, the chain shows:

  • An edited file. Its fingerprint no longer matches its entry.
  • An edited entry. Its own fingerprint changes, and the next entry no longer points at it.
  • A removed entry. The next one points at something that isn’t there.
  • An inserted entry. It breaks the link between two that used to fit.
  • A reordered pair. The links point the wrong way.

The function behind the fingerprints, such as SHA-256 from NIST’s standard, is public. Anyone can recompute the chain and see if it adds up.

Where its promise ends

A chain is only as strong as the copy you check it against.

  • Whoever controls the whole chain can rebuild it. They can change an early item and recompute every fingerprint after it. The new chain adds up perfectly; it just differs from the old one.
  • So something has to leave. Once a fingerprint, or a report of the whole chain, is sent to someone else or printed, that copy is a fixed point. A rebuilt chain won’t match it.
  • It says nothing about truth. A chain proves that a photo hasn’t changed since it went in. It can’t prove the photo shows what you say it shows.
  • The clock matters. An entry’s time comes from the device that wrote it.

You already use chains like this

The idea is older and wider than any one app.

  • The seal on a medicine bottle. It doesn’t stop anyone opening the bottle. It shows that someone did. That is tamper-evident in physical form.
  • Software history. Version control tools used by programmers link each saved change to the one before by its fingerprint, so a rewritten past shows up.
  • Public logs of web certificates. Browsers rely on logs built from linked fingerprints, so a certificate can’t be slipped in or quietly removed.

Each uses the same move: make every new entry depend on all the old ones, and let outsiders keep copies.

Making one count

  1. Add things as they happen. An entry’s time means more when it was written on the day.
  2. Send a copy out early. An email of the fingerprints to yourself or someone else, or a printout, is the fixed point.
  3. Keep the originals as they were. Edit copies, never the item in the record.
  4. Write down how to check it, so a stranger can recompute the chain without your help.

For damage photos meant for an insurer, insurance claim photos covers what to take.

Where Sealed helps, and where it doesn’t

It helps with stacks that keep this kind of chain, and a report that becomes your fixed point. An evidence stack makes a PDF report with each file’s SHA-256 fingerprint, and explains how to check a file yourself with shasum on a Mac or certutil on Windows. Each link of an evidence chain is written as plain text, so anyone can recompute its hash with standard tools. The evidence stacks page shows the screens.

It doesn’t make the chain impossible to rebuild. An evidence stack is not tamper-proof: whoever holds the vault key could rebuild a whole chain, so a report that has left the phone is the fixed point, and a file whose fingerprint matches that report has not changed since.

It doesn’t come with the free plan. Creating a time-sealed stack or an evidence stack is part of Sealed Pro, while opening one and adding to it are not.

Questions and answers

Is tamper-evident the same as tamper-proof?

No. Tamper-proof would mean nothing can be changed. Tamper-evident means a change can be made but can’t go unnoticed, as long as someone checks against a copy they trust.

Will a court accept a record like this?

That depends on the court, the place and the case. A chain of fingerprints is one kind of support for a record, not a guarantee. Ask a lawyer where it matters.

Can I keep adding to a chain?

Yes. New entries link to the last one. What you can’t do quietly is change an old one.

Sources

What this page says about Sealed was checked against the app on .

Last checked:

Get Sealed

Sealed is free to download, and Sealed Pro is an optional in-app purchase.