Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: proof
18
Glossary
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.
Inclusion proof
The RFC 9162 proof that one leaf belongs to a Merkle tree, the object {leaf_index, path, tree_size} with at most 32 path hashes; a Truestamp proof walks one from the subject's hash to its block's merkle_root and one per commitment from the block hash to its epoch's merkle_root.
Offline verification
A verification run that reads nothing outside the proof - every recomputation, link, key binding and signature check runs, but no chain or source is read, so each such row is skipped as offline, no window edge is drawn, and a sound Truestamp proof is internally-consistent, never verified.
Proof bundle
The self-contained, signed JSON file Truestamp serves for a committed subject - the subject and its record, its block, the block's commitments to Stellar or Bitcoin with their epochs, an item's witnesses and one Ed25519 signature, each declared hash beside its record.
Provenance
The third pillar of Truestamp's product framing - the traceable history of data as a hash-linked, 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 public records the item's fingerprint commits to and before its block was committed to a public chain, always phrased as submitted and submission window, never created or creation time.
t type code
Truestamp proofs carry no integer t type code; a proof names its subject in its type member (block, beacon, item, entropy_nist, entropy_stellar or entropy_bitcoin), and the proof's signature covers that member through the proof hash (0x50).
Timestamp
What a Truestamp timestamp is - a cryptographic submission window proving data was submitted after the public records it names and before its block's commitment on a public chain, immutable and independently verifiable, never a creation-time claim; the first of the home page's three pillars.
Witness
A record that already existed when an item was submitted and that its item hash commits to - the head block plus each source's newest captured entropy; the entropy witnesses open the submitted-after edge of the submission window, and the head block only fixes the item's place in the ledger.
Product
Submission Window
The submission window is the time guarantee of a Truestamp proof, that data was submitted after public records it witnesses and before a public chain recorded its block's epoch hash, each edge drawn by a verifier from public reads, which is why we say submitted rather than created.
What Truestamp Does Not Prove
The 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 signed proof of the exact bytes and of a provable submission window, which anyone can check against public chains and sources without trusting Truestamp.
What Truestamp Proves
The affirmative guarantees of a Truestamp proof, that the exact bytes existed unchanged and that submission fell inside a submission window a verifier draws from public records the proof names and from the public chain that holds its block's epoch hash, every hash it compares recomputed.
Verification
Proof Bundle Wire Format
The JSON format of a Truestamp proof - the signed envelope, the proof's members by type, block and epoch nodes, subjects, witnesses and beacon observations, commitments keyed by chain, the signing key event, constructions modes, the environment marker, value classes and size limits.
Proof Claims by Availability
Claims matrix for a Truestamp item proof - which of eight claims (bytes existed, unchanged, both submission-window edges, signature, key binding, ledger position, entropy freshness) hold from the proof alone, from chain or source reads, from a keyring, from Truestamp's records, or never.
The Proof Lifecycle
How a Truestamp proof comes to exist and strengthens over time as an item is submitted against a set of witnesses, committed into a block via item commitment, and that block is committed to Stellar and Bitcoin via block commitment, through an epoch whose hash goes on chain.
Verify a Proof
How to verify a Truestamp proof on the web, the APIs or the CLI - the fifteen steps of the specification, from the envelope, key binding and signature through every recomputation, the chain and entropy reads and the submission window, to the expected hash, the report rows, codes and labels.