Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

Committed

The normal resting state on both Truestamp levels - an item is committed once its commitment into a finalized block's Merkle tree exists (Item Commitment), and a block once its commitment into an epoch whose hash is recorded on Stellar or Bitcoin exists (Block Commitment).

Overview

Committed is the normal resting state at both of Truestamp’s levels, with two related meanings. An item becomes committed when its commitment into a finalized block exists: its item hash is a leaf of the block’s Merkle tree, and the commitment holds the inclusion proof to that tree’s root. This is Item Commitment, and the item moves from processing to committed in the same write. A block is created finalized and becomes committed when its commitment into an epoch exists, an epoch whose epoch hash (the hash of its record: its Merkle root and leaf count) Truestamp recorded on Stellar or Bitcoin; this is Block Commitment. A committed item already has a verifiable place in its block, but a proof of it is generated only once that block also has a final commitment on at least one chain. The distinction is explained in Item Commitment vs Block Commitment and the batching in the epoch concept.