Knowledge Base

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

Block hash

The SHA-256 hash under prefix 0x31 of a Truestamp block's seven-member record (height, id, leaf_count, merkle_root, metadata, previous_block_hash, signing_key_id); it chains blocks, is signed, is a leaf of an epoch tree, is the beacon value, and names each item's block witness.

Overview

The block hash identifies a Truestamp block: SHA-256(0x31 || JCS(record)), under the byte prefix 0x31, over the block record of exactly seven members: height, id (the block’s UUIDv7), leaf_count, merkle_root, metadata, previous_block_hash and signing_key_id. metadata is the map itself: {} for an ordinary block, {"key_event": ...} for a key-event block, and {"genesis": ..., "key_event": ...} for the genesis block, whose previous_block_hash is the hash under 0x30 of its genesis object. Because the record holds the previous block’s hash, the hashes chain the blocks; because it holds the Merkle root and the leaf count, it commits to every item and entropy observation in the block. The block hash is what Truestamp signs for each block, with the active key or, for a rotation block, the key the rotation introduces, and that signature stays in Truestamp’s own records. Block hashes are the leaves of each epoch’s tree, whose epoch hash goes on a public chain, and a block’s hash is also its beacon value on the public beacons page.

Every item names a block hash of its own. The hash of the block at the head of the chain when the item was submitted is the required block witness in the item record’s witness_hashes, which fixes the item’s place after that block in the ledger. It gives no edge of the submission window, because no chain or source holds that block’s time.

In a proof bundle every block node carries its block_hash beside its record: the block that includes the subject, an item’s witness block and the block of the signing key event. A verifier recomputes each hash from its record and compares it, and every later check uses the recomputed value: an item’s block witness is compared with it, and it is walked into each commitment’s epoch tree. The field layout is in the proof bundle wire format.