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.

Committed

The normal resting state on both Truestamp ledgers - an item is committed once its item hash is a leaf in a finalized block (Item Commitment), and a block is committed once its block hash is covered by an epoch recorded on a public blockchain (Block Commitment).

Overview

Committed is the normal resting state on both of Truestamp’s ledgers, with two related meanings. An item becomes committed when its item hash is included as a Merkle-tree leaf in a finalized block; this is Item Commitment, and from that point the item is verifiable. A block is created finalized and becomes committed when its block hash is covered by an epoch whose Merkle root is recorded on a public blockchain; this is Block Commitment. The two events are distinct and a complete proof depends on both: a downloadable proof for an item is only issued once its covering block has at least one public-blockchain commitment. The distinction is explained in Item Commitment vs Block Commitment and the batching in the epoch concept.

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]