Knowledge Base

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

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.

Overview

The claims hash is the SHA-256 hash of exactly what you submitted: your claims map is put into canonical byte form with JCS and hashed under the claims byte prefix 0x10: SHA-256 over 0x10 followed by the canonical bytes, which an item returns as claims_jcs beside its claims_hash. Nothing Truestamp generates is mixed into it, so anyone holding a copy of the claims can recompute the hash and compare, without trusting Truestamp. In prose Truestamp calls it the claims fingerprint. It is a member of the item’s record, with the item’s id and its witness hashes, and the item hash over that record is what enters the Merkle tree. The prefix mechanics are covered in domain-separated hashing.

An item’s proof bundle carries the claims themselves and, in the item’s record, the claims_hash. A verifier canonicalizes the claims the proof holds, hashes them under 0x10 and compares the result with the carried value, and builds the item hash from the record with the value it recomputed, so the claims hash is never taken on trust.