• Language

  • Non-English translations are machine-generated.

  • Language Preferences
  • Theme
Sign In

Knowledge Base

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

Tagged: block

9
API
Beacon API The authenticated programmatic beacon surfaces - JSON:API endpoints under /api/json/beacons (list, latest, by id, by hash), the equivalent GraphQL queries, the four-field beacon object, error and rate-limit behavior including the rate_limited code, and beacon proof generation by block id.
Blockchain
Item Commitment vs Block Commitment The load-bearing distinction between Item Commitment (an item's item_hash becomes a Merkle-tree leaf in a finalized block) and Block Commitment (block hashes Merkle-rooted into an epoch whose root is recorded on a public blockchain such as Stellar or Bitcoin), and why a complete proof needs both. Public Ledger Explorer The public ledger explorer pages, no account required - the /blocks index and /blocks/<block_id> detail with commitment chain and proof downloads, the /entropy and /entropy/<observation_id> observation pages, and the real-time /timeline visualization of entropy, items, blocks, and commitments. The Epoch and Block Commitment How Truestamp batches many finalized internal block hashes into an epoch, builds one epoch Merkle root, records that single root on a public blockchain (Stellar via MEMO_HASH, Bitcoin via OP_RETURN), and gives each block an inclusion proof within the epoch as its Block Commitment.
Glossary
Block (Truestamp block) A minute-cadence unit of Truestamp's internal ledger: a Merkle tree over the item hashes and entropy observations collected in that window, hash-chained to the previous block and Ed25519-signed, created finalized and transitioning to committed once an epoch commitment covers it. Block Commitment The second Truestamp commitment event: finalized block hashes are batched into an epoch whose single Merkle root is recorded on a public blockchain (Stellar MEMO_HASH, Bitcoin OP_RETURN), moving each covered block from finalized to committed and adding an external timing witness. Block hash The SHA-256 digest (prefix 0x32) identifying a Truestamp block, binding its UUIDv7 id, previous-block hash, Merkle root, metadata hash, and signing-key ID; it chains blocks, is batched into epochs, published as a beacon, and committed by each item as its block witness. Committed The normal resting state on both Truestamp ledgers - an item is committed once its item hash is a leaf in a finalized block (Item Commitment), and a block is committed once its block hash is covered by an epoch recorded on a public blockchain (Block Commitment).
Product
Global Search How the search page at https://www.truestamp.com/search auto-detects what you paste (26-character item ID, block/beacon/entropy UUID, 32-128 hex digest, or free text over names, descriptions, and tags) and returns grouped items, blocks, beacons, and entropy observations with team-aware visibility.