Skip to content

RUFF

RANDOMNESS UTILITY & FULFILLMENT FRAMEWORK

RUFF (Randomness Utility & Fulfillment Framework) gives a consumer contract a 32-byte random result and the public evidence needed to check how it was produced. The contract requests a number; the relayer delivers it in a later block; the consumer receives a callback.

The framework consists of an on-chain hub, a delivery service, and a TypeScript SDK. It is independent of JERDOG’s game rules and registration system. Any deployed consumer contract can request within the hub’s fee and capacity limits.

Capability How it works
Contract requests A paid request fixes its consumer, sequence, lane, and contribution on-chain.
Verifiable output The result combines a committed hash-chain link with the request block hash and request context.
Asynchronous delivery An authorized relayer submits evidence; the hub verifies it before delivery.
Callback recovery A stored result remains readable if the consumer callback fails.
Independent checking Anyone can recompute the formula and verify the seed commitment from public data.
Bounded intake Consumer, global, and optional per-block limits control accepted requests.

RUFF uses commit-reveal randomness: the hub checks every delivered seed against a hash-chain commitment published before the request, mixes in the request block hash, and computes the result on-chain. Anyone can re-check a result from public data, for example with npx ruff-hub verify. Deliveries come from RUFF’s authorized relayers; upgrades require the 2-of-3 Safe and a 600-second timelock. The trust model lists the exact guarantees.

How RUFF protects your results explains what stays protected even if the relayer server is compromised. Secure your RUFF integration covers fixed application state, result derivation, recovery and the limits of additional entropy.

RUFF is the product name. The Solidity contract is RandomnessHub. The public SDK and CLI are distributed as ruff-hub, version 0.2.0.

Contract coordinates and implementation versions are listed in the deployment reference.