Seven steps.
Permanent proof.

Drop your file

Open the Stamp File page and drag any file into the drop zone — a contract, a photo, a design, a video, a spreadsheet. There are no restrictions on file type or size.

The file is loaded directly into your browser's memory. It does not travel over the network. No server ever receives it.

Your browser computes a cryptographic commitment

This is the heart of the system. Your browser runs two operations entirely on your machine:

First, it applies SHA-256 twice to your file, producing a 64-character file hash. Double-hashing is a hardening technique used by Bitcoin itself — it makes the hash more resistant to certain theoretical attacks.

Second, it generates a random 256-bit nonce — a secret number unique to this job — and concatenates it with the file hash. A final SHA-256 is applied to the combination, producing the commitment.

The commitment is a 64-character hex string that is mathematically bound to both your file and your nonce. It reveals nothing about the content of the file.

Save your receipt JSON — keep the nonce safe

Before payment, download the receipt JSON file. It contains your commitment, your nonce, and the job ID. This file is your key to verification later.

The nonce is critical. Without it, you cannot prove the relationship between your file and the on-chain commitment. The more copies you keep, the more secure your proof is.

You have two ways to preserve it: keep the receipt JSON in a secure location alongside the original file, and — once the timestamp is confirmed — generate the printable PDF certificate, which includes the nonce printed directly on it. A physical copy stored with your documents is a level of redundancy no cloud backup can match.

Pay 1 XRP via Xaman

The service generates a payment request: exactly 1 XRP, to the service wallet, with a unique Destination Tag that identifies your job. Scan the QR code with the Xaman wallet — the address, amount, and destination tag are pre-filled.

The Destination Tag is mandatory. It is how the worker matches your payment to your job. Without it, the payment cannot be attributed and the job will expire.

XRP settles in approximately 4 seconds.

The worker detects your payment and anchors the commitment on-chain

A background worker monitors the service wallet for incoming payments. When it detects your 1 XRP with the correct Destination Tag, it looks up your job and submits an AccountSet transaction to the XRP Ledger.

The commitment is encoded into the transaction's MemoData field as a JSON structure containing the commitment hash, the algorithm identifier, and a version number. This data is permanently attached to the transaction record on the ledger.

The worker uses the Reliable Submission pattern — it resubmits the transaction if needed until it receives ledger confirmation.

Generate your proof certificate

Once the transaction is confirmed, visit the Certificate page and paste your transaction hash. The page fetches the full transaction from the ledger and renders a printable proof certificate.

The certificate contains everything needed for independent verification: the commitment hash, your nonce, the transaction ID, the ledger index, the close time, and a QR code linking directly to the on-chain record.

Save it as a PDF. Print it on paper. Either copy is self-contained — verification does not depend on this website being online.

Verifiable forever — by anyone

To verify a proof, any third party follows a simple procedure: take the original file, apply the same commitment formula with the nonce from the certificate, and compare the result against the commitment recorded in the on-chain transaction.

If they match, the file provably existed — in exactly that form — at the moment the transaction was confirmed by the XRP Ledger. No trust in XRPL Timestamp is required. The ledger is the authority.