Verify a case file

Was this case file changed?
Check it against Robinhood Chain.

Drop the PDF. Your browser computes its SHA-256 fingerprint, recomputes the seal from its proof, and reads the seal transaction straight from Robinhood Chain. Your file never leaves this device.

Drop a case file hereor choose a file · PDF or any other file Fingerprinted locally · never uploaded

How the seal worksMethod

Fingerprint. Each case file's SHA-256 fingerprint becomes one leaf of a Merkle tree. The file itself is never sent.
One transaction per batch. Every few minutes the tree's root is written to Robinhood Chain in a single transaction.
Data layout. The transaction data is "FORENSA1" || root || count: 8 + 32 + 4 bytes.

What this page checks

1Your file's fingerprint, run through its proof, gives the batch root.
2That root is the one written in the seal transaction on Robinhood Chain.
3The transaction is confirmed in a block, which fixes the date.

Checks 2 and 3 read Robinhood Chain from your browser through a public RPC, not through FORENSA.

Was this case file changed?Check it against Robinhood Chain.

Was this case file changed?
Check it against Robinhood Chain.