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.

Byte prefix

The reserved single byte prepended to data before SHA-256 hashing for domain separation; every hashed object kind in Truestamp has its own registered prefix (0x00 Merkle leaf, 0x01 internal node, 0x11 item claims, 0x61 proof signing payload), enumerated in the byte-prefix registry.

Overview

A byte prefix is a single reserved byte that Truestamp places in front of data before hashing it with SHA-256, so the preimage is always prefix_byte || data. Each kind of hashed object has its own registered prefix value: 0x00 for a Merkle leaf, 0x01 for a Merkle internal node, 0x11 for item claims, 0x61 for the proof signing payload, among others. The prefix is what implements domain separation: the same bytes hashed under two different prefixes produce two unrelated fingerprints. The complete table of reserved prefixes is a long-lived contract, and a prefix, once assigned, is never reused for a different purpose. A verifier reproducing any Truestamp hash must take the prefix from the byte-prefix registry; the mechanism itself is explained 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]