Knowledge Base

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

Beacon

A public, verifiable snapshot of the Truestamp chain, the hash of a finalized or committed block published on the public /beacons page as verifiable randomness and a moment-in-time marker, with four fields (id, hash, timestamp, previous_hash) and a stable permalink per hash.

Overview

In Truestamp, a beacon is a public, verifiable snapshot of the Truestamp chain: the block hash of a finalized or committed block, published on the public /beacons page as a source of verifiable randomness and as a moment-in-time marker. Every beacon exposes exactly four fields, id, hash, timestamp, and previous_hash (the chain-link to the previous beacon), and each hash has a stable permalink at /beacons/<hash>. Because the hash commits, through a Merkle tree, to everything finalized in the underlying block, it is unpredictable before the public entropy its block commits to exists and immutable once the block is finalized, which is what qualifies it as a public randomness beacon, though not one resistant to bias: Truestamp builds each block after its entropy is public, so it could try many candidate blocks and publish the one it prefers. The beacon page also derives deterministic tools from the beacon hash (coin toss, dice roll, random integer, lottery draw, and drawing from a list); each reads the hash directly as one 256-bit number, so outcomes derived from the same beacon are related, and one beacon serves one decision. See public entropy beacons for the page behavior and proof downloads, and public randomness for the security properties, which rest on the entropy sources folded into each block.