What Truestamp Is
Plain-language overview of Truestamp, the data-integrity and timestamping service that turns submitted data into a portable signed proof of the exact bytes and of a provable submission window, which anyone can check against public chains and sources without trusting Truestamp.
Overview
Truestamp is a data-integrity and timestamping service. You submit a piece of data, and Truestamp gives back a small, self-contained cryptographic proof. That proof shows two things: that your data existed in exactly that form, and that you submitted it to Truestamp within a provable submission window. The proof is portable and independently verifiable. Anyone you hand it to can check it for themselves, without asking Truestamp whether it is real and without running any Truestamp software: every hash a verifier compares is one it recomputes from what the proof carries, and the submission window is read from public blockchains and public randomness sources, never from Truestamp.
If Truestamp is offline or gone, an offline run still confirms the proof’s integrity and its recomputed chain, and a run given a keyring the holder saved, or a keyless run, still draws the window; a default online run reads Truestamp’s keyring and fails until it answers. Each case is worked through in proof claims by availability.
Why it matters
People and organizations often need to show, later and to a skeptical party, that some specific data existed at some point in the past. A signed contract, a creative work, a measurement, an audit record, a research snapshot, a written statement: all of these can lose their value if there is no trustworthy way to pin down when they were submitted and to prove they have not been altered since.
A Truestamp proof is checked by recomputation and by reading public records. A verifier recomputes every hash it compares from the bytes the proof carries, and reads both edges of the window from public blockchains and public randomness sources that Truestamp does not control. The proof carries the records and pointers those reads start from.
The core idea
The service works in three plain steps.
- You submit data. You can submit a fingerprint (a hash) of a file you keep on your own device, or you can submit the actual content directly when the content itself is what you want to attest. Either way, Truestamp records a cryptographic representation of exactly what you submitted. The step-by-step walkthrough is submit an item.
- Truestamp binds it to a submission window. At the moment you submit, Truestamp records the hash of each record that already existed: the newest reading it has captured from each public randomness source it watches, and the current head of its own ledger. Those hashes are folded into your submission’s fingerprint, so which records you submitted against is settled then and there and cannot be changed afterwards. Your submission’s fingerprint then becomes a leaf of a ledger block, and the block is committed, in a batch, to public blockchains. That gives your data a submission window: submitted after those public records were published, and before the public chain recorded the batch that holds its block. Your submission passes from a freshly submitted state, through processing, to a committed state once it is in its block.
- You get a portable proof. Once its block is committed to a public chain, Truestamp produces a proof you can download and keep: one small JSON file, signed by Truestamp. The proof carries every record a checker needs to re-derive the whole cryptographic chain on their own, including the public records the submitted-after edge of your window rests on.
The timing claim is the submission window: Truestamp proves when data was submitted, not when it was originally created.
Independent, portable verification
Anyone can check the proof, anywhere, without asking Truestamp whether it is real. A verifier re-derives the whole chain, from your submitted data all the way out to the value written in a public-blockchain transaction, from the proof in hand. Every hash a verifier compares is one it recomputed from bytes the proof itself carries, so a checker never has to accept a number that only Truestamp could have produced. Offline, that shows the proof is intact and signed by a Truestamp key; the submission window comes from reading the public chains and randomness sources the proof names, which a verifier does online. Which key may sign is settled by a keyring of Truestamp’s keys: a verifier online reads Truestamp’s published keyring in each run, and offline uses the one built into it (see verify a proof).
Truestamp also publishes a public verification page, a convenience beside verifying for yourself: open a public item, block, beacon, or entropy observation by its identifier and read a full verification report. No account is needed to read one, and anyone can locate public items, blocks, beacons, and entropy observations to verify via the search page. For an item you can also check a local file against what was timestamped: your browser computes the file’s fingerprint on your own device, so the file itself never leaves your machine, or you paste a fingerprint you already have. The same verification can also be done programmatically or with independent tooling built by third parties, because the proof format is open and documented well enough for anyone to write their own verifier.
Who it is for
- Individuals and teams who need durable, tamper-evident records of when data was submitted and proof that it has not changed since: contracts, creative works, measurements, audit trails, compliance artifacts, research snapshots.
- Applications and services that want to timestamp their own data, or their users’ data, with a third party and later prove it without that party’s help.
- Auditors, courts, and counterparties who need to check such proofs without trusting either the person who submitted the data or Truestamp.
Use of the service is governed by the published Terms of Service and Privacy Policy; see the legal documents.
What Truestamp does and does not claim
Truestamp proves that specific data existed in a specific form, that the data was submitted to Truestamp within a provable submission window, and that this fits into a verifiable chain committed to public blockchains. For the full statement of these guarantees, see what Truestamp proves.
It does not prove when the data was originally created, who authored the underlying data, or anything about the data beyond the bytes themselves. For the limits, and why they matter, see what it does not prove.
Each list has its own concept, and the two link to each other. For help, or to report a security issue, see support and contact channels.