AthenXiv content page
slug: timestamping
locale: en
title: How timestamping works
-----

# How timestamping works

## In one sentence

When you upload a paper, the SHA-256 digest of every file is submitted to public OpenTimestamps calendars and ends up anchored in the **Bitcoin blockchain**. You receive an `.ots` proof that can be verified in your own browser — **without trusting this site, and without this site still existing**.

## Step by step

1. **Hash locally.** Each file (the PDF and every attachment) is hashed with SHA-256. **Only the 32-byte digest leaves this server; the contents of your paper never do.**
2. **Submit to calendars.** The digest is sent to several public OpenTimestamps calendars (aggregators). Each returns an operation chain proving it accepted that digest at that moment.
3. **Build the proof.** The chains are merged and stored as an `.ots` file, offered for download on the paper page.
4. **Wait for confirmation.** Calendars aggregate digests into a Merkle tree and commit it in a Bitcoin transaction. That normally lands in a block within one to three hours. This site polls the calendars on a schedule (and opportunistically when a paper page is viewed) and replaces the pending proof with one carrying the **block height**.
5. **Verify independently.** Download the `.ots`, open <https://opentimestamps.org/#stamp-and-verify> and drop the proof (and optionally the PDF) into the verification area. Your browser recomputes the whole chain and compares it against the block header.

## What it proves — and what it does not

| Proves | Does not prove |
| --- | --- |
| The file **existed** at a given Bitcoin block time | that the content is correct, original or important |
| The file is **unchanged** since then (one altered byte fails) | who wrote it, or that the authorship is genuine |
| The proof is verifiable **without trusting this site** | that the paper was peer reviewed |

**Note:** while a proof is still pending, the calendar has recorded only its URI — the proof contains *no time information at all*. The "submitted at" date shown on such a page is this site's own record, and we label it as not yet cryptographically anchored. The block time appears once confirmed.

## Why this matters for authors

* **Priority**: rejection, withdrawal, takedown or this site going offline do not invalidate the proof;
* **Evidence**: in a plagiarism dispute you can produce a proof bound byte-for-byte to your file;
* **Cost**: free for authors, readers and citers;
* **Public**: anyone can download and verify it — reviewers, editors, journals, courts.

## Calendars and privacy

The public calendars used by default:

* https://a.pool.opentimestamps.org
* https://b.pool.opentimestamps.org
* https://a.pool.eternitywall.com
* https://ots.btc.catallaxy.com

They are donation-funded, need no registration and no API key. **Only the digest is submitted**: a calendar sees 32 opaque bytes and cannot recover your title, abstract or authorship.
