Knowledge Base

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

Public randomness beacon

A service that periodically publishes unpredictable, publicly verifiable random values, ideally ones no one can bias; Truestamp consumes external beacons such as the NIST Randomness Beacon as entropy and publishes its own on /beacons, which no one can predict but Truestamp could bias.

Overview

A public randomness beacon is a service that periodically publishes random values anyone can observe, that no one can predict in advance, and that anyone can independently verify after the fact. A good one is also hard to bias: no one, its operator included, can push a value toward a result they prefer. The defining properties are unpredictability, resistance to bias, public verifiability, and availability; together they let mutually distrustful parties agree on an outcome without a trusted referee. Truestamp relates to beacons in both directions: it consumes external public randomness, including the NIST Randomness Beacon, as entropy sources folded into its blocks, and it acts as a beacon itself by publishing each finalized block hash as a beacon on the public /beacons page. Truestamp’s own beacon lacks resistance to bias: no one, Truestamp included, can predict it before its block’s entropy exists, but Truestamp builds the block after that entropy is public, so it could try many candidate blocks and publish the one it prefers, and nothing in a proof shows whether it did. See public randomness for the security properties in depth and public entropy beacons for Truestamp’s own beacon page.