THE ARCHITECTURE
For promotions, game outcomes, and audited selections, SOPH combines a large evolving internal state, derived output extraction, continuous published validation, and opt-in ledger auditability. The point is practical: produce a result fast, then defend it later with evidence when trust matters.
THE PIPELINE
Hardware entropy input → large evolving internal state → derived output blocks
Earlier states are not directly exposed.
The state evolves through mixing rounds that spread change across the whole structure. Later snapshots are not intended to provide a straightforward path back to prior states.
SECURITY PROPERTIES
Design goals and operational advantages, not formal proofs.
Large configurable internal state
At default configuration SOPH maintains a 2,808-bit internal state. That is materially larger than the small fixed states common in many API-facing RNG services, and it can be expanded with configuration.
State secrecy and output secrecy are independent problems
In many constructions, observing enough output tells you almost everything worth knowing about the active state. SOPH is designed so output derivation and internal state tracking are not the same task, which gives teams a larger separation between what stays internal and what gets published.
Post-quantum-oriented design goals
The design is not based on factoring or discrete-log assumptions. Its security intent is closer to hidden state and one-way-style extraction than to public-key hardness, which supports post-quantum-oriented deployment while formal proofs and broader third-party cryptanalysis remain future work.
Most of the state stays internal
SOPH is designed so output represents only a derived view of a larger internal state. That gives teams a different tradeoff from APIs that repeatedly expose a simpler generator state through output alone.
When a draw result may later be disputed, architecture alone is not enough. SOPH publishes ongoing validation results from established batteries against live output so teams can inspect current behaviour instead of relying on marketing copy alone.
NIST SP 800-22
15 statistical tests from the US National Institute of Standards and Technology.
Dieharder
An extended suite derived from Marsaglia's Diehard battery.
TestU01 BigCrush
A demanding public battery often used as a high bar for empirical validation.
PractRand
Designed to detect subtle biases across long runs.
Statistical quality and architecture matter, but some teams also need an auditable publication trail for winner selection and game outcomes. Add ?ledger=true when you want that trail. The session is hash-chained in real time to a public ledger that counterparties can verify independently.
Your application requests a ledger-backed stream
Each output block is hashed and chained to the previous entry in real time
The chain is written to a public ledger for tamper-evident publication
Share the session hash and an external party can verify the published chain independently
Early access is open. Free for 90 days for the first 400 teams.