PSPratyush Shivam

Evidence, anchored

Shipment documents are fingerprinted on a permissioned blockchain, so every party can verify them instead of disputing them.

01 · Context

Disputes start with documents

A delivery note is signed, scanned, forwarded and re-saved. When two versions disagree weeks later, nobody can show which one is original.

02 · Challenge

Prove integrity without exposing content

Freight documents are commercially sensitive. The proof had to be shareable between companies while the documents themselves stayed private.

03 · Thinking

Anchor the fingerprint, keep the file

Only a cryptographic fingerprint of each document goes on chain. The file stays where it belongs. Anyone with the document can check it; nobody can read it from the ledger.

04 · Engineering

Approvals as contracts

Smart contracts encode who has to approve what, and in which order, following each company's own signing route. Transaction signing is handled by a dedicated service, so applications never touch keys.

05 · Result

Verified instead of argued

Any party can confirm that a document is the one that was approved, when, and by whom. The question "is this the right version?" has a checkable answer.

06 · What I learned

Be exact about what you prove

A fingerprint shows a document has not changed. It does not show the document was true. Saying that plainly is what makes the rest of the claim credible.

Film

Documents, approved

Approvals on the shared record. A thirty-second explanation of the idea behind this work.

Details are described at the level of problem and approach. Implementation specifics stay with the company.