Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

Glossary

terminology of Truestamp, one definition per term, cross-linked to the concepts that explain each in depth.

AI chat assistant The in-app slide-out AI chat sidebar that answers questions about Truestamp and, for signed-in users, their own items and teams through a read-only actor-scoped toolset, also available to anonymous guests with a smaller toolset and tighter limits when anonymous chat is enabled. API key A long-lived opaque credential (prefix truestamp_) that authenticates programmatic requests as your whole account, sent as an Authorization Bearer header on JSON:API and GraphQL or as a connection parameter on the console WebSocket; the MCP surface never accepts one and requires OAuth 2.1. Audit path The path member of a Merkle inclusion proof, RFC 6962's audit path and RFC 9162's inclusion path - the sibling hashes from a leaf up to the root, each 64 lowercase hex and at most 32, with no side markers, since leaf_index and tree_size fix each sibling's side. Authorship The immutable audit-trail record of who submitted an item (its creator), set once at submission, never consulted for rights decisions, and deliberately excluded from every cryptographic hash, so a Truestamp proof makes no claim about who authored the underlying data. Beacon A public, verifiable snapshot of the Truestamp chain, the hash of a finalized or committed block published on the public /beacons page as verifiable randomness and a moment-in-time marker, with four fields (id, hash, timestamp, previous_hash) and a stable permalink per hash. Billing owner The user who created a team, whose plan plus any administrator overrides sets the effective limits and entitlements for all work done in that team, whichever teammate does it - including the pooled monthly item allowance and member limits counted across every team that person created. Bitcoin A public proof-of-work blockchain Truestamp uses two ways - new Bitcoin blocks are captured as entropy observations, and each Bitcoin epoch's epoch hash is written in an OP_RETURN output, which a proof carries as its commitments.bitcoin entry on mainnet, testnet or regtest. Block (Truestamp block) A unit of Truestamp's internal ledger, made at least once a minute while items or entropy observations wait: a Merkle tree over their hashes, hash-chained to the previous block and Ed25519-signed, created finalized and committed once its commitment into an epoch on a public chain exists. Block Commitment Block Commitment means a block's commitment exists: a commitment row binds its block_hash into the Merkle tree of an epoch whose epoch hash Truestamp recorded on Stellar (a hash memo) or Bitcoin (OP_RETURN); a block still finalized moves to committed in that write, at its first chain's commitment. Block hash The SHA-256 hash under prefix 0x31 of a Truestamp block's seven-member record (height, id, leaf_count, merkle_root, metadata, previous_block_hash, signing_key_id); it chains blocks, is signed, is a leaf of an epoch tree, is the beacon value, and names each item's block witness. Byte prefix The single byte placed before data when Truestamp hashes it with SHA-256 for domain separation; thirteen are assigned, one per construction, from 0x00 and 0x01 for Merkle leaves and nodes through 0x10 claims, 0x31 blocks, 0x40 epochs and 0x50 proofs to the 0x6_ key bytes. 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. Claims The user-supplied data map an item is made of - a required name plus optional external content hash and algorithm, description, URL, location, freeform metadata, user timestamp, and nonce, JCS-canonicalized so the claims hash stays independently reproducible by the submitter. Claims hash The claims fingerprint, a SHA-256 hash, under the claims byte prefix 0x10, of the JCS-canonicalized claims a user submitted and nothing else; independently reproducible by anyone holding the claims, and bound with the item's id and witness hashes into its item hash. Claims-only submission Submitting an item without an external hash, so the claims themselves are the content of record; needs a description of at least 32 code points or non-empty metadata, and the JCS claims less any nonce must fit the per-plan byte budget (256 B Free to 16 KB Enterprise). CLI (truestamp) The open-source truestamp command-line client, a single static binary for macOS, Linux, and Windows that submits items, downloads proof bundles, and verifies proofs without an account, online by default or offline on request, signing in through the browser as a pre-registered OAuth 2.1 PKCE client. Commitment A commitment binds a record hash into the Merkle tree one level up - an item or entropy observation into its block, or a block into an epoch whose hash is recorded on Stellar or Bitcoin - and its inclusion_proof walks to that tree's merkle_root; no commitment is signed. Committed The normal resting state on both Truestamp levels - an item is committed once its commitment into a finalized block's Merkle tree exists (Item Commitment), and a block once its commitment into an epoch whose hash is recorded on Stellar or Bitcoin exists (Block Commitment). Console (WebSocket) The authenticated multiplexed WebSocket surface at /console/websocket for real-time programmatic access, where clients subscribe to live streams, issue commands such as items.create and items.watch, and receive stream events under per-connection rate, stream, and payload limits. 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. 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. Domain separation Truestamp's rule that every record hash, and the Merkle leaf and node, is SHA-256 computed over a reserved single-byte prefix plus the data, so a hash made for one purpose (Merkle leaf, node, item claims, proof hash) can never collide with or be replayed as a hash for another purpose. Ed25519 signature The deterministic 64-byte signature scheme Truestamp signs three kinds with, each over the 32 bytes of a domain-separated record hash - a block record, a key handover and a proof; items, entropy observations, commitments and epochs are not signed. Entitlement A named Truestamp plan capability that cannot be reduced to a numeric limit, such as team-retained item ownership or the support level (community, email, priority); administrators can grant extra entitlements and limit overrides per account, and every check uses the effective values. Entropy observation A captured record of unpredictable public entropy from the NIST Randomness Beacon, the Stellar ledger, or the Bitcoin blockchain, hashed but not signed, folded directly as a Merkle leaf into a Truestamp block, and named as a witness by the items submitted after it. Entropy source One of the three independent public systems Truestamp captures unpredictable randomness from, the NIST Randomness Beacon, the Stellar ledger, and the Bitcoin blockchain, each yielding entropy observations with its own proof bundle subject type (entropy_nist, entropy_stellar, entropy_bitcoin). Epoch The batch Truestamp uses for Block Commitment: the blocks after a chain's last recorded epoch form one Merkle tree, and the hash of the epoch record {leaf_count, merkle_root} goes on Stellar or Bitcoin; each chain advances its own series of epochs, and epochs are not signed. Epoch hash The hash Truestamp writes on a public chain for each epoch - SHA-256 under prefix 0x40 of the epoch record {leaf_count, merkle_root} over the epoch's block hashes - as a Stellar hash memo or a Bitcoin OP_RETURN output; a proof carries it in each commitment entry's epoch. GraphQL Truestamp's authenticated GraphQL endpoint at /gql with an interactive playground at /gql/playground, accepting an API key or OAuth 2.1 bearer token, whose introspectable schema of queries and mutations is generated from the same resource domains as the JSON:API. 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. Item A single unit of data submitted to Truestamp for timestamping - named by its UUIDv7 id and its item code, fingerprinted by its item hash, belonging to exactly one team, with a transferable owner and an immutable creator, advancing through the created, processing, and committed states. Item code An item's short name - 16 uppercase Crockford base32 symbols, the leftmost 75 bits of its item_hash and one check symbol - shown beside the item and accepted in links; anyone can recompute it from a proof, but it is a name, never a proof or a verdict. Item Commitment Item Commitment means an item's commitment exists: a commitment row binds its item_hash into the Merkle tree of a finalized block, holding the inclusion proof to that block's merkle_root, and the item moves from processing to committed in the same write. Item hash The hash of an item's record, SHA-256 under prefix 0x11 over the JCS of {claims_hash, id, witness_hashes}; it is the item's Merkle-tree leaf in a Truestamp block, gives the item its item code, is not signed, and leaves out authorship and ownership. Item retention The per-plan window a Truestamp item is kept - 90 days on the Free tier (expired items enter the deleted_expired state with an email warning and a 7-day cancellable grace period), unlimited on paid tiers; team-owned items follow the team billing owner's plan. Item states The lifecycle states of a Truestamp item - created (waiting), processing (in a finalized block, its commitment being written), committed (its commitment into the block exists), redacted, plus the deletion states deleted_user and deleted_expired (7-day cancellable grace). Item visibility The per-item read scope - private (default; only the item's user-owner plus the owning team's admins and owners), team (any member of the owning team), or public (readable by anyone, including anonymous visitors); visibility controls who can read an item, ownership controls who can change it. JCS (JSON Canonicalization Scheme) RFC 8785, the deterministic JSON serialization Truestamp applies to a JSON map (claims, the item, entropy, observation, block, epoch, handover and proof records, and the genesis object) before SHA-256 hashing, so the same data always yields the same bytes and hash, whatever its key order. JSON:API Truestamp's authenticated REST surface at /api/json following the JSON:API specification, with API-key or OAuth 2.1 bearer authentication, an OpenAPI spec rendered by Swagger UI and ReDoc, and resource endpoints with standard filtering, sorting, and pagination. Magic link A single-use, time-limited sign-in link Truestamp emails to your address as a passwordless alternative to password sign-in; if no account exists for that email one is created on the spot, and an enabled TOTP second factor still applies after the link signs you in. MCP (Model Context Protocol) The Model Context Protocol, which connects an LLM agent (Claude Code, IDE agents, Claude Desktop) to a Truestamp account at /mcp, a three-tool code-mode surface authenticated exclusively by OAuth 2.1 with an mcp:read/mcp:write scope split and a preview-then-submit write flow. Merkle leaf The bottom-level entry of a Merkle tree, hashed as SHA-256(0x00 || hash) under the reserved leaf prefix so it can never be confused with an interior node (prefix 0x01); block-tree leaves are item and entropy observation hashes, epoch-tree leaves are block hashes. Merkle root The single hash at the top of a Merkle tree that commits to every leaf below it; a block record's merkle_root commits to that block's items and entropy observations, and an epoch record's merkle_root and leaf_count hash to the epoch hash recorded on chain. Merkle tree A binary hash tree where each parent is the SHA-256 hash of its two children, reducing a whole set of leaves to one root; Truestamp builds these trees over item and entropy observation hashes per block and over block hashes per epoch. NIST Randomness Beacon The US National Institute of Standards and Technology public randomness service publishing cryptographically signed random pulses about once a minute in a tamper-evident chain, one of Truestamp's three entropy sources, captured by HTTP polling and re-verifiable by chain and pulse index. OAuth 2.1 Truestamp's built-in authorization server (authorize, token, register, revoke endpoints with RFC 8414/9728 discovery) issuing audience-bound access tokens and rotating refresh tokens via PKCE S256 consent, with per-surface mcp/api/console read and write scopes; the only credential MCP accepts. 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. Ownership The transferable rights holder of a Truestamp item, either a single user or a team, that every rights decision (read, update, redact, restore, delete, reassign) is authorized against; ownership can change hands without altering any hash, so an existing proof stays valid across transfers. Ownership model The per-team setting choosing who owns newly submitted items - creator retains (the default; the submitting user owns their items) or team retains (the team owns them; plan-gated, requires each invitee's acknowledgment of ownership terms, and blocks plan downgrades while in effect). Passkey A phishing-resistant WebAuthn sign-in credential on a Truestamp account, approved with Touch ID, Face ID, Windows Hello, or a security key, completing sign-in in one usernameless step that skips the TOTP prompt; added, renamed, and removed from the profile page. Plan The account-level tier (Free, Starter, Pro, Enterprise) setting numeric limits (items per month, teams owned, members per team, metadata size, claims-only budget, webhooks, retention, daily chat messages and knowledge-base searches) and named entitlements; the billing owner's plan governs the team. 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. Public randomness beacon A service that periodically publishes unpredictable, publicly verifiable random values, ideally ones no one can bias; Truestamp consumes external beacons such as the NIST Randomness Beacon as entropy and publishes its own on /beacons, which no one can predict but Truestamp could bias. Recovery code A single-use backup code issued in a batch when Truestamp two-factor authentication is enrolled, entered in place of a TOTP code at the second-factor step; each code works exactly once, only a hashed form is stored, and regenerating a batch invalidates the previous one. Redaction Removing a committed item's claims and tags while preserving every hash (claims hash, witness hashes, item hash) and the item code, so the inclusion proof stays valid - restoring requires claims that hash to the preserved claims hash, and only a system administrator undoes a compliance redaction. RFC 6962 The Certificate Transparency standard Truestamp takes its Merkle hash primitives from - SHA-256 with 0x00 leaf and 0x01 node domain-separation prefixes, and the empty-tree root - and its tree shape, which Truestamp builds over leaves it sorts by key. Signing-key ID The 4-byte id of an Ed25519 signing key, SHA-256 under prefix 0x60 over the 32 key bytes cut to 4 bytes and written as 8 lowercase hex; a block record holds it as signing_key_id and key events and the keyring as key_id, but no proof carries a kid, and it never selects the signer. Stellar A public blockchain Truestamp uses two ways: closed Stellar ledgers are captured as entropy observations, and each Stellar epoch's epoch hash is a transaction's hash memo, which a proof carries as its commitments.stellar entry on the public or testnet network. 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). Team The unit of tenancy in Truestamp - every item belongs to exactly one team, every signed-in request is evaluated against your identity plus one active team, and team membership is what grants any visibility into a team's items and members. Team role The single role each Truestamp team membership carries, in a strict privilege hierarchy - team owner (full control), team admin (team settings plus member and viewer memberships), team member (submits and works with items), team viewer (read-only); roles govern actions, plans govern features. 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. TOTP Time-based One-Time Password, the optional authenticator-app second factor on a Truestamp account; after a password or magic-link sign-in you enter the app's rotating six-digit code, with code entry rate-limited to 3 attempts per 5-minute window against brute-force guessing. UUIDv7 The time-ordered UUID version (RFC 9562) of Truestamp's record ids, items, blocks, teams and users among them, with four exceptions such as an API key's random UUIDv4; its leading 48-bit millisecond time sorts values by generation time. Verification level One of the two independent checks on an entropy observation - internal verification recomputes its entropy hash and observation hash offline, external verification re-fetches the value from its public source, and the summary adds the Merkle check. Verification summary The combined pass/fail report over every verification layer of an entropy observation (entropy hash, observation hash, Merkle inclusion, external source); it passes only when no individual check fails and marks the Merkle step skipped, not failed, until the observation is committed. Webhook (outgoing) An HTTPS endpoint registered with Truestamp to receive outgoing item event callbacks, managed over the JSON:API and GraphQL surfaces, with optional bearer-token authentication, delivery tracking, private-IP SSRF safeguards, no HMAC payload signing, and a per-plan endpoint limit. 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.