Commitment
A commitment binds a record hash into the Merkle tree one level up - an item or entropy observation into its block, or a block into an epoch whose hash is recorded on Stellar or Bitcoin - and its inclusion_proof walks to that tree's merkle_root; no commitment is signed.
Overview
In Truestamp a commitment binds a record hash, its subject, into the Merkle tree one level up: an item’s item_hash or an entropy observation’s observation_hash into its block’s tree, or a block’s block_hash into the tree of an epoch whose epoch hash Truestamp recorded on Stellar or Bitcoin. Each commitment holds an inclusion proof, inclusion_proof, that walks the subject’s hash to that tree’s merkle_root; there is one kind of commitment, used at both levels, and commitments are immutable and not signed. Item Commitment means an item’s commitment into its block exists, and Block Commitment means a block’s commitment into an epoch exists; the epoch’s write of its hash to a chain is not itself a commitment, and a block’s commitment is written once the chain holds that write. A proof carries the subject’s commitment as the subject’s inclusion_proof and the block’s as the entries of commitments, keyed by chain, and a proof is generated only once its block has a final commitment on at least one chain. The two levels are explained in Item Commitment vs Block Commitment, and the order in which they happen in the proof lifecycle.