Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

For researchers, designers, inventors and R&D teams

When someone claims they had it first, show that you had it, on a date nobody can move.

A design copied, a dataset disputed, a former partner claiming an idea. The quickest way to settle it is to show the exact file was in your hands by a certain date, without having had to publish it.

Try it in two minutes Talk about a pilot
When it is tested
A dispute with a former partner or employee; a design or copyright dispute; a trade-secret case; a question of who contributed what in a collaboration.
What you will be asked for
Evidence that a specific document, design, dataset or piece of code existed, unchanged, by a given date, and that it was in your possession then.
What goes wrong today
File dates are trivially changed, emails can be edited and forwarded, and publishing something to prove its date gives it away.
What changes
Seal the file’s fingerprint and keep the file private. The date rests on our signed log, two independent time-stamps and a Bitcoin anchor, not on your word.

Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. A seal is not a patent or a registered design and gives no exclusive right; it is evidence that a file existed unchanged by a date.

Try it in two minutes

  1. Choose a real file of your own: a notebook page, a design file or a dataset. It is read in your browser and never uploaded.
  2. Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
  3. Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.

From your own systems it is one API call per record. Integrate · Other industries