Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: domain-separation
7
Cryptography
Byte-Prefix Registry
The complete lookup table of every single-byte SHA-256 domain-separation prefix Truestamp uses, the thirteen kinds of SPEC.md 4.3, mapping each byte to what it hashes and whether it is signed, so a verifier can reproduce any hash exactly.
Domain-Separated Hashing (SHA-256 Byte Prefixes)
How Truestamp separates SHA-256 hash contexts with single-byte domain prefixes, keeping leaf hashes, node hashes, and each kind of hashed object in distinct hash spaces to prevent ambiguity and second-preimage confusion.
Glossary
Byte prefix
The single byte placed before data when Truestamp hashes it with SHA-256 for domain separation; thirteen are assigned, one per construction, from 0x00 and 0x01 for Merkle leaves and nodes through 0x10 claims, 0x31 blocks, 0x40 epochs and 0x50 proofs to the 0x6_ key bytes.
Domain separation
Truestamp's rule that every record hash, and the Merkle leaf and node, is SHA-256 computed over a reserved single-byte prefix plus the data, so a hash made for one purpose (Merkle leaf, node, item claims, proof hash) can never collide with or be replayed as a hash for another purpose.
Merkle leaf
The bottom-level entry of a Merkle tree, hashed as SHA-256(0x00 || hash) under the reserved leaf prefix so it can never be confused with an interior node (prefix 0x01); block-tree leaves are item and entropy observation hashes, epoch-tree leaves are block hashes.
RFC 6962
The Certificate Transparency standard Truestamp takes its Merkle hash primitives from - SHA-256 with 0x00 leaf and 0x01 node domain-separation prefixes, and the empty-tree root - and its tree shape, which Truestamp builds over leaves it sorts by key.