Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Items
item lifecycle, ownership vs authorship, the item record and its hash.
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.