Knowledge Base

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

Tagged: verification

24
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. 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 fully offline without an account, signing in through the browser as a pre-registered OAuth 2.1 PKCE client. 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. Offline verification Checking a Truestamp proof bundle using only its own contents with no call to any Truestamp server, by recomputing domain-separated hashes, walking the Merkle inclusion and epoch proofs, and verifying the Ed25519 signature; on-chain confirmation is the only optional network step. Proof bundle The self-contained JSON or CBOR file downloaded for a committed subject, carrying the subject data and its metadata, Merkle proofs, an Ed25519 signature, the witness detail that opens the submitted-after edge, and at least one public-blockchain commitment, every hash recomputed from carried bytes. Provenance The third pillar of Truestamp's product framing - the traceable origin and history of data as a signed, 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. t type code The frozen integer discriminator of a proof subject type, drawn from a registry namespaced by decade (10-19 block-like, 20-29 item, 30-39 entropy, 40-49 reserved for commitment chains); a bundle carries the matching registry name in its type key while the integer is what the signed payload binds. Verification level One of the two independent checks on an entropy observation - internal verification recomputes the stored hash and Ed25519 signature offline, external verification re-fetches the value from the original public source, and the merged summary adds the Merkle inclusion check. Verification summary The combined pass/fail report over every verification layer of an entropy observation (data hash, Ed25519 signature, 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. Witness A public record that already existed when a subject was submitted and that the subject's composite fingerprint commits to, opening the submitted-after edge of the submission window; the registry is the head block plus one entry per captured entropy source, plus the signing-key event.