Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: item
24
Glossary
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.
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).
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).
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.
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.
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.
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.
Item Ownership vs Authorship
The Item split between immutable authorship (audit-only creator record excluded from every hash, with one exception when the author's account is deleted) and transferable ownership (the user or team rights holder driving all rights-based decisions), plus the creator-retains vs team-retains model.
Item Visibility
The three item visibility levels (private, team, public), who can read an item at each level, how public items are discovered through anonymous search and the public verification page, who can set and change visibility, and why visibility changes never affect an item's hashes or proof.
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 Code
The item code, a 16-character Crockford base32 short name for an item (the leftmost 75 bits of its item_hash and a check symbol), how to check it from a proof, how Truestamp issues, shows and accepts it, how a typed code is read, and what a matching code does not prove.
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.