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.
Tagged: hashing
21
Library
An Introduction to Merkle Patricia Trie
LambdaClass blog primer on the Merkle Patricia Trie (MPT), the authenticated key-value structure behind Ethereum state: tries, Patricia path compression, Keccak hashing, node types, StateRoot, and proof construction.
Bitcoin: A Peer-to-Peer Electronic Cash System
Satoshi Nakamoto's 2008 Bitcoin whitepaper: a trustless peer-to-peer cash system using a proof-of-work timestamp server, hash-chained blocks, and Merkle trees to prevent double-spending.
Blockchain vs Traditional Timestamping Methods (ScoreDetect Blog)
ScoreDetect blog article contrasting blockchain timestamping with traditional TSA/RFC 3161 timestamping across security, speed, scalability, cost, immutability, transparency, Merkle-tree batching, hybrid systems, and legal admissibility.
Comprehensive Guide to Merkle Trees, Merkle Proofs, and Merkle Roots
Cyfrin developer primer defining Merkle trees, proofs, and roots, how pair-wise hashing builds a root, how inclusion proofs verify membership, the second preimage attack, and blockchain uses.
Design of a Secure Timestamping Service with Minimal Trust Requirement
1999 UCL Crypto Group paper (Massias, Serret Avila, Quisquater) on the Belgian TIMESEC timestamping service: round-based Merkle trees, hash-linked round values, and newspaper publication to minimize trust in the authority.
How The Bitcoin Blockchain Is Fighting Fraud In Guatemala's Presidential Elections
Bitcoin Magazine feature on Simple Proof, which used OpenTimestamps and the Bitcoin blockchain to timestamp Guatemala's 2023 election tally sheets, creating tamper-evident proof-of-existence records citizens could independently verify.
How to Time-Stamp a Digital Document
Haber and Stornetta's 1991 Journal of Cryptology paper founding cryptographic digital timestamping via hashing, digital signatures, hash-linking chains, and distributed-trust witnessing.
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.
Linked Timestamping (Wikipedia)
Wikipedia overview of linked timestamping: hash chains and Merkle trees that link time-stamps into a tamper-evident order, avoiding private keys, with history, standards, and blockchain publication.
Merkle tree - Wikipedia
Wikipedia's reference article on Merkle (hash) trees: leaf and parent hashing, the root hash, logarithmic inclusion verification, Ralph Merkle's 1979 patent, the second-preimage attack, and uses in Bitcoin, Git, ZFS, and Certificate Transparency.
Merkle Trees in Git and Bitcoin
Initial Commit blog article explaining how Git and Bitcoin both use Merkle trees and content-addressable hashing to build tamper-evident, verifiable distributed data structures.
Ralph Merkle - Wikipedia
Wikipedia biography of Ralph Merkle, co-inventor of public-key cryptography, inventor of Merkle trees and cryptographic hashing, and researcher in nanotechnology and cryonics.
RFC 6962: Certificate Transparency
IETF Experimental RFC defining Certificate Transparency: publicly auditable append-only Merkle Hash Tree logs of TLS certificates, with SHA-256 leaf/node domain separation, inclusion and consistency proofs, SCTs, and Signed Tree Heads.
RFC 8785: JSON Canonicalization Scheme (JCS)
RFC 8785 defines the JSON Canonicalization Scheme (JCS), a deterministic serialization of I-JSON data for reliable hashing and signing, using ECMAScript number formatting, UTF-16 property sorting, and UTF-8 output.
Secure Hash Standard (SHS)
FIPS PUB 180-4, the NIST Secure Hash Standard specifying SHA-1 and the SHA-2 family (SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256) message-digest algorithms.
Some Aspects of Merkle Tree - DEV Community
Sergey Shandar's developer article on Merkle tree implementation pitfalls: second preimage and length extension attacks, distinguishing data from branch nodes, and hash alignment limits in content-addressable networks.
Stuart Haber - Wikipedia
Wikipedia biography of cryptographer Stuart Haber, co-author of the 1991 linked digital time-stamping work with Scott Stornetta, cited in the Bitcoin whitepaper and foundational to blockchain.
The First Blockchain or How to Time-Stamp a Digital Document
Decentralized Thoughts article by Ittai Abraham on the 1991 Haber-Stornetta digital timestamping scheme: hash chaining, Merkle trees, trusted repositories, and its influence on Bitcoin.
Using Merkle Trees to Efficiently Detect Data Changes
JavaScript Development Substack tutorial on Merkle (hash) trees: bottom-up SHA-256 construction, root-hash summaries, logarithmic change detection, and use in blockchain, P2P, and cloud sync.
Why and how Bitcoin uses Merkle trees - Applied Mathematics Consulting
John D. Cook blog post explaining how Bitcoin organizes block transactions into a Merkle tree, storing only the root in the block header to enable logarithmic-size Simple Payment Verification proofs.
Why do cryptocurrencies use Merkle trees instead of hashing all the data in the block in one go?
Reddit r/cryptography discussion explaining why blockchains use Merkle trees rather than a single block-wide hash: inclusion proofs, SPV light-client verification, partial verification without full data, and second preimage concerns.
Get Help
API Documentation
Comprehensive guides for the REST and GraphQL APIs, including interactive documentation and code examples.
View API DocsFAQ
Quick answers to the most commonly asked questions about timestamping and verification.
Browse FAQSecurity Issues
Report security vulnerabilities through our responsible disclosure program.
[email protected]