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.
Overview
The item hash is the hash of the item’s record: SHA-256 over the byte prefix 0x11 followed by the JCS form of the item record, an object of exactly three members:
claims_hash, the item’s claims hash;id, the item’s identifier, a UUIDv7;witness_hashes, a map naming the item’s witnesses:block, the hash of the block at the head of Truestamp’s chain at submission, and, for each entropy source whose newest captured observation could be read, that observation’s entropy hash.
It is the value that becomes a Merkle leaf in a Truestamp block at Item Commitment, and its leftmost 75 bits give the item its item code. Items are not signed: a block’s signature covers the Merkle root its items’ hashes enter, and a proof’s signature covers the whole proof. Who authored or currently owns the item is deliberately excluded, so ownership can change hands without invalidating any proof. See Truestamp’s Merkle tree for how that leaf enters the tree.
Binding the witness hashes is what pulls the item’s witnesses into the item hash: they name the public records the item was submitted after, so fixing the item hash fixes that choice of witnesses permanently.
An item’s proof bundle carries the item hash as subject.item_hash, beside the record it is the hash of, the claims and the witness records the record names. A verifier recomputes the claims hash from the claims, then the item hash from the record, compares each with the carried value, checks each witness against its entry in witness_hashes, and walks the recomputed item hash into the block, so no hash is accepted on trust.