When people talk about blockchains for business documents, one confusion comes up more than any other: treating a fingerprint as if it were a signature.
They are both useful. They prove very different things.
What a fingerprint proves
A fingerprint, technically a hash, is a short value computed from a file. Change one comma in the file and the fingerprint changes completely. Anchor that fingerprint on a ledger and you can later show that the file has not changed since that moment.
That is genuinely valuable. Nobody can quietly edit a delivery note after the fact and pretend it was always that way.
What a fingerprint does not prove
- Who agreed to it. A fingerprint has no author. Anyone can compute one.
- That the content is true. A wrong delivery note, anchored perfectly, is still wrong.
- When the event happened. It shows when the file was recorded, not when the goods actually arrived.
What a signature adds
A signature is a person or a company saying "I stand behind this". That needs real identities, keys that belong to them, and a clear record of who signed what, and in what order. In freight, that order matters: the carrier confirms delivery, then the receiver confirms what arrived, then the shipper accepts.
Label honestly
A good system shows both, and labels each one precisely. If your interface shows a green tick for a file that was only fingerprinted, you are promising more than the system checked. People notice eventually, and trust is hard to win back.
I set out these distinctions in more detail in a short open-access paper: What a permissioned ledger can and cannot prove about business documents.
I'm Pratyush Shivam, CTO at Konfidio in Berlin, where we build TrustedTrucks. More about my work at pratyushshivam.com.
