Epoch hash
The hash Truestamp writes on a public chain for each epoch - SHA-256 under prefix 0x40 of the epoch record {leaf_count, merkle_root} over the epoch's block hashes - as a Stellar hash memo or a Bitcoin OP_RETURN output; a proof carries it in each commitment entry's epoch.
Overview
The epoch hash is the one value Truestamp writes on a public chain for an epoch: SHA-256(0x40 || JCS(record)), under the byte prefix 0x40, over the epoch record of exactly two members, leaf_count, the number of block hashes in the epoch’s Merkle tree, and merkle_root, that tree’s Merkle root. Hashing the record rather than writing the bare root makes the chain’s copy fix the tree’s size with its root, so an inclusion proof cannot claim a different size for the same tree. On Stellar the epoch hash is a transaction’s hash memo; on Bitcoin it is the 32 bytes of the one output whose script is exactly 0x6a 0x20 followed by them. Epochs are not signed: the chain’s copy is what a verifier compares with. In a proof bundle each commitment entry carries its epoch as {epoch_hash, record}, and a verifier recomputes the hash from the record and compares it with epoch_hash and, wherever it holds the chain’s copy, with that copy. When a verifier holds that copy, and how the entry’s inclusion proof walks into the record, are in verify a proof and the proof bundle wire format, and the batching in the epoch and Block Commitment.