Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: submission-window
16
Glossary
Chronolocation
The investigative practice of establishing when digital evidence such as a photo existed or was captured - Truestamp supports it by proving a submission window, giving evidence a verifiable existed-by guarantee while never claiming creation time.
Creation time
The moment content was originally authored, which a Truestamp proof deliberately does not attest - a proof pins data to the window in which it was submitted, and data can exist long before it is submitted, so the guarantee is always a submission window, never a creation time.
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.
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.
Items
Item Lifecycle
The states a Truestamp item moves through from created to committed, plus the terminal redacted and deletion states, what each means to a user, how an item advances to committed, and how ownership governs who can act at each stage.
Submit an Item
How to timestamp data by submitting an item on the web form, JSON:API, GraphQL, console WebSocket, CLI, or an MCP agent, with every claims field (name, hash and hash type, description, URL, location, timestamp, metadata), hash mode versus plan-gated claims-only mode, and the limits that apply.
The Item Record and Its Hash
How an item's claims fingerprint, its id and its witness hashes are bound into one item record whose hash (item_hash) is the Merkle leaf, keeping user data independently verifiable, committing the witnesses of the submitted-after edge, and excluding authorship from every hash.
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 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.