Block Commitment
Block Commitment means a block's commitment exists: a commitment row binds its block_hash into the Merkle tree of an epoch whose epoch hash Truestamp recorded on Stellar (a hash memo) or Bitcoin (OP_RETURN); a block still finalized moves to committed in that write, at its first chain's commitment.
Overview
Block Commitment means a block’s own commitment exists, the upper of the two Merkle levels a commitment binds. For each chain, Truestamp batches the hashes of the blocks after that chain’s last recorded epoch into a new epoch, builds one Merkle tree over them, and writes the epoch’s epoch hash, the hash under 0x40 of its record {leaf_count, merkle_root}, to a public chain: as a Stellar transaction’s hash memo, or as a Bitcoin output whose script is exactly 0x6a 0x20 and the hash’s 32 bytes. Once the chain holds that transaction (on Bitcoin, once a version of it confirms), Truestamp writes one commitment row per block of the epoch, each carrying the inclusion_proof that walks the block’s block_hash to the epoch tree’s merkle_root, and moves each block still finalized to committed in the same transaction, which happens at the block’s first chain’s commitment; a block the other chain already committed stays committed. A proof carries the block’s commitments as the entries of its commitments, keyed by chain, and a Bitcoin entry appears only once it is final, when the chain is 10 blocks past the transaction’s block. Block Commitment is what lets a verifier read a submitted-before edge from a chain Truestamp does not control; the level below it is Item Commitment. The batching is covered in the epoch and Block Commitment, and the two levels in Item Commitment vs Block Commitment.