Tyche produces sub-second, threshold-signed attestations that bind timestamp, deterministic ordering, and multiparty randomness into a single stateless round. No blockchain. No token. Just verifiable infrastructure.
Built for audit logs, fairness protocols, AI integrity, and any system that needs a neutral witness instead of another blockchain.
Tyche is not a blockchain and not a single-purpose beacon. Each round produces a compact attestation that simultaneously acts as a timestamp, an ordering digest, and a randomness source.
Multi-operator, threshold-signed timestamps with tight drift bounds. Prove that a digest existed before a specific moment in time without trusting any single clock or authority.
Canonical ordering of gateway-submitted events inside every round, committed via a global Merkle root. No global state, no consensus — just a deterministic function all operators can recompute.
Bias-resistant randomness sourced from many entropy providers using commit–reveal, with optional VDF hardening. Secure as long as at least one provider is honest.
Tyche keeps the heavy cryptography in a small, vetted operator set, pushes client interaction to gateways, and opens randomness to a broad ecosystem of entropy providers.
Core nodes that maintain accurate clocks, exchange subtree roots, and produce threshold-signed round outputs. Limited in number and chosen for diversity and reliability.
Stateless APIs that batch client digests into Merkle subtrees and return proofs after each round. Permissionless to run, free to compete on latency, pricing, and features.
Independent organizations that contribute randomness using commit–reveal. As long as one is honest, the beacon remains unbiased.
Tyche is infrastructure, not a product. It’s designed to sit underneath systems that already exist: audit and compliance stacks, AI pipelines, identity systems, games, and even blockchains.
Anchor security logs, financial events, and cross-org workflows into a neutral witness network. Prove that nothing was silently backdated or rearranged.
Drive commit–reveal flows, lotteries, tournament seeding, and RFP windows with verifiable time and randomness on every round.
Attach external attestations to inference logs, decisions, and agent actions. Make “what happened when” something you can prove, not just assert.
The overview paper describes Tyche’s motivation, design goals, network roles, security model, and roadmap. It’s the right entry point if you want to understand the system in detail without diving straight into a formal specification.
Download the Overview (PDF)