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.

Commitment

Truestamp's term for recording a hash somewhere durable and checkable: Item Commitment places an item's hash in a finalized block's Merkle tree, Block Commitment records an epoch root of batched block hashes on a public blockchain, and a complete proof requires both events.

Overview

In Truestamp, a commitment is the act of recording a hash in a durable place where it can later be checked independently. The word covers two distinct, load-bearing events, and a complete proof needs both: Item Commitment, where an item’s hash becomes a leaf in the Merkle tree of a finalized Truestamp block, and Block Commitment, where a batch of block hashes is Merkle-rooted into an epoch whose single root is recorded on a public blockchain such as Stellar or Bitcoin. The first event ties an item to Truestamp’s internal ledger; the second ties that ledger to an independent external witness. The distinction is explained in depth in Item Commitment vs Block Commitment, and the sequence in which the two events happen and strengthen a proof is walked through in the proof lifecycle.

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]