Skip to content
Veristamp Documentation

Introduction

Veristamp proves a file existed at a specific time, without uploading it anywhere.

What is a Veristamp receipt?

Section titled “What is a Veristamp receipt?”

A Veristamp receipt is a small JSON document that bundles everything needed to verify a file's timestamp:

  • A SHA-256 hash of your file — computed entirely in your browser
  • An ISO 8601 timestamp stating when the hash was submitted
  • An Ed25519 signature from Veristamp's active signing key
  • A receipt ID and cryptographic nonce for inclusion in the transparency log

You can verify any receipt offline using the pinned root public key — no network call required.

A Veristamp proof is portable: keep the original file, keep the receipt, and verification does not depend on Veristamp staying online.

How it works

Section titled “How it works”
  1. Hash locally: Your browser computes a SHA-256 digest of the file using the Web Crypto API. The file is never uploaded.
  2. Sign: The Veristamp signing service cryptographically signs the hash with the active Ed25519 key and returns a structured receipt.
  3. Commit to log: Within 24 hours, the receipt is sealed into a public, append-only Merkle log that is cryptographically tamper-proof.
  4. Epoch Anchoring: The daily log root is "cross-timestamped" by 4 public Timestamp Authorities (DigiCert, Apple, GlobalSign, Microsoft), providing undeniable mathematical proof of when the log was sealed (see Transparency Log).
  5. Verify offline: Anyone with the original file and receipt can recompute the hash, verify the Ed25519 signature, and confirm inclusion in the public log — all without network access (see Verify a Receipt).

Trust model

Section titled “Trust model”

Veristamp's signing key is rotated on a regular schedule to limit exposure. All keys — both active and retired — are published in a signed keyring (see Keyring Reference) at:

cURL
$ curl -s https://stamp.veristamp.in/.well-known/veristamp-keyring.json

Veristamp vs. Blockchain

Section titled “Veristamp vs. Blockchain”

While blockchains provide decentralized consensus, they are often slow, expensive, and require a constant network connection to verify. Veristamp is designed to be a high-performance, cost-free alternative for digital asset timestamping.

FeatureVeristamp (PKI + Merkle)Blockchain Timestamping
Transaction Cost100% Free (Zero Fees)Variable (Gas & Consensus Fees)
Processing SpeedSub-millisecond (Instant)Minutes (Block confirmation times)
VerificationOffline via CryptographyRequires active ledger connection/RPC
Data Privacy100% In-Browser (Local Hashing)Often exposes receipt data to public nodes
Environmental ImpactNone (Zero Carbon Primitives)High (Energy-intensive consensus)
Reliance on PKIYes (Ed25519 Keys)No (relies on network consensus)
Reliance on TSAsYes (Apple, DigiCert anchors)No
Anchor of TrustKeyring + Transparent R2 LedgerDecentralized Miners/Validators

Platform overview

Section titled “Platform overview”

Web Application

stamp-web-app

The browser-based app where you timestamp files and verify receipts. All cryptographic operations — hashing, signature verification, keyring validation — run locally on your device. Nothing sensitive leaves your browser.

Signing Service

stamp-worker

The API that receives file hashes, signs them with the active Ed25519 key, and returns receipts. It also orchestrates the daily Merkle sealing process that commits receipts to the public transparency log.

Transparency Log

roots.veristamp.in

Public, append-only storage for signed Merkle epoch checkpoints and epoch bundles. All transparency data is served directly from roots.veristamp.in for independent auditability — no API keys, no authentication.

Next steps

Section titled “Next steps”