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: proof
19
Glossary
CBOR
Concise Binary Object Representation (RFC 8949), the compact binary encoding of a Truestamp proof bundle, interchangeable with the JSON form, wrapped in the self-describing tag 55799, carrying hash and key fields as raw byte strings instead of hex or base64 text.
Compact proof encoding
The binary wire form of a Merkle inclusion proof used in proof bundle ip and ep fields, packing a depth byte, a left/right direction bitfield, and raw 32-byte sibling hashes into unpadded base64url, mapping losslessly to and from the JSON direction:hash form.
Data integrity
The affirmative guarantee that the exact bytes submitted to Truestamp remain unchanged - any alteration changes the data's SHA-256 fingerprint and breaks the proof, so a verifier who re-hashes the data detects even a single changed byte; one of the three product pillars.
External Commitment
Truestamp's permanent per-block, per-chain record that a block was committed to a public blockchain, carrying the Merkle proof from block_hash to the on-chain epoch root; appears in a proof bundle as a cx entry (type 40 Stellar, 41 Bitcoin), and every bundle carries at least one.
Inclusion proof
A short list of about log2(N) sibling hashes, also called an audit proof, proving one Merkle leaf belongs to a tree with a given root without revealing other leaves; a Truestamp proof bundle uses one subject-into-block (ip) and one block-into-epoch (ep) per commitment.
Offline verification
Checking a Truestamp proof bundle using only its own contents with no call to any Truestamp server, by recomputing domain-separated hashes, walking the Merkle inclusion and epoch proofs, and verifying the Ed25519 signature; on-chain confirmation is the only optional network step.
Proof bundle
The single self-contained JSON or CBOR file downloaded for a committed subject, carrying subject data, hashes, Merkle proofs, an Ed25519 signature, and at least one public-blockchain commitment so anyone can verify it offline, discriminated by an integer top-level t type code.
Provenance
The third pillar of Truestamp's product framing - the traceable origin and history of data as a signed, publicly verifiable chain of evidence from submission through block inclusion to public-blockchain commitment, deliberately bounded to make no claim about who authored the content.
Submission window
Truestamp's honest time guarantee - the cryptographic proof that data was submitted after the most recent internal block at submission and before the finalized block that includes it, always phrased as submitted and submission window, never created or creation time.
t type code
The integer discriminator at the top of every proof bundle and inside each cx entry, drawn from a frozen registry namespaced by decade (10-19 block-like, 20-29 item, 30-39 entropy, 40-49 commitment chains); never renumbered or reused, and bound into the signed payload.
Timestamp
What a Truestamp timestamp is - a cryptographic submission window proving data was submitted after one block and before the finalized block that includes it, immutable and independently verifiable, never a creation-time claim; the first of the home page's three pillars.
Product
Submission Window
The submission window is Truestamp's honest time guarantee, the cryptographic proof that data was submitted after one public block and before the block that includes it, which is why we say submitted and submission window rather than created or creation time.
What Truestamp Does Not Prove
The honest limits of a Truestamp proof - it attests submission timing and data integrity but not creation time, not authorship or ownership, not the truthfulness of the content, and not that data existed before it was submitted.
What Truestamp Is
Plain-language overview of Truestamp, the data-integrity and timestamping service that turns submitted data into a portable cryptographic proof that the data was submitted within a proven time window, independently verifiable by anyone without trusting or contacting Truestamp.
What Truestamp Proves
The affirmative guarantees of a Truestamp proof - data existence and integrity that the exact bytes existed unchanged, submission within a time window bracketed by public-blockchain commitments, and independent offline verification against Stellar and Bitcoin without trusting Truestamp.
Verification
Proof Bundle Wire Format
The self-describing JSON and CBOR wire format of a Truestamp proof bundle, its integer top-level t type code (block/beacon/item/entropy plus Stellar/Bitcoin commitment codes), the fixed-width Ed25519 signature payload layout, and how the bundle is verifiable offline.
The Proof Lifecycle
How a Truestamp proof comes to exist and strengthens over time as an item is submitted, committed into a block via item commitment, and that block is committed to Stellar and Bitcoin via block commitment.
Verify a Proof
Step-by-step guide to verifying a Truestamp proof bundle offline by recomputing the leaf hash with domain separation, walking the Merkle inclusion path to the block root, and confirming that root against the public Stellar or Bitcoin commitment, via the verify web page, JSON:API, or GraphQL.
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]