RFC 3161 timestamping and an evidence package that can be verified offline
A module to build into your software that requests the timestamp from an RFC 3161 authority, signs and chains your records and delivers them in a package that a third party checks offline with a command-line tool.
Proving that a file existed on a given date and has not been altered takes more than storing it. This RFC 3161 timestamping module signs and chains your records, requests the timestamp from a timestamping authority and puts everything together in a package that a third party can check offline.
Who it is for
Software companies, registration platforms for works or designs, compliance vendors and forensic experts who want to add proof of integrity and date to their product.
What RFC 3161 timestamping solves
- Evidence that depends on your database. The recipient checks the package with an independent tool.
- Dates with no outside backing. Each record carries the timestamp of a timestamping authority.
- Deletions nobody notices. If a record in the middle is missing, the check flags it.
What it does
- Requests the timestamp from the RFC 3161 authority you configure and stores its response with the record.
- If no authority is configured, it reports that the service is unavailable instead of using the server's clock.
- Signs each record with your application's key.
- Links each record to the previous one, so changes, deletions, corrupted data and broken chains are detected.
- Lets you prove that a specific file is included in a record without handing over the others.
- Generates a ZIP package with the signed manifest, the records, the timeline, the provenance in W3C PROV-O format and an HTML report.
- Includes a command-line verifier that checks the package's integrity with no network and no database.
- Optionally keeps a transparency log with the chained events.
Benefits
- You deliver evidence anyone can review without asking you for access.
- You detect any change or gap in the history.
Industry context
General industry data with its public source. These are not results of this product.
- In the EU, an electronic timestamp cannot be denied legal effect or admissibility as evidence in legal proceedings on the grounds that it is in electronic form or is not qualified. Qualified timestamps also enjoy a presumption of the accuracy of the date and time and of the integrity of the data. Source: Regulation (EU) No 910/2014 (eIDAS), Article 41(1) and (2). Regulation (EU) 2024/1183 keeps those two paragraphs and deletes the third.
What you get with each license
Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.
- The module code and the command-line verifier, ready to add to your product.
- Integration examples and documentation.
- A warranty against defects for the agreed period.
- Everything above, with the right to adapt and maintain it inside your product.
- Everything in the source code license.
- Our commitment not to license the module to third parties in the agreed sector or territory for the agreed term; for example, registration of works in one country.
- The right to integrate the asset into a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without requesting authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing the asset on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 5.9 on Node.js. Minimum supported version: Node.js 20.11 (declared in the configuration).
Frameworks: None. It ships as Node.js libraries and a command-line verification tool.
Database: Only the optional transparency log needs one, and it runs on PostgreSQL.
Operating systems: A server with Node.js. The verification tool runs offline on any computer with Node.js.
Interface languages: The evidence package report and the verification tool are in English.
Required infrastructure:
- An RFC 3161 timestamping authority (requires the buyer's own account).
- PostgreSQL, only for the optional transparency log.
Private deployment: It runs in your infrastructure. It only needs a connection to the timestamping authority you contract. Package verification works offline.
Main libraries:
| Library | Version | License |
|---|---|---|
| fflate | 0.8.3 | MIT |
| postgres (transparency log, optional) | 3.4.9 | Unlicense |
Dependencies with specific license terms: None.
Compatibility and integrations: RFC 3161 (Time-Stamp Protocol over HTTP) and W3C PROV-O in JSON-LD to describe provenance.
Redistribution terms
The asset's own code can be integrated into the licensee's commercial products under the embeddable module license, the source code license, the exclusive license and the OEM license, on the terms of the contract. None of the module's production dependencies has a copyleft license or specific commercial terms.
Installation requirements
A Node.js 20 or later application and the address of an RFC 3161 timestamping authority under your own contract. The transparency log is optional and needs PostgreSQL.
Frequently asked questions
Which timestamping authority do I need?
An RFC 3161 compliant authority, under your own contract. If you need a qualified timestamp under eIDAS, it has to be a qualified trust service provider; before signing up with one, check with us how it handles authentication.
Does the package replace a qualified timestamp or an expert report?
No. The package keeps the authority's timestamp and lets you check the integrity of the records. Its weight before a judge or a third party depends on the authority you choose and, where relevant, on an expert witness.
Is maintenance included?
No. Maintenance and integration support are contracted separately.
They fit with this asset
Request
Request information on M-EVI-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.