Support

We're here to help you get the most out of Truestamp. Find answers to common questions or get in touch with our support team.

Community & Updates

Share feedback, follow what we're building next, and see what just shipped. Each opens right here in a popup, so no separate account is needed.

Knowledge Base

Browse the concepts behind Truestamp. Pick a domain to explore, follow the links between concepts, or search across everything.

Improving the Efficiency and Reliability of Digital Time-Stamping

Bayer, Haber, and Stornetta 1993 paper introducing hash trees (Merkle trees) to batch digital time-stamp requests, reducing storage and verification cost and enabling time-stamp renewal to extend signature lifetimes.

Open resource

Overview

“Improving the Efficiency and Reliability of Digital Time-Stamping” is a 1993 research paper by Dave Bayer, Stuart A. Haber, and W. Scott Stornetta. It extends the authors’ earlier digital time-stamping work by introducing binary hash trees (Merkle trees) as the core data structure for batching many time-stamp requests together. The paper argues that trustworthy chronological ordering of digital documents must rest on “digital causality” (one-way hash dependencies) rather than the physical properties of paper. Its two central contributions are a tree-based batching scheme that sharply cuts storage and verification cost, and a renewal technique that extends the practical lifetime of time-stamps and the digital signatures they protect.

Key points

  • Many time-stamp requests submitted in one round are combined into the leaves of a binary hash tree; the single root hash value can be widely witnessed (for example, published in a newspaper), so a large batch of documents shares one broadly public certifying value.
  • Because assurance flows through the tree root, each widely-published value certifies an exponentially larger number of documents, giving greater public confidence per time-stamping event while reducing the storage and computation needed to verify any one document.
  • Verification of a single document requires only the sibling hashes along its path to the root (a logarithmic-size witness), not the entire batch, making proofs compact and independent of the number of co-timestamped documents.
  • Time-stamps can be renewed: before a hash function or signature scheme weakens, a document together with its existing time-stamp certificate is re-timestamped under a newer, stronger hash, preserving the original date even after the old cryptographic primitive is compromised.
  • This renewal mechanism extends the useful lifespan of digital signatures and other cryptographic security tools beyond the point at which their underlying algorithms would otherwise be considered broken.
  • The scheme builds directly on Haber and Stornetta’s 1991 linking-based time-stamping work, replacing or augmenting per-request linking with an efficient tree structure.

Relevance to Truestamp

This paper is a foundational precursor to Truestamp’s architecture: batching submissions into a hash tree and proving membership via a compact root-path witness is exactly the Merkle-tree model Truestamp uses for inclusion proofs and for its submission window guarantees. Its emphasis on one-way hash dependencies as the basis of verifiable ordering underlies Truestamp’s proof-of-existence design, and its renewal idea foreshadows strategies for keeping proofs verifiable as cryptographic primitives age.

Citations

  1. Improving the Efficiency and Reliability of Digital Time-Stamping. Dave Bayer, Stuart A. Haber, and W. Scott Stornetta, in Sequences II: Methods in Communication, Security, and Computer Science, pp. 329-334 (eds. Capocelli, De Santis, Vaccaro), Springer-Verlag, New York, 1993.
  2. Improving the Efficiency and Reliability of Digital Time-Stamping (ResearchGate copy). The same paper; this is the copy cited in the Truestamp whitepaper.

Get Help

API Documentation

Comprehensive guides for the REST and GraphQL APIs, including interactive documentation and code examples.

View API Docs

FAQ

Quick answers to the most commonly asked questions about timestamping and verification.

Browse FAQ

Email Support

Send us a message and our team will respond within 24 hours.

[email protected]

Security Issues

Report security vulnerabilities through our responsible disclosure program.

[email protected]