Epoch
The batch Truestamp uses for Block Commitment: the blocks after a chain's last recorded epoch form one Merkle tree, and the hash of the epoch record {leaf_count, merkle_root} goes on Stellar or Bitcoin; each chain advances its own series of epochs, and epochs are not signed.
Overview
An epoch is the batch Truestamp uses to perform
Block Commitment. For one chain, the blocks after that
chain’s last recorded epoch, up to the head, are gathered into one Merkle tree over their
block hashes, and the epoch record holds that tree’s leaf_count and merkle_root. Only
the record’s hash, the epoch hash, is written to the public
chain, so a single transaction commits a whole range of blocks, and Stellar and Bitcoin
each advance their own series of epochs, which covers the ledger without gaps. Once the
chain holds the transaction, every covered block gets its commitment into the epoch’s
tree, and each block still finalized moves to committed in the same transaction, at
its first chain’s commitment. Epochs are not signed, and in a proof each commitment entry
carries its epoch as {epoch_hash, record}. How an epoch is reserved and sent, and the
rest of the mechanics, are in the epoch and Block Commitment.