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.

Claims hash

The claims fingerprint, a SHA-256 hash, under the item-claims byte prefix 0x11, of the JCS-canonicalized claims a user submitted and nothing else; independently reproducible by anyone holding the claims, and one of the two inputs bound into the item's composite fingerprint.

Overview

The claims hash is the SHA-256 hash of exactly what you submitted: your claims map is put into canonical byte form with JCS and hashed under the item-claims byte prefix 0x11. Nothing Truestamp generates is mixed into it, so anyone holding a copy of the claims can recompute the hash and compare, without trusting Truestamp. In prose Truestamp calls it the claims fingerprint. It is one of the two independent fingerprints described in the item’s composite fingerprint: the claims hash and the metadata hash are both inputs to the item hash that enters the Merkle tree. The prefix mechanics are covered in domain-separated hashing.

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]