STAMP.WARPYARD.COM

independent OpenTimestamps calendar

Prove it existed.
Anchored in Bitcoin.

This is a public OpenTimestamps calendar server. It aggregates document hashes into a merkle tree and commits the tip into the Bitcoin blockchain through our own archival full node — a cryptographic notary with no trusted third party. Timestamping is free; your file never leaves your machine.

Pending commitments
Best block
Wallet (sats)
Server

Use it

# install the client
$ pip install opentimestamps-client

# stamp a file against this calendar (writes document.pdf.ots)
$ ots stamp -c https://stamp.warpyard.com -m 1 document.pdf

# later — once the calendar has written its Bitcoin attestation —
# upgrade the receipt to a self-contained, independently verifiable proof
$ ots upgrade document.pdf.ots
$ ots verify document.pdf.ots

How it works

1 · Aggregate

Your client submits a salted SHA-256 digest. The calendar folds every digest received each second into a merkle tree.

2 · Commit

The merkle tip is written into a Bitcoin transaction (OP_RETURN) from this server's wallet, RBF-bumped until it confirms.

3 · Verify forever

After confirmation, your .ots receipt upgrades to a proof any Bitcoin node can verify — no calendar, no server, no trust required.

API

EndpointDescription
POST /digestSubmit a raw 32-byte digest; returns a serialized pending-attestation timestamp.
GET /timestamp/<hex>Fetch the (upgraded) timestamp for a commitment.
GET /statusRaw calendar status page (pending count, wallet, recent txs).
Bitcoin attestations are batched (≥ 6 h between transactions) to keep fees sane — a pending receipt is normal and upgrades automatically. This calendar is best-effort community infrastructure: for critical documents, stamp against several calendars (the default ots stamp behaviour) as well as this one.