Blockchain timestamping for engineering firms
By BlockchainSignLast updated
Engineering work generates exactly the kind of record that becomes valuable later and impossible to reconstruct: iterations of a design, dated, confidential, and mostly unpublished. A timestamp fixes what you had on a day without the files going anywhere.
The moment this matters
Three of them, and they are all before something rather than after.
Before you file. A patent application takes months and costs thousands. The design existed long before either. A timestamp of the CAD files, the calculations and the test results gives you a dated record of the work as it stood while you were deciding whether to file at all.
Before you disclose. A prospect, a factory, a distributor, a trade show. Once a design has been shown, "who had it first" becomes a question of evidence. Worth knowing: the US allows a one-year grace period after your own disclosure, but most other jurisdictions have no grace period at all — a public showing before filing destroys novelty there. If international protection matters, the disclosure date is not a detail.
Before a design freeze. When a revision becomes the revision, a dated record of exactly which bytes that was removes a whole category of later argument, internally and with suppliers.
The objection: doesn't a patent do this?
It does, later and for a great deal more money — and only for what you actually file.
A patent is a granted monopoly on a specific claimed invention. A timestamp is evidence of a date. They are not substitutes, and the timestamp is not trying to be one. What it covers is the gap: the months of work before the application, the designs you decided not to file, the iterations that show how you got there, and the CAD files and drawings that are copyrightable as graphic works even where the product itself is not.
At around ten dollars a record, timestamping every significant revision is a rounding error against an engineering budget.
Why the confidentiality model matters here
Every conventional option for dating a document involves giving it to someone. A notary sees the paper. A deposit service archives the file. An escrow agent takes custody.
For a pre-patent design, that is the problem rather than the solution.
Here the file is hashed in your browser with the Web Crypto API, and only the 64-character SHA-256 hash is transmitted. There is no upload endpoint for the file, because nothing would use it. You can watch this in your browser's network tab, and the free hash tool runs the same code with nothing sent anywhere at all.
Practically: a STEP file, a full assembly, a folder zipped into one archive — none of it leaves the machine it is on.
A workflow that fits how engineering actually runs
| When | What to timestamp | Why |
|---|---|---|
| Concept settled | Sketches, initial CAD, calculations | The earliest artefact is the most valuable one |
| Each significant revision | The assembly, the drawing set | A sequence tells a story of development |
| Before any disclosure | The exact package you are about to send | Fixes what you had going in |
| Design freeze | The released revision | Removes argument about what "the" version was |
| Before filing | The disclosure document | Supports the conception date |
What it proves, and what it does not
It proves that a specific file existed by a specific time and has not changed since. That is existence and integrity.
It does not prove who designed it, it is not a patent, and it does not create any right. See proof of existence vs proof of authorship for exactly where that line falls, and is a blockchain timestamp valid in court for how courts have actually treated this evidence.
Used for what it is — a cheap, permanent, independently checkable anchor on a date — it is one of the better records an engineering team can create in the time it takes to save a file.